1 © NOKIA NORDUNET_2000-ipv6.PPT/ 28.9.00 / TKn IPv6 Core technology for the future Internet Timo Knuutila Nokia Research Center [email protected]

1 © NOKIA NORDUNET_2000-ipv6.PPT/ 28.9.00 / TKn

IPv6Core technology for the future

Internet

Timo Knuutila

Nokia Research Center

[email protected]


Presentation outline

• What future Internet ?

• Short history of the Internet

• IPv6 essentials

• Next generation mobile networks (2G/3G/etc)

• Current IPv6 technology status

• Summary


Millions

1996 1997 1998 1999 2000 2001 2002 2003 2004 2005

1,400

1,200

1,000

800

600

400

200

0

Internet Outlook

More handsets than PCs connected to the Internet

by the end of 2003 !

More handsets than PCs connected to the Internet

by the end of 2003 !

Projectedcellularsubscribers(Nokia 1999)

Projected PCsconnected tothe Internet(Dataquest 10/98)

Projected Webhandsets(Nokia 1999)


19991999 20002000

Mobile Internet will be always-on

2002200220012001

Ses

sion

s / M

onth

/ ce

llula

r su

b(le

adin

g m

arke

ts)

Usage

Mobile Web (WAP)Mobile Web (WAP)

Fixed WebFixed Web

WAP

GPRS

IPv6Optimizing

radio capacityusage Scaling up

address space


Why IPv6: Cost of patching IPv4 is too high

• It is possible to implement new services using IPv4

• But, it is becoming more and more expensive to patch IPv4

•IPv6 can bend the cost curve

• Mobile players will face the cost challenge sooner because of

•more terminals, mobility, push, location

Cellular focus* 1000M handsets* always-on * mobility* peer-to-peer* push & location

Ope

rato

r co

st (

CA

PE

X+

OP

EX

)

# of subs100M 1000M

IPv4

IPv6

Current fixed IP focus* 100M PCs * dial-in / power on-off* wireline* client-server* retrieval services


1999 2000 2001QoS support through Diff. Serv. and/or MPLS.

Gradual IPv4 evolution

2002

Dis

rupt

ive

IPv6

leve

rage

Mobile devices with need to be "always-connected" to the Internet, dynamic DNSs

New directory servers and VoIP gateways interworking with telco ntw

• billion of mobile devices with IP connectivity

• IP level security

• roaming btw heterogeneous networks

IPv6 - Shortcut to Global IP Mobility





• IPv6 essentials

• Next generation mobile networks (2G/3G)


• Summary


A view of Internet History

• 1970’s• Arpanet / Internet Technology Invented

• 1980’s• Research / Non-Commercial Internet Service

• 1990’s• The Web and the Internet Everywhere

• Bill Gates decided he Invented it!

• 2000’s• The Mobile and Wireless Internet


The Internet model

• End-to-End Communication• Intelligence in Hosts• Simple / Fast forwarding in Routers

• All Services run over IP

• IP runs over Everything

• IP’s Success based on• Solid Architecture• Technology Evolution





• IPv6 essentials



• Summary


Initial motivation behind IPv6

• IPv4 addressing inefficiencies:• Class B addresses are nearly exhausted.

• CIDR (classless inter-domain routing) provides a short-term solution

• Efficient corporate networking requires more class A addresses or complicated workouts (NATs, DDNS, DHCP)

• Routing tables are growing extremely fast. • More hierarchical addressing levels are required.

• IPv6 provides a good platform for added-value features like security and mobility.

• Inefficient manual configuration management of IPv4:• IPv6 autoconfiguration.


IPv4 address structure

• IPv4 addresses are 32 bit long

• The address contains two parts: network & host • Class A contains 24 bits for host number • Class B contains 16 bits for host number• Class C contains 8 bits for host number

• Class C addresses have been allocated to small organizations (max. 256)

• Most organizations viewed Class C addresses as too small and received Class B addresse (wasting most of its address space)


Non optimal IPv4 address allocation

Theoretically 4,3 Billion Adresses, Currently 60 Million in use

Allocations:

• US Government ~168 Million

• Europe ~80 Million

• IBM ~33 Million

• UK Government ~33 Million

• Stanford University ~17 Million

• China ~ 9 Million

• Lucent ~ 6 Million

• Unlucky large users: Use Net 10 and NATs


• IPv6 address is made of two parts: prefix and suffix (I.e interface-ids)

• and hierachical structure (that depends on format prefix, FP)

• prefix:

• suffix:

• Link-local address (mandatory) is unique within a "link".

IPv6 address

64 bits suffix64 bits prefix

FP TLA NLA SLA

interface ID

64 bits suffix54 '0' bits1111111010


Hierarchy solves routing table explosion

TOP TOP

Next level Next level Next level

Site

LinkHost

Provider,Exchange


IPv6 address types

• Link local, site local, globally routable

• Unicast (1:1)

• Anycast addresses (1: nearest node of a set of nodes): currently only used to address routers

• Multicast (1:n)

• IPv4 compatible: ::/96:IPv4address

• IPv4 mapped: ::/80:FF:IPv4address


Header Format: Main Differences to IPv4

• Streamlined Header Format• Fixed format IPv6 Header and Extension Headers • elimination of header checksum, flags, options, IHL,

hop-by-hop segmentation procedure, ...

Vers

Flags

Type of service Total length

Identification

HLen

Fragment offset

Time to live Protocol Header checksum

Source IP address

Destination IP address

IP options (if any) Padding

IPv4 header (20 bytes or more…)

Source IP address


Vers Class

Next header Hop limitPayload length

Flow label

IPv6 header (40 bytes)


Extension Header

• Purpose: only those nodes process the extension headers for which they are relevant

• Intermediate routers care only hop-by-hop options and routing header

• Six extension headers• Hop-by-Hop• Routing header• Fragment header• Authentication header• Encrypted security payload• Destination option headers

•implements mobility options

Source IP address


Vers ClassNext hdr: 43 Hop limitPayload lengthFlow label

Routing Information

Authentication Data

TCP Header and data

Nxt hdr: 51

Nxt hdr: 6

Header length

Header length


Address Autoconfiguration

• Stateless address autoconfiguration• No central server needed to aid in address

configuration• Node forms its own suffix, checks if it is unique• Node obtains prefix(es) from the nearest router

• Stateful address autoconfiguration• Central server allocates full addresses to nodes on

request• DHCPv6 is the current protocol for stateful address

autoconfiguration


Neighbor Discovery Messages • Router Solicitation

• request to all routers multicast address for router advertisement messages

• Router Advertisement • are sent periodically to the all nodes multicast address or to the

source of a router solicitation message • contains prefix value/length, router address, lifetime, link/Internet

parameters, stateful/ stateless address autoconfiguration flag

• Neighbor Solicitation• sent to solicited-nodes multicast address or to unicast address

• Neighbor Advertisement • response to neighbor solicitation message or propagation of new

information (e.g., link address modification) to all-nodes multicast address

• Redirects• to indicate a better next hop for a specific destination


Routing

• longest prefix match” routing like IPv4 CIDR

• Inter Domain Routing Protocol (IDRP)

• Modification of unicast (OSPF, RIP, BGP) and multicast routing protocols (PIM, DVMRP, MOSPF) to handle larger addresses

• Routing headers to route packets through particular regions


Design Advantages

• Hierarchical addressing allows route aggregation• Smaller routing tables in the backbone, containing

aggregated routes only

• Address autoconfiguration reduces administration overhead

• No need to have a dedicated address allocator

• Extensible headers allow introduction of new features without loss of performance

• IPv4 had only one mechanism for customization: IP options

• IPv4 routers tend to treat IP options in the slow path


Moving to IPv6

• Changes to Domain Name Service

• Changes to Applications

• Interoperability with IPv4• with IPv4 correspondents (e.g., legacy IPv4 servers)• over IPv4 routers


Changes to Domain Name Service

• New DNS records to support IPv6 have been defined

• A4 records: fields have full IPv6 addresses (similar to A records for IPv4)

• A6 records: fields map a name to a suffix and a partial name ("non-terminal literal")

• e.g., a node doing DNS lookup for "www.nokia.com" finds• www.nokia.com -> nokia-isp.nokia.com, p1:s1• nokia-isp.nokia.com -> p2• Therefore, IP address of www.nokia.com is p2:p1:s1

• A6 records make it easy to renumber IP network• e.g., when changing from one ISP to another, change only

the p2 DNS entry.


Changes to Applications

• Non-network applications need no change

• Network applications need to• use new DNS record types for IPv6 addresses • use the new socket API

• Bump-in-the-stack approach for transition• introduces an inter-operability module as a "bump"

in the network stack, between the application/transport layers and the IP layer.

• allows IPv4 applications to work unchanged on IPv6 networks


Interoperability with IPv4

• Interoperability with IPv4 correspondents• Dual stack operation

• May need mechanisms for temporary IPv4 address acqusition scheme: RSIP

• Protocol-and-address translators• IP level: NAT-PT• Transport level: SOCKS• Application level: Application level gateways (ALGs)

• Interoperability over IPv4 routing infrastructure• IPv6-in-IPv4 tunneling• Various mechanisms: automatic tunneling,

configured tunneling, 6to4, and 6-over-4


Transition to IPv6

Users IPv4 Services

Public/Private IPv6 network

Public IPv4 Internet

Users

NAT 6/4

IPv6 Services

IPv6 Service

s


IPv6 Dominates

Users V4 Services

Public/Private IPv6 network

Public v4 Internet

IPv6 Services

IPv6 Services

Users

NAT

NAT

NAT

NAT


Summary: Transition from IPv4 to IPv6

• A number of mechanisms exist; applicability depends on the interworking scenario.

• Main mechanisms• Dual stack,• IPv6-in-IPv4 tunnelling: automatic, configured, 6over4,

6to4• Bump in the stack: legacy applications in a IPv6 host• Protocol translators: NAT-PT• RSIP (Realm Specific IP)• application level gateways, Socks

• Updates on Upper Layers• Upper layer checksums: TCPv6, UDPv6, • DNS "AAAA" and "A6" records• DHCPv6• IPv6 socket





• IPv6 essentials



• Summary


D O C U M E N T T Y P E 1 ( 1 )

T y p e U n i t O r D e p a r t m e n t H e r eT y p e Y o u r N a m e H e r e T y p e D a t e H e r e

U T R A N

R N S

U E( M S )

U E( M S )

U E( M S )

U E( M S )

B S

R N C

R N C

W M S C /V L R

3 G -S G S N

W C D M A a i r i n t e r f a c e

G G S N

G M S C

I P - n e t w o r k

P L M N s , P S T N ,I S D N , e t c . . .

H L R S C P

M A P e

M A P e

C A P

I u

I u b

C A P C A P

C A P

W M S C = W i d e b a n d M S CG M S C = G a t e w a y M S CS C P = S e r v i c e C o n t r o l P o i n t ( I N / C A M E L )

M S = M o b i l e S t a t i o n ( M T + T E + U S I M )U E = U s e r E q u i p m e n t ( = M S i n E T S I )B S = B a s e S t a t i o nR N C = R a d i o N e t w o r k C o n t r o l l e r

3 G - S G S N = 3 G S e r v i n g G P R S S u p p o r t N o d eG G S N = G a t e w a y G P R S S u p p o r t N o d e

U T R A N = U M T S T e r r e s t r i a l R a d i oA c c e s s N e t w o r kR N S = R a d i o N e t w o r k S y s t e m

G s( o p t i o n a l )I u r

R N S

B S

B S

B S

UMTS Rel. 99 Reference Architecture


R99 Interfaces and ProtocolsUMTS User Plane

L1

RLC

PDCP

MAC

E.g., IP,PPP,OSP

Application

L1

RLC

PDCP

MAC

ATM

UDP/IP

GTP-U

AAL5

Relay

L1

UDP/IP

L2

GTP-U

E.g., IP,PPP,OSP

3G-SGSNUTRANMS

Iu-PSUu Gn Gi

3G-GGSN

ATM

UDP/IP

GTP-U

AAL5

L1

UDP/IP

GTP-U

L2

Relay


Rel. 00 All-IP Reference Architecture

Gf GiIu-ps'

Iu

GiMr

Gi

Ms

Gi

R UuMGW

Gn

Gc

Gp

Signalling and Data Transfer InterfaceSignalling Interface

TE MT UTRAN

GrOther PLMN

SGSN

GGSN

GGSN

EIR

SGSN

Gn

MGCF

R-SGW

MRF

MultimediaIP Networks

PSTN/Legacy/External

Applications &Services *)

Mm

Mw

Legacy mobilesignalingNetwork

Mc

Cx

R UmTE MT ERAN

AlternativeAccess

Network

Mh

CSCF

CSCFMg

T-SGW *)

T-SGW *)

HSS *)

HSS *)

Applications& Services *)

MSC server GMSC serverIu1 =Iucs (RTP, AAL2)

Iu2 =Iu(RANAP)

*) those elements are duplicated for figurelayout purpose only, they belong to the samelogical element in the reference model

McMc

MAPMAP

SCP

CAP

MGWNb

Nc

Iu1

Iu2

R-SGW *)

Mh





• IPv6 essentials

• Next generation mobile networks (Mobile Internet)


• Summary


Target scenario for mobile IPv6 development

Sub net Sub net Sub net Sub net Sub netSub net

InternetInternet

Interactive (e.g. VoIP) session


Mobile IPv6 development

• Future Internet is largely wireless/mobile• IPv6 needed for billions of wireless devices• Mobile IPv6 meets mobility requirements better than mobile

IPv4

• Current mobile IP (v4 or v6) specifications are not alone sufficient to construct a network that offers VoIP type of services (real time requirements, no packet loss) with mobile nodes changing their point of attachment frequently.

• Following extensions necessary• regional registrations• header compression• buffer management• authentication infrastructure AAA/HLR interactions


Regional registrations

Problem: • how to reduce latency due to signaling associated with mobile ip

handovers

Solution: Localize signaling to Visited Domain

Method: Regional Registrations, registrations between the MN and the

Visited Domain implies:• signalling between visited domain routers• authentication between MN, visited network routers and home agent• new IETF draft, draft for mobile IPv4 exists





• IPv6 essentials

• Next generation mobile networks


• Summary


IPv6 IETF standards status

• IPv6 IETF Standards•IPv6 Protocol•Addressing Architecture•ICMP •DNS•Security•Unicast Address Formats •Transition Mechanisms•Neighbor Discovery•Address Auto-configuration•IPv6 over Ethernet•IPv6 over FDDI•IPv6 over PPP•IPv6 over Token Ring•IPv6 over ARCNET•IPv6 over Frame Relay•Routing Protocols (RIPng, OSPFv3, ISIS, BGP4++)

•Tunneling•MIB’s•Jumbo Grams•Header Compression•Literal URL format•Mobility Support

• IETF Completing Work•Routing Protocols (PIM)•More MIB’s•IPv6 over <link>•Router Renumbering•DHCP•Service Location•Multihoming•Cellular Header Compression


IPv6 implementations

• Host Systems•BSDI•Digital/Compaq•Epiloque•FreeBSD•HP-UX•IBM (AIX)•INRIA (NetBSD, FreeBSD)•Linux•Mentat (Streams)•Microsoft•Novell•NRL (4.4-lite BSD)•Pacific Softworks•Process Software (VMS)•SCO•Siemens Nixdorf

•Sun Microsystems•UNH•WIDE Consortium (KAME, NAIST, Hitachi, Sony, NTT)

• Routers•3Com•Nortel•Cisco Systems•Digital•Hitachi, Ltd.•Merit•Nokia•NTH University•Sumitomo Electric•Telebit AS


IPv6 applications• Chat software

• IRC: BitchX client - now supports IPv6

• RAT and SDR - Win vers of the UCL conf. ports

• DNS

• BIND 9

• totd - a DNS proxy to support IPv4/IPv6 translation

• Firewalls

• ipfilter - supports IPv6 filtering

• IPFW - included within the FreeBSD 4.0 release

• netfilter - IPv6 patches for Linux's packet filter

• FTP

• LFTP - supports IPv6 as is

• NcFTP (Windows) - available from MSR

• NcFTP (BSD) - from the KAME project site

• Games

• Quakeforge - a FreeBSD port by Viagenie.

• Java

• IPv6 Java for Windows - note this is not a Sun Javasoft product

• Mail

• Monitoring Tools

• News

• Socket software

• Tunnel/translator software

• WWW

• Apache (Linux) - from the Japanese Linux user group

• Apache (BSD) - from the KAME project site

• Fnord! - a Windows web server from MSR

• lynx v2.8.2 - port of LYNX by Tromso

• mini_hhtpd - a Web server with IPv6 support

• Mozilla - port of the broswer by KAME

• Squid - port of the web cache by KAME

• thhtpd - a Web server with IPv6 support

• w3m - a text-based browser that supports IPv6

• wwwoffle v2.5 - a proxy for viewing v6 only sites


IPv6 offerings

• Two ISP:s in Japan offering commercially IPv6 connectivity

• A lot of (political) enthusiaism in Far-East and Europe

• References• http://playground.sun.com/pub/ipng/html/ipng-

main.html• http://www.ipv6forum.com • http://www.6ren.net• http://www.6bone.net• http://www.6tap.net• http://www.ipv6.org• http://www.3gpp.org• http://www.3gpp2.org• http://www.mwif.org





• IPv6 essentials



• Summary


Summary

• Mobile devices will play major role in the growth of Internet

• Internet Doubles Every Year• Creates strain on Infrastructure• Creates Tremendous Opportunity

• Exponential Growth Means• Every three years 85% of installed base is new

• IPv6 starts to be mature enough to be deployed commercially

• IPv6 will be the enabling technology for the mobile Internet


Thank You !

Documents

1 © NOKIA NORDUNET_2000-ipv6.PPT/ 28.9.00 / TKn IPv6 Core technology for the future Internet Timo Knuutila Nokia Research Center [email protected]