p00-20010409-029 r1 atlanta, ga april 9-12, 2001 title: ipv6 motivation in 3gpp2 source: ernie...

P00-20010409-029 R1 Atlanta, GA April 9-12, 2001

TITLE: IPv6 Motivation in 3GPP2

SOURCE: Ernie Tacsik+1 [email protected]

NoticeThe contributor grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other

copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner's standards publication. Permission is granted to 3GPP2 participants to copy any portion of this contribution for the legitimate purpose of the 3GPP2. Copying this contribution for monetary gain or other non-3GPP2 purpose is prohibited.


Outline Cellular Requirements & Issues External Influences IPv4 Limitations IPv4 to IPv6 Transition IPv4 & IPv6 Interoperability Conclusion/Recommendation & References


Cellular requirements

1 billion devices in 2002/3 Millions of always-on devices/operator? New services requires:

always on (has an IP address) push technology autoconfiguration real time telephony security


Mobile Subscriptions (Seimens)


Mobile entertainment services revenue (Yankee Group 2000, Gartner 2000)

0

2

4

6

8

10

12

14

16

18

1999 2000 2001 2002 2003 2004

USD

, Bil

lion

s

GamesGraphicsAudioVideo


Hypothetical Subscriber Breakdown

North America CDMA '03 (85 million subscribers - Dataquest SEP'00)

• Assumptions:– 50% IP enabled phones (42.5 m)

• 50% of those on any given time (has IP addr.) (21.3 m)

– 75% ext MM srvc (15.9 m)– 25% int MM srvc (5.4 m)

• IPv4 Net 10 addr. Supports 4 m users

• 15.9 m >>> 4 m

CS phone

Not on

on & IPexton & IP int


Example of IPv4 Address Allocation Inequity - CHINA

Currently Allocated ~ 9 Million Global Addresses

(137 /16’s + 27 /24’s) Other Allocations (minimum)

Stanford University ~17 Million

IBM ~33 Million

US Government ~168 Million

UK Government ~33 Million

Europe ~80 Million


All-IP PS

core

Operator IPv4 services


Edge Router

Operator Network Domain

FW

HA4/6

AGW4/6

IPv6Internet

IPv6 Intranet

CN6

Operator NW IPv4

Internet

Router 1

MS

IPv4 Intranet

Functionality:• NAT• NAT-PT / NAPT-PT• Encapsulation / decapsulation• RSIP • ALGs• etc.

IPv4/v6 Services Number of users within Operator's IPv4 domain is limited

(externally) to that operator's allocated address space (globally routable addresses) - internal services virtually unlimited

For example net 10 address yields 4.2 million maximum users

External IPv6 services

Limited To Operator'sIPv4 Address Space

External IPv4 services


COMMISSION OF THE EUROPEAN COMMUNITIES

(Brussels 20.3.2001COM(2001)141 final)

"The current implementation of the Internet Protocol (version 4, IPv4) is considered to limit the full deployment of 3G services in the long run. The proposed new IP version (IPv6) would overcome this addressing shortage and enable additional features, such as guaranteed quality of service and security. Implementing IPv6 mobile networks will also allow for wireless machine-to-machine interconnection, thereby considerably boosting the application of 3G. Any delay in the transition to all-IPv6 networks, which will require several years of effort, risks hindering the deployment of these advanced 3G service features at a later stage."

"Full potential of 3G services cannot be exploited without the gradual introduction of the new Internet Protocol (IPv6). A fully-fledged mobile Internet, where each mobile terminal will have an Internet address requires a much larger address space than the current IPv4 can cater for. In time, Europe risks to run out of Internet addresses if co-ordinated action is not taken now. The European Commission will invite Member States to work together with industry in an ad hoc group, which should provide proposals by the end of 2001 to accelerate the introduction of IPv6. The Commission will also increase support for test beds through its IST and TEN Telecom programmes."


3GPP TS 23.221 V1.1.0 (2001-01)

Technical Specification Group Services and System Aspects;Architectural requirements;

(Release 5)

5.1 IP version issuesThe UMTS/GSM architecture shall support IPv4 / IPv6 based on the statements below.

IP transport between network elements of the IP Connectivity services (between RNC, SGSN and GGSN) and IP transport for the CS Domain: both IPv4 / IPv6 are options for IP Connectivity

IM CN subsystem elements (UE to CSCF and the other elements e.g. MRF):

The architecture shall make optimum use of IPv6.

The IM CN subsystem shall exclusively support IPv6.

The UE shall exclusively support IPv6 for the connection to services provided by the IM CN subsystem.

Access to existing data services (Intranet, Internet,…):

The UE can access IPv4 and IPv6 based services.


Why not IPv4 + NAT ? (1 of 2)

Net 10 (private addresses) is too small: Max: 2M nodes

Potentially, several layers of NAT are needed. Nobody knows how to do that today.

NAT breaks the End to End model prevents IPsec, makes the network less secure.

NAT prevents "incoming calls". Problem with "push" technology, VoIP, local services...


Why not IPv4 + NAT ? (2 of 2)

NAT boxes are single point of failure. Makes the network less reliable.

Deployment of new services may requireALG set-up on all NAT boxes. Requires global co-ordination.

Makes the cost of introducing new services higher.

Obliterates many of the advantages of using IP.


Costs of IPv4 based solution

Costs of the daily management of NAT boxes

Costs of introducing new services

Costs of "buying" IPv4 global addresses

Costs of doing 2 architectures for 3G networks: Once with IPv4 now

Transition to IPv6 later


Why IPv6 ?

IPv6 solves the address issue once for all.

IPv6 has some interesting properties: Auto-configuration

MobileIPv6: within IPv6 world, triangular or quadrangular routing is not necessary

IPv6 is an evolution from IPv4, not a revolution Operation & Management of IPv6 networks are similar to IPv4

ones. Training can be reused.


Advantages over IPv4 + NAT

New applications deployed within IPv6 networks do not require proxies or NAT boxes.

One can do direct IPv6 communications with content providers, other wireless carriers, and anybody else which deploys IPv6.

NAT-PT or ALG are only needed at the boundaries with IPv4.


Evolution of costs

The strain on the NAT boxes will increases as the number of subscribers increase and new applications are rolled out.

The strain on the proxies and NAT-PT boxes can be managed by making direct IPv6 connections to the key sites.

IPv4 IPv6


Transition issues

New applications are rolled out with IPv6.

Not all applications need to communicate between the original IPv4 Internet and the cellular devices.

The most important ones are:VoIP, Web and Mail.

Dual Stack (IPv4/IPv6) proxies can be a good, simple solution.


Transition mechanisms

The IETF NGtrans working grouphas developed a set of transition mechanisms: to connect v6 islands with tunnels:

automatic, configured, tunnel brokers, 6over4, 6to4...

to allow communication between IPv4 and IPv6: Dual Stack, SIIT, NAT-PT, BIS, TCP-relay, SOCKS, DSTM…

Dual Stack & Tunnelling best approaches for 3GPP2, NAT-PT where necessary


Transition phases 1/2 Today: PDSN/CDMA 2000 network supports only IPv4• IPv4 terminals• NATs required• Services via IPv4

First phase: separate IPv6 islands in the network• Most IPv6 services are provided in the operator network • IPv4 and dual stack terminals

IPv4

Internet

First phase

IPv6 Intranet

Operatornetwork

IPv4Intranet

NAT

NAT-PT

MT

MT

IPv4

IPv4NAT

dual stackIPv4 / IPv6

core router

IPv4 world today - the starting point

IPv4

InternetOperatornetwork

IPv4Intranet

NAT

MT

NAT

NAT

IPv4

IPv4

IPv4Intranet

MTIPv4

core PDSNrouter

router


Transition phases 2/2•Second phase: IPv6 is widely deployed• Mainly dual stack terminals•IPv4 & IPv6 services

•Final phase: IPv6 is dominant and virtually all services work on IPv6 platform• No NATs / NAT-PTs needed in mobile networks.• Some separate IPv4 networks still exist

Second phase

IPv4

Internet

IPv6

Internet

Operatornetwork

IPv6Intranet

IPv6Intranet

IPv4 Intranet

NAT

NAT-PT

MT

NAT-PT

MT

dual stackIPv4 / IPv6

dual stack

dual stack NAT

MTIPv6

core PDSN

Final phase

IPv6

Internet

IPv6Intranet

IPv6 IntranetOperator

network

IPv4 IPv4

MT

MT

NAT-PTNAT-PT

MT

IPv6

dual stackin IPv6 mode

IPv6

IPv6

core PDSN

router

router


IPv4 / IPv6 interoperability If two communicating IP nodes do not share the

same version of IP - protocol translators (like NAT-PT) are needed. Dual stack is a good way to ensure that the communicating nodes do share the same version of IP.

Three different types of network services: IPv4 services over IPv4 network.

IPv6 services over IPv4 network – communicating IPv6 nodes / networks are connected via IPv4 Internet by tunneling. Use of protocol translation is also possible.

IPv6 services over IPv6 network.


IPv4 Intranet

core

IPv4Internet

AG

Edge

Router

NAT

Operator network

FW

Router 1

"IPv4"

c)

a)

b)

Operator

IPv4 servicesHost

IPv6Internet

IPv6Intranet

Operator NW

Router

Host

Native IPv4 Terminal to v4 host Three cases are shown:

a) connection to an IPv4 host in Intranet;

b) connection to an IPv4 host via public Internet;

c) connection to an IPv4 host via public Internet using private IP

addresses and NAT in the operator network.


NAT

IPv4 Internet

Operator NW

core

AG

routerEdge Router

Operator network

FW



IPv4 Intranet

Dual stack hostin IPv4 mode

Native IPv4host

Dual Stack Terminal (v4 mode) to v4 host (Private Address Allocation)

NAT functionality is needed when the mobile terminal is communicating with a native IPv4 host via IPv4 Internet.


IPv4 Internet

IPv6Intranet

IPv6Internet

Operator NWcore

AG

PDSNEdge Router

Operator network

FW

6to4 tunnel between ER and Router 1

Router 1

Host

The routing done via IPv6 network

The routing done tunnelled via IPv4

network

Capable

of tunneling



IPv4 Intranet

Dual Stack Terminal (v6 mode) to v6 host

The packets are routed via IPv6 Internet or tunneled via IPv4 Internet to the peer host having a "6to4" type of address.

The edge router makes the "6to4" tunneling (encapsulation / decapsulation).


core

IPv6

IPv6interface

IPv6interface

IPv4

IPv4 InternetEdgerouter

IPv6IntranetIPv6

IPv6/v4gateway

Dualstackrouter

IPv4interface

6in4tunnelAGW

AGW

IPv4

IPv6

Dual Stack MSin IPv4 modeor IPv4 only MS

Dual Stack MSin IPv6 mode

6to4tunnel

Summary: MS IP connectivity

Edgerouter

ExternalIPv4Services



IPv6OperatorServices

IPv4OperatorServices


Outline Cellular Requirements & Issues External Influences IPv4 Limitations IPv4 to IPv6 Transition IPv4 & IPv6 Interoperability Conclusion/Recommendation &

References


Conclusion/Recommendation

Adopt fundamental message from TS 23.221:

IP transport : both IPv4 / IPv6 are options for IP Connectivity

IM control & bearer plane elements (e.g. MS to CSM): The architecture shall make optimum use of IPv6.

The IM control & bearer planes shall exclusively support IPv6.

The MS shall exclusively support IPv6 for the connection to services provided by the IM control & bearer plane.

The MS can access IPv4 and IPv6 based services.


References IPng wg

http://playground.sun.com/ipng

6bone http://www.6bone.net

NGtrans wg http://www.6bone.net/ngtrans

IPv6 forum www.ipv6forum.com

p00-20010409-029 r1 atlanta, ga april 9-12, 2001 title: ipv6 motivation in 3gpp2 source: ernie...

Documents