The migration from IPv4 to IPv6...IPv6 Task Force June 25th 2001 Brussels 1 The Armstrong IPv6 project The migration from IPv4 to IPv6 The Armstrong IPv6 Project Dr. André Zehl Deutsche

1IPv6 Task Force June 25th 2001 Brussels

The Armstrong IPv6 project

The migration from IPv4 to IPv6

The Armstrong IPv6 Project

Dr. André ZehlDeutsche Telekom

[email protected]

2


IPv6 Task Force June 25th 2001 Brussels

The project title?

• We thought we get rid of the usual three-letter project acronym ...

• „One small step for IP, but a giant leap for mankind“

3



Agenda

• Quick overview: The Armstrong project• The migration tools: transition

mechanisms• Things to do as an IPv6 ISP• Which transition mechanism to use?• Conclusion from this presentation



The Armstrong project

5



What is EURESCOM?

• Performs collaborative R&D projects for new telecommunications and Internet scenarios, network solutions and advanced services.

• European Institute for Research and Strategic Studies in Telecommunications

• Founded in 1991 and located in Heidelberg, Germany.

• 20 Shareholders from 19 European countries

6



The Armstrong Network PoPs & Partners

7



Rationale for the Armstrong project

• Operational experience needs to be gained by the Internet community with the deployment of the IPv6 protocol suite

• Appropriate transition mechanisms and strategies for various scenarios are needed

• This project can be seen as an IPv6 deployment trial with a European provider testbed.

8



Main Project Results

• “Transition strategies IPv4 to IPv6” – January 2001

• “Inter-provider Routing and Peering in IPv6“– March 2001

• “IPv6 in Always On and Mobile Scenarios (e.g. UMTS)” – April 2001

9



Transition strategies IPv4 to IPv6

• Which are the possible transition strategies for an incremental transition from IPv4 to IPv6?

• Which advantages and disadvantages do these transition mechanisms offer for ISPs

• What should “legacy” (IPv4) ISPs do (what could “greenfield” ISPs do)?

10



The migration from IPv4 to IPv6

• Migration is a complex problem• Transition will take a long time• Transition requires an analysis of the

network environment• A „flag day“ is not acceptable• The good news: the IETF had all this in

mind, when designing IPv6



The migration tools:transition mechanisms

12



3 types of mechanisms• Dual Stack

mechanismsallow for the parallel usage of IPv4and IPv6 in onemachine or network

IPv4

draft-ietf-ngtrans-ngtrans-dstm-03.txt

DualStackNodeAIIH

(DHCPv6DNS)

IPv6

DSTM

IPv4


DualStackNodeAIIH

(DHCPv6DNS)

IPv6

DSTM

RFC 1933RFC 1933

IPv6/v4

NodeIPv6

IPv4

DualStackNode

NodeIPv6

IPv4

DualStackNode

13



3 types of mechanisms• Tunneling

mechanismsallow for the usage of IPv6 services over IPv4

IPv6

draft-ietf-ngtrans-6to4-03.txt

IPv6IPv4

6to4

IPv6


IPv6IPv4

6to4

RFC2529

IPv4IPv6Node

IPv6Node6over4

RFC2529

IPv4IPv6Node

IPv6Node6over4

IPv4


DualStackNodeAIIH

(DHCPv6DNS)

IPv6

DSTM

DSTMBorderRouter

IPv4


DualStackNodeAIIH

(DHCPv6DNS)

IPv6

DSTM

DSTMBorderRouter

14



3 types of mechanisms• Translator

mechanismsallow for a smooth transition from IPv4 to IPv6

IPv6 IPv4

NAT/PT

SIIT

RFC 2766/2765

IPv6 IPv4IPv4

NAT/PT

SIIT

RFC 2766/2765

BITS

IPv6Stack

BITS

IPv6Stack

IPv4Appli-cation

IPv4Appli-cation

RFC 2767

IPv6Host

IPv6 IPv4

Draft-ietf-socks-gateway-05

IPv4Host

SOCKS- GatewayTCPUDP- Relay

IPv6Host

IPv6 IPv4

Draft-ietf-socks-gateway-05

IPv4Host

SOCKS- GatewayTCPUDP- Relay

15



Realistic Scenario:Dual Stack systems

• Routers and hosts support IPv4 and IPv6

• E.g. if the Domain Name System (DNS) returns an IPv6 address, IPv6 will be used.

• Problem: 1 IPv4 address / host

DualStackNode

DualStackNode

RFC 1933

DualStackNode

DualStackNode

RFC 1933

IPv6/v4

16



Dual-stack: Dual Stack Transition Mechanism (DSTM)

IPv4


DualStackNodeAIIH

(DHCPv6DNS)

IPv6

DSTM

DSTMBorderRouter

17



Realistic Scenario:IPv6 in IPv4 Tunneling

• static or automatic tunneling (e.g.6to4)

IPv6 in IPv4 tunnel connection

IPv4 connection with IPv6 packet as payload data

IPv6 connection

IPv6 IPv6 IPv6

IPv4IPv4

Internet

IPv6

18



7XQQHO�%URNHU

'16�6HUYHU

,3Y��:RUOG

7XQQHO�6HUYHU�,��'XDO�6WDFN�

&RQILJXUHG�,3Y��LQ�,3Y��7XQQHO

7XQQHO�6HUYHU�,,��'XDO�6WDFN�

7XQQHO�6HUYHU�,,,��'XDO�6WDFN�

,3Y��:RUOG

1DWLYH�,3Y�

,3Y��RQO\��(QGV\VWHP

Tunnel Broker

19



Realistic Scenario:6to4

• To interconnect IPv6 islands in IPv4 sea

• Egress router creates tunnel to other domain

• Prefix formed from special TLA (2002::/16) and IPv4 address of egress router

IPv6


IPv6IPv4

6to4

20



Protocol Translation

• Sort of cross between proxy server and NAT

IPv6 IPv4NAT/PT

SIIT

RFC 2766/2765



Things to do as an IPv6ISP

22



Do nothing / Let users use external Tunnel Broker

IPv6 sevices

IPv6 network

IPv4 access/transit network(Telco)

Tunnel Broker Tunnel

IPv4 network

ISP

Dual stack hostor router

Tunnel Server

Tunnel Broker

23



Offer Tunnel Broker and Tunnel Server

IPv6 sevices

IPv6 network

IPv4 access/transit network(Telco)

Tunnel Broker Tunnel

Tunnel Broker

Tunnel Server

IPv4 network

IPv4 network

IPv6 transit network

ISP A

ISP B

Dual stack hostor router

Configured tunnel

24



Offer Dual Stack Network(early stage)

Ipv4 only router

Dual stack router

Ipv6 only router

Ipv4 only link

Dual stack router

Ipv6 only link

edge

core

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Internet

25



Offer Dual Stack network(intermediate stage)

Ipv4 only router

Dual stack router

Ipv6 only router

Ipv4 only link

Dual stack router

Ipv6 only link

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer routerCustomer router

edge

core

Internet V6

Internet

26



Offer Dual Stack Network(late/final stage)

Ipv4 only router

Dual stack router

Ipv6 only router

Ipv4 only link

Dual stack router

Ipv6 only link

edge

core

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Internet

Internet V6

27



Alternative path: Offer edge only IPv6 networks (first)

Customer router

IPv6 only router

dual stack router

Ipv4 only router

Ipv4 link

Ipv4 and Ipv6 link

Lien Ipv6 link

IPv6-in-Ipv4 tunnel

edgecore

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Internet V6

Internet

28



Alternative path: Offer edge only IPv6 network (intermed.)

Customer router

IPv6 only router

dual stack router

Ipv4 only router

Ipv4 link

Ipv4 and Ipv6 link

Lien Ipv6 link

IPv6-in-Ipv4 tunnel

edge

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

core

Internet

Internet V6

29



Alternative path: Offer edge only IPv6 network (late/fin.)

Customerrouter

IPv6 only router

dual stack router

Ipv4 only router

Ipv4 link

Ipv4 and Ipv6 link

Lien Ipv6 link

IPv6-in-Ipv4 tunnel

edge

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Customer router

Ipv6 core

core

Internet V6

Internet

30



IPv6

IPV4 only

IPv6 native network NAT-PT

IPv6

IPv4

IPv4

Things one could do as a new IPv6-only ISP



Which transition mechanism to use?

32



Phases for transition

LegacyIPv4

Internet(As we knew it)

LegacyIPv6

IPv6 OceanIPv4

Islands,legacy v4

apps

LargeIPv4nets, large

IPv6 nets

Large IPv4

Ocean,SmallIPv6

islands

1 53 42

IPv4IPv6

DSTMNAT-PT

BIS„4to6?“

NAT-PTBIS

TB6to4

6over4NAT-PT

BIS

Phase 1 53 42

33



Prelim. Interoperability table<draft-krampell-v6transition-interaction-00.txt>

Src \ Dest 6to4 Tunnel Br DSTM SOCKS NAT-PT BIS 6over4-------------------------------------------------------------6to4 x A(1) N/A N/A A(2) A(1) A(1)

Tunnel Br A(1) x N/A N/A N/A A(2) A(1)

DSTM N/A N/A x A(3) A(1) N/A N/A

SOCKS A(2) N/A A(1) x A(1) N/A N/A

NAT-PT A(2) N/A A(2) N/A x A(1) N/A

BIS A(1) A(1) N/A N/A A(1) x A(1)

6over4 A(1) A(1) N/A N/A N/A A(1) x

-------------------------------------------------------------A(1) = applicable, will workA(2) = applicable, with special limitation, see commentA(3) = Applicable, one mechanism has a limitationN/A = Not applicable, because mechanisms have a different goalx = no interaction of transition mechanisms

34



Conclusion from this presentation

• The IETF has developped a plethora of transition mechanisms

• This is good, since no single mechanism applies to all situations

• The philosophy is to offer a toolbox with special tools for special cases

• Some guidelines must be applied, to easily choose the right tool for a specific case



Outlook

36



7KH�7VXQDPL ,3Y��3URMHFW7KH�7LGDO�:DYH�RI�,3Y��LV�JRLQJ�WR�KLW�WKH�FRDVW�VRRQ

37



For more information ...

• http://www.eurescom.de/public/projects/P1000-series/p1009/P1009.htm

• Email [email protected]

Thank you for your attention!

Documents

The migration from IPv4 to IPv6...IPv6 Task Force June 25th 2001 Brussels 1 The Armstrong IPv6 project The migration from IPv4 to IPv6 The Armstrong IPv6 Project Dr. André Zehl Deutsche