Deploying IPv6 Networks

8/6/2019 Deploying IPv6 Networks

1/94

111 2002, Cisco Systems, Inc. All rights reserved.

Session Number

Presentation_ID


2/94


3/94

3 2002, Cisco Systems, Inc. All rights reserved.RST-231

Deploying IPv6 Networks

Session RST-231

Axel Clauberg

[email protected]


4/94444 2002, Cisco Systems, Inc. All rights reserved.RST-231

Agenda

Why IPv6?

Current IPv6 Market & Some Examples

IPv6 Technology Update and Challenges Deployment Scenarios

IPv6 @ Cisco Conclusion



Why IPv6?



Why IPv6?

Addresses

Plug and play

Scalable Home Networking

Mobility

Not really a reason for IPv6:

Security

QoS



IP Address Allocation History

1981IPv4 Protocol Published

1985 ~ 1/16 of Total Space




This despite increasingly intense

conservation effortsPPP/DHCP address sharing

CIDR (classless inter-domain routing)

NAT (network address translation)

Plus some address reclamation

Theoretical limit of 32-bit space: ~4 billion devices;practical limit of 32-bit space: ~250 million devices

(See RFC 3194)



Playing with the Numbers

Internet users or PC

~530 million users in Q2 CY2002, ~945 million by 2004

(Source: Computer Industry Almanac)

PDA, pen-tablet, notepad

~20 millions in 2004

Mobile phonesAlready 1 billion mobile phones delivered by the industry

Transportation

1 billion automobiles forecast for 2008

Internet access in planes, trains, ships

Consumer devices

Billions of home and industrial appliances



Home Area Networking Paradigm

Deployment of key intra-home areanetworks layer 2 technologies

Bluetooth, Ethernet, IEEE 1394, wireless

Plug and play mechanisms todecrease the operational costs

Stateless auto-configuration

CPE prefix delegation mechanisms

DNS auto-discovery

New services adapted to always-onAlways-attacked protection

Internet

Router



Mobile InternetDelivering Convergence



Networks in MotionMobile Router

HA

CNCN

MR

IPv6

Extend IP connectivity to any kind of mobile environment

Enables new services and applications

Enhanced scalability of mobile environment


12/94


Current IPv6 Market &Some Examples


13/94


Who Is Using IPv6 Today?

Academic NRN

Internet-II (Abilene, vBNS+), Renater, SURFnet, DFN,

GARR, Nordunet, 6REN/6TAP, JGN, Government/military

Geographies and politics

Japan, Korea, China

EEC e-Europe document and IPv6 task force,Euro6iX, 6net

Wireless

IPv6 still mandatory for UMTS rel. 5 multimedia

Not deployed before 2005 (+ ?)


14/94


Enterprises?

Requires IPv6 support by O.S. and applications

SUN Solaris 8+, IBM z/OS 1.4 & AIX 4.3+, HP, FreeBSD

4.x, Linux, Microsoft Windows XP Pro SP1, MicrosoftWindows .NET Server...

Waiting for killer environment

Addresses are a problem for severalenterprises after a series of mergers


15/94


16/94


IPv6Looking at the Crystal Ball

X

20072010

Q

1

Q

2

Q

3

Q

4

2005

Q

1

Q

2

Q

3

Q

4

2004

Q

1

Q

2

Q

3

Q

4

2002

Q

1

Q

2

Q

3

Q

4

2003

Q

1

Q

2

Q

3

Q

4

2006

Distribut

ed

Gami

ng

ideAp

plicatio

ns

Suppor

t

Cisco IOS

IPv6 EFT

Early Adopters

Application Port

ISP Adoption

Enterprise Adoption

Consumer Adoption

19962001

WE-Europe, E-Japan, North-America IPv6 Task Force,


17/94


IPv6Working out the Timeline

Q

1

Q

2

Q

3

Q

4

Q

1

Q

2

Q

3

Q

4

Q

1

Q

2

Q

3

Q

4

Q

1

Q

2

Q

3

Q

4

Q

1

Q

2

Q

3

Q

4

20072010200520042002 2003 2006

Deploying

Testing

Identifying aBusiness Case

Registering for

an IPv6 Prefix

Funding

the Project

Training

Production

How Long Is Needed for Each Phase of an IPv6 Deployment Project?


18/94


SURFnet

Dutch NRN, see http://www.surfnet.nl

Currently 5th network generation

STM-64c/OC-192c core with mostly12416 routers

SURFnet-4 and SURFnet-5 ran in parallel for ayear, which created a big opportunity to test newservices

Dual-stack IPv4/IPv6

IPv6 service offering via tunnel, dedicated link,dual-stack
http://www.surfnet.nl/http://www.surfnet.nl/


19/94


SURFnet Topology

750712416

750712416

750712416

750712416

750712416

750712416

750712416

750712416

7507

12416

7507

12416

7507

12416

7507

12416

7507

12416

7507

12416

7507

12416Den Haag Eindhoven Amsterdam Leiden Delft Maastricht Rotterdam

WageningenTilburgNijmegenZwolleGroningenHilversumUtrechtEnschede

Amsterdam

Sara

12008

12008

7200

12008

12008

GE

POS OC192

POS OC48

Amsterdam

Hempoint Startap and

Starlight

GEANT

AMS-IX

Inter-

national

Chicago


20/94


New EU-Funded (IST) Projects

Euro6IX

Link IPv6 exchange points

Mostly incumbent carriers, some universities

Without involvement of traditional IXP operators

See www.euro6ix.org

6net

Coordinated by Cisco, 34 Partners

Dante, Terena, 9 NRNs (Renater, DFN, UKERNA,SURFnet, NorduNET, GRNET, GARR, SWITCH,ACONET), Universities, IBM, SONY, NTT recentlyadded: ETRI, Hungarnet, CESNET, PSNC

www.6net.org
http://www.euro6ix.org/http://www.6net.org/http://www.6net.org/http://www.euro6ix.org/


21/94


6net Main goals

To build and operate a dedicated internationalIPv6 network, and use this network to validate

that the demands for the continuous growth ofthe global Internet can be met with the new IPv6technology.

To help European research and industry to playa leading role in defining the next generation ofnetworking and application technologies that go

beyond the current state of the art.


22/94


6net Workflow

WP1: Build & operate the IPv6 network

WP5:

IPv6 application

trials

WP2:IPv4-IPv6

coexistence,

interworking &

migration

WP6:IPv6 network

management

architecture &

tools

WP4:

Application &

service support

WP3:

Basic

Network Services

WP1: Build & operate the IPv6 network

WP5:

IPv6 application

trials

WP2:IPv4-IPv6

coexistence,

interworking &

migration

WP6:IPv6 network

management

architecture &

tools

WP4:

Application &

service support

WP3:

Basic

Network Services

WP0 - Project management and technical management

WP7 - Dissemination and exploitation


23/94


The actual 6net network

United Kingdom Sweden

Germany

Italy

Switzerland

France

The Netherlands

Austria

Greece

L2-ISIS Neighborship

STM1 POS/ATM

STM1 Tunnel

Denmark Norway

Finland

Sweden

NorduNET

STM16 POS

Gigabit Ethernet

ATM Link

NREN

POP

NREN

POP

NRENPOP

NREN

POP

NREN

POP

NREN

POP

NREN

POP

NRENPOP

NRENPOP


24/94


6net Equipment

Hardware6net PoP: 12404NRN PoP: 12404 or 7206

Initial softwareCisco 12404: IOS 12.0(22)S

Cisco 7206: IOS 12.2(8)T


25/94


IPv6 TechnologyUpdate and Challenges


26/94


IPv6 Technology Scope

IP Service IPv4 Solution IPv6 Solution

Mobile IP with Direct

Routing

DHCP, ZeroConf

Mobile IP

IGMP/PIM/MulticastBGP

IP Multicast MLD/PIM/Multicast BGP,Scope Identifier

Mobility

AutoconfigurationServerless, ZeroConf,

Reconfiguration, DHCP

32-bit, NetworkAddress Translation 128-bit, NAT-PTAddressing Range

Quality of ServiceDifferentiated Service,

Integrated ServiceDifferentiated Service,

Integrated Service

SecurityIPSec Mandated,

Works End-to-EndIPSec


27/94


IPv6 Update

Flow label

Addresses

DNS

IPv6 multicast

Security Mobility


28/94


IPv6 Flow Label

Ver.

Time toLive

Source Address

Total LengthType ofService

HdrLen

IdentificationFragment

OffsetFlg

ProtocolHeader

Checksum

Destination Address

Options

Source Address

Payload LengthNext

Header

Hop

Limit

Flow Label HdrLen

IdentificationFragment

OffsetFlg

HeaderChecksum

Options

Flow LabelTrafficClass

Ver.

Potential use for the Flow Label finallydescribed inhttp://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txt

Destination Address
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txthttp://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txthttp://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txthttp://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txt


29/94


IPv6 Header Options (RFC 2460)

IPv6 Header

Next Header

= TCP

TCP Header

+ Data

IPv6 Header

Next Header

= Routing

Routing Header

Next Header = TCP

TCP Header

+ Data

IPv6 Header

Next Header

= Routing

Routing Header

Next Header =

Fragment

Fragment Header

Next Header = TCP

Fragment of

TCP Header

+ Data

Processed only by node identified in IPv6 destination addressfield => much lower overhead than IPv4 options

Exception: Hop-by-hop options header

Eliminated IPv4s 40-octet limit on optionsIn IPv6, limit is total packet size, or path MTU in some cases


30/94


Global Unicast Addresses (RFC 2374)

TLA = Top-Level AggregatorNLA* = Next-Level Aggregator(s)SLA* = Site-Level Aggregator(s)

All subfields variable-length, non-self-encoding(like CIDR)

TLAs may be assigned to providers orexchanges

SiteTopology

(16 Bits)

InterfaceIdentifier

(64 Bits)

PublicTopology

(45 Bits)

Interface IDSLA*NLA*TLA001


31/94


6Bone Addressing

3ffe

pTLA Prefix

Site Prefix

/28 /48 /64

LAN Prefix

The 6Bone uses the 3ffe::/16 range:

A pTLA receives a /28 prefixA site receives a /48 prefix

A LAN receives a /64 prefix


32/94


Initial Address Allocation

2001

ISP Prefix

Site Prefix

/35 /48 /64

Registry

/23

0410

LAN Prefix

The allocation process was:

IANA allocates 2001::/16 to registries

Each registry got a /23 prefix from IANA

Registry allocated a /35 prefix to IPv6 ISP/LIR

Policy is that an ISP allocates a /48 prefix to each customer

Address AllocationNew Scheme


33/94


Adopted Globally (ARIN, APNIC, RIPE)

2001 0410

Site Prefix

/48 /64/32Grow on HD Ratio

Initial LIR

LAN Prefix

IXP Prefix (Not Announced to Peering ISPs)

Log (Number of Allocated Objects)HD Ratio =Log (Max Number of Allocatable Objects)

Desirable HD Ratio = 0.8 .. 0.85 0.8 Picked for New Proposal

Link-Local & Site-Local Unicast


34/94


Addresses, draft-ietf-ipngwg-addr-arch-v3-10.txt

Link-local addresses for use during auto-configuration andwhen no routers are present:

Site-local addresses for independence from changes ofTLA / NLA*:

1111111010 0 interface ID

1111111011 interface IDSLA (54 bit)


35/94


IPv6 and DNS

PTR record:2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.8.1.c.0.0.0.b.0.e.f.f.3.ip6.int. PTR www.abc.test.

(experimental)\[x3ffe0c000c1800010000000000000002 /128].ip6.arpa. PTRwww.abc.test

AAAA record:www.abc.test AAAA

3FFE:B00:C18:1::2

A6 record (now experimental)

www.abc.test A6 0 3FFE:B00:C18:1::2

IPv6

PTR record:

1.30.168.192.in-addr.arpa. PTRwww.abc.test

A record:www.abc.test

A 192.168.30.1

IPv4

Hostname

to IPAddress

IP Addressto Hostname


36/94


One Domain Name System

Every IP device must have a domain name

Nobody wants to type an IPv6 address

Sub-domain offers the Region/Applications flexibility

Today, no root DNS server can answer over an IPv6transport

Transition rules require more developments as dual-stack is a realchallengemore thinking is needed

Preferred protocol version has to be defined for applicationsdual-stack servers

Uniqueness can only be guaranteed by keeping one andonly one root

Non-unique domain name has also legal issue, e.g. inadequatewww.cisco.com registration
http://www.cisco.com/http://www.cisco.com/http://www.cisco.com/


37/94


Multicast Addresses (RFC 2373)

11111111

4 80 Bits8

Group IDFlags

32

0Scope

4

Low-order flag indicates permanent/transient group; three otherflags reserved

Scope field:1node local

2link-local

5site-local

8organization-localBcommunity-local

Eglobal

(All other values reserved)


38/94


Multicast Addresses / RFC3306

64

Group ID00PT Prefix

8 8

Res. Plen11111111 Scope

8 4 324

New flag P:

0address not assigned on prefix

1prefix based assignment

P == 1:

Plenlength of network prefix

Prefixnetwork prefix, at most 64 bitsSSM: plen = 0, prefix = 0

FF3X::/96

See also RFC 3307


39/94


Multicast Listener DiscoverMLD

MLD is equivalent to IGMP in IPv4

MLD messages are transported over ICMPv6

Version number trouble

MLDv1 corresponds to IGMPv2

See RFC 2710MLDv2 corresponds to IGMPv3, needed for SSM

See draft-vida-mld-v2-01.txt

MLD and IGMP are now standardized in the IETFMAGMA working group

http://www.ietf.org/html.charters/magma-charter.html
http://www.ietf.org/html.charters/magma-charter.htmlhttp://www.ietf.org/html.charters/magma-charter.htmlhttp://www.ietf.org/html.charters/magma-charter.html


40/94


IPv6 Multicast Routing

PIM, SSM, MBGP cover IPv4 and IPv6

draft-ietf-pim-sm-v2-new-04.txt,

draft-ietf-ssm-overview-02.txt (SSM needs MLDv2)

RFC 2858

Bidir PIM also applicable Currently no MSDP work for IPv6

Strong doubts that BGMP will ever make it as

inter-domain protocol

For the time being, it is assumed that SSM solvesthe inter-domain IPv6 multicast problem (?)

S it


41/94


Security

IPv6 specifications mandates IPSecTaking benefits of the global address space to allow

end-to-end deployment But

No global IKE distribution mechanism is in place on the

InternetFirewalls are largely in use

Central versus distributed security model

IPv6 helps against DoS/port scansWould take 1M years to do a full /64port scan

M bil IP 6


42/94


Mobile IPv6

Correspondent

MN

HA

Registration

IPv6 RD: Agent Advertisement:

Lifetime, Type, Services

IPv6 RD:

Agent Solicitation:Lifetime, Services

MN

No foreign agent in IPv6 mobile IP Route optimization built-in

Problem was authenticationIPSec AH problems due to missing PKI

IETF mobile IP WG finally coming close to consensusdraft-ietf-mobileip-ipv6-18.txt

Oth IETF IP 6 N


43/94


Other IETF IPv6 News

IPv6 is considered operational now

NGtrans WG EOL

New v6ops WG Multi6 Working group practically dead,

work hopefully continued by v6ops


44/94


IPv6 Deployment Scenarios

IP 6 Deplo ment Scenarios


45/94


IPv6 Deployment Scenarios

Many ways to deliver IPv6 services to end users

End-to-end IPv6 traffic forwarding is the key feature

Minimize operational upgrade costs

Service providers and enterprises may have

different deployment needsIncremental upgrade/deployment

ISPs differentiate core and edge

infrastructures upgradeEnterprise campus and WAN may haveseparate upgrade paths

Integration and TransitionIPv6 IPv4 Communication Mechanisms


46/94


IPv6-IPv4 Communication Mechanisms

Dual-Stack

Translation

NAT-PT (RFC 2766)TCP-UDP Relay (RFC 3142)

DSTM (Dual Stack Transition Mechanism)

API

BIS (Bump-In-the-Stack) (RFC 2767)

BIA (Bump-In-the-API)

ALG

SOCKS-based Gateway (RFC 3089)

NAT-PT (RFC 2766)

Dual Stack Approach


47/94


Dual Stack Approach

Dual stack node means:

Both IPv4 and IPv6 stacks enabled

Applications can talk to both

Choice of the IP version is based on name lookup andapplication preference

TCP UDP

IPv4 IPv6

Data Link (Ethernet)

0x0800 0x86dd

Application

TCP UDP

IPv4 IPv6

Data Link (Ethernet)

0x0800 0x86ddFrameProtocol ID

nservers

IPv6-enable

ApplicationPreferredm

ethodotions

pplica

A

Dual Stack Approach & DNS


48/94


Dual Stack Approach & DNS

IPv4

IPv6

www.a.com

= * ?

3ffe:b00::1

10.1.1.1

DNS

Server

3ffe:b00::1

In a dual stack case, an application that:

Is IPv4 and IPv6-enabled

Asks the DNS for all types of addresses

Chooses one address and, for example, connects tothe IPv6 address

Integration and TransitionNAT PT Overview


49/94


NAT-PT Overview

ipv6 nat prefix 2010::/96

NAT-PTIPv4-only

network

IPv4 Host IPv6 Host

IPv6-only

network

2001:0420:1987:0:2E0:B0FF:FE6A:412C

Src: 2001:0420:1987:0:2E0:B0FF:FE6A:412C

Dst: PREFIX::1

1

2

Src: 172.17.1.1

Dst: 172.16.1.1

3

Src: 172.16.1.1

Dst: 172.17.1.1 Src: PREFIX::1

Dst: 2001:0420:1987:0:2E0:B0FF:FE6A:412C

4

172.16.1.1

PREFIX is a 96-bit field that allows routing back tothe NAT-PT device

Integration and TransitionConfiguring Cisco IOS NAT-PT


50/94


Configuring Cisco IOS NAT-PT

interface ethernet-1

ipv6 address 2001:2::10/64

ipv6 nat prefix 2010::/96ipv6 nat

!

interface ethernet-2

ip address 192.168.1.1 255.255.255.0

ipv6 nat

!ipv6 nat v4v6 source 192.168.1.100 2010::1

!

ipv6 nat v6v4 source route-map map1 pool v4pool1

ipv6 nat v6v4 pool v4pool1 192.168.2.1 192.168.2.10

prefix-length 24

!

route-map map1 permit 10match interface Ethernet-1

DNS

.100

2001:2::1

Network Address Translation-Protocol Translation

RFC 2766

IP Header and Address translation

Support for ICMP and DNS embedded translation

Auto-aliasing of NAT-PT IPv4 Pool Addresses.200

Ethernet-2LAN2: 192.168.1.0/24

Ethernet-1NATed prefix 2010::/96

LAN1: 2001:2::/64

IPv6 TransitionTasks and Methods


51/94



Connect IPv6 nodes with IPv4 nodes

Dual-stacked for servers

NAT-PT close to IPv6-only clients

(do they exist today ??)

Cisco IOS NAT-PT Features


52/94


Cisco IOS NAT-PT Features

NAT-PT support is scheduled for 12.2(5th)T/12.2S

Currently EFT

IP header and address translation

Support for ICMP and DNS embedded translation

Auto-aliasing of NAT-PT IPv4 pool addresses

Future developments will add ALGs support1st implementation does not support FTP ALG



53/94


IPv6 Transition Tasks and Methods

Connect IPv6 islands/nodes over existing

infrastructure with IPv6 nodes

Tunneling: Manually or automagically configured6to4, ISATAP

IPv6 over dedicated link-layer: ATM/FR/SDH/WDM orAToM/L2TPv3

Dual-stacked network

IPv6 over MPLS: 6PE

Integration and TransitionManually Configured Tunnel (RFC 2893)


54/94


Manually Configured Tunnel (RFC 2893)

IPv4IPv6Network

IPv6Network

Dual-Stack

Router2

Dual-Stack

Router1

IPv4: 192.168.99.1

IPv6: 3ffe:b00:c18:1::3

IPv4: 192.168.30.1

IPv6: 3ffe:b00:c18:1::2

router1#

interface Tunnel0

ipv6 address 3ffe:b00:c18:1::3/64

tunnel source 192.168.99.1

tunnel destination 192.168.30.1tunnel mode ipv6ip

router2#

interface Tunnel0

ipv6 address 3ffe:b00:c18:1::2/64

tunnel source 192.168.30.1

tunnel destination 192.168.99.1tunnel mode ipv6ip

Manually Configured tunnels require:

Dual stack end pointsBoth IPv4 and IPv6 addresses configured at each end

Integration and Transition6to4 Tunnel (RFC 3056)


55/94


6to4 Tunnel (RFC 3056)

IPv4IPv6Network

IPv6

Network

6to4Router2

192.168.99.1 192.168.30.1Network prefix:

2002:c0a8:6301::/48

Network prefix:

2002:c0a8:1e01::/48= =

E0 E0

6to4Router1

6to4 Tunnel:

Is an automatic tunnel method

Gives a prefix to the attachedIPv6 network

2002::/16 assigned to 6to4

Requires one global IPv4 address

on each Ingress/Egress site

router2#

interface Loopback0

ip address 192.168.30.1 255.255.255.0

ipv6 address 2002:c0a8:1e01:1::/64 eui-64

interface Tunnel0

no ip address

ipv6 unnumbered Ethernet0

tunnel source Loopback0

tunnel mode ipv6ip 6to4

ipv6 route 2002::/16 Tunnel0

Integration and Transition6to4 Relay


56/94


6to4 Relay

IPv4IPv6Network

IPv6

Network192.168.99.1

Network prefix:2002:c0a8:6301::/48

IPv6 address:

2002:c0a8:1e01::1=

6to4Relay

IPv6Internet

router1#

interface Loopback0

ip address 192.168.99.1 255.255.255.0

ipv6 address 2002:c0a8:6301:1::/64 eui-64

interface Tunnel0no ip address

ipv6 unnumbered Ethernet0

tunnel source Loopback0

tunnel mode ipv6ip 6to4

ipv6 route 2002::/16 Tunnel0

ipv6 route ::/0 2002:c0a8:1e01::1

6to4 relay:Is a gateway to the rest of

the IPv6 Internet

Default router

Anycast address (RFC 3068) for

multiple 6to4 Relay

6to4Router1

ISATAP


57/94


ISATAP

Intra-Site Automatic Tunnel Adressing Protocol

Connect IPv6 nodes to IPv6 routers within apredominantly IPv4 environment

Ideal for sparse distribution of IPv6 nodes

E.g. Campus Networks with IPv4-onlyL3-Switches

See draft-ietf-ngtrans-isatap-04.txt(Fred Templin, SRI, co-authored by Cisco)

ISATAP Details


58/94


Use IANAs OUI 00-00-5E and encode IPv4address as part of EUI-64

Automatic discovery of ISATAP routers

DNS "isatap.domainname" A record lookup

Automatic deprecation when end system receivesnative IPv6 router advertisements

Interface

Identifier(64 bits)

IPv4 Address64-bit Unicast Prefix 0000:5EFE:

32-bit32-bit

Integration and TransitionISATAP


59/94


IPv4

Network2001:0420:ACAC:3101:0000:5EFE:C0A8:640A

IPv6

Network

ISATAP-gw

192.168.99.1

E0

192.168.100.10

6to4 Tunnel:

Is an automatic tunnel method

Ideal for sparse distribution, e.g.Campus

Supported in Windows XP Pro SP1

Supported in Cisco IOS EFT

ISATAP-gw#

interface Ethernet0

ip address 192.168.99.1 255.255.255.0

interface Tunnel0

ipv6 address 2001:0420:ACAC:3101::/64 eui-64

no ipv6 nd suppress-ra

tunnel source Ethernet0

tunnel mode ipv6ip isatap

IPv6 over IPv4 Tunnels Case Study


60/94


y

IPv6 over IPv4

Tunnels

IPv6 Site A

IPv6 Site B

U N I V E R S I T YU N I V E R S I T Y

6Bone

IPv6 IX

ServiceProvider

IPv4 Backbone

ISP scenarioConfigured tunnels between IPv6core routers

Configured tunnels to IPv6customers

MP-BGP4 peering withother 6Bone users

Connection to an IPv6 IX

6to4 tunnels toIPv6 customers

6to4 relay service

Enterprise scenario6to4 tunnels between sites

ISATAP in campusConfigured tunnels betweensites or to 6Bone users

Home

6to4

Native IPv6 over Dedicated Data Links


61/94


Native IPv6 links over dedicated infrastructure

ATM PVC, dWDM Lambda, Frame Relay PVC, Serial,SONET/SDH, Ethernet

All of the above are supported on Cisco IOS 12.2T, aswell as Cisco 12000 Internet series routers

Same applies to UTI or AToM

No impact on IPv4 infrastructure

Only upgrade the appropriate network paths

IPv4 traffic and revenues are separated from IPv6 Network management done through IPv4

OpEx?

Cisco IOS Dual Stack Configuration


62/94


g

router#

ipv6 unicast-routing

interface Ethernet0ip address 192.168.99.1 255.255.255.0

ipv6 address 2001:410:213:1::/64 eui-64

Dual-Stack

RouterIPv6 and IPv4

Network

IPv4: 192.168.99.1

IPv6: 2001:410:213:1::/64 eui-64

Cisco IOS is IPv6-enable:

If IPv4 and IPv6 are configured on one interface, therouter is dual-stacked

Telnet, Ping, Traceroute, SSH, DNS client, TFTP,

Dual Stack IPv4-IPv6 Infrastructure


63/94


Seems to be a natural approachbut

On WAN, is generally a long term goal, when IPv6traffic and users will be rapidly increasing

On LAN: No L3 switches support IPv6 today

Can be configured on Cisco IOS >12.2(2)T/12.0(19)ST but have to consider

Memory size for IPv4 and IPv6 routing tables

IGP options: Integrated versus ships in the night

Full network upgrade

IPv4 and IPv6 traffic should not impacteach other

Require more feedback and experiments

IPv6 over MPLS Infrastructure


64/94


Service Providers have already deployed MPLS

in their IPv4 backbone forvarious reasons

MPLS/VPN, MPLS/QoS, MPLS/TE, ATM + IP switching

Several IPv6 over MPLS scenariosIPv6 over AToM (no impact on IPv6)

IPv6 provider edge router (6PE) over MPLS

(no impact on MPLS core)Native IPv6 MPLS (require full network upgrade)

IPv6 over AToM (Same for UTI)


65/94


v6v6P

P

Eth

AToM

(E.g. ATM VC, FR PVC, Ethernet)v6

PE

PEPE

PE

Circuit

IPv6

IPv6

v6

IPv6

Routers

IPv6 IPv6

No impact on existing IPv4 or MPLS Core (v6 unaware)

Edge MPLS routers need to support AToM

Mesh of PE-to-PE connections

PE routers can be regular IPv6 routers (V6 over ATM, v6 over

FR, v6 over Ethernet) or forward just the L2 VC (e.g. Ethernet)to the IPv6 router

Native MPLS Support of IPv6


66/94


Core infrastructure requires full control plane upgrade to IPv6

IPv6 routing in core

IPv6 label distribution protocol in core

Dual control plane management if IPv4 and IPv6 services

P

P

IPv6

MPLS Label Switch Paths for IPv6

IPv6

All Routers Are

IPv6-Aware

IPv6 MPLS

v6

v6

v6

v6IPv6

IPv6

IPv6

IPv6 Provider Edge Router (6PE) over MPLS


67/94


P P

PP

6PE6PE

v6v4

v4 IPv4MPLS

CE

CE

CE

2001:0421::

2001:0420::

145.95.0.0

2001:0621::

2001:0620::

6PE6PE

IPv6 IPv6

v6

v6 v6

CE v4 192.254.10.0

Dual StackIPv4-IPv6

Routers

Dual Stack

IPv4-IPv6

Routers

MP-iBGP Sessions

192.76.10.0

IPv4 or MPLS core infrastructure is IPv6-unaware

PEs are updated to support dual stack/6PE

IPv6 reachability exchanged among 6PEs viaiBGP (MP-BGP)

IPv6 packets transported from 6PE to 6PE inside MPLS

6PE Overview


68/94


P P

PP

6PE6PE

v6v4

v4CE

CE

CE

2001:0421::

2001:0420::

6PE6PE

v6

v6 v6

CE v4 192.254.10.0

Dual StackDual Stack

MP-iBGP Sessions2001:0620::

145.95.0.0

2001:0621::

192.76.10.0

V6:

IGP/BGP

V6:

IGP/BGP IGPv4MPLS V4:

LDPv4

(TE v4)

IPv6 Unaware

No Core Upgrade

6PE Routing


69/94


6PE-2

6PE-1

P1P2

192.254.10.17

192.72.170.13

Translation of v6 BGPNext_Hop into v4address

Recursion of thisaddress via IGPv4

MP-BGP Advertises 2001:0421::::and Binds a (2nd Level) Label

IPv6 Next Hop Is an IPv4 Compatible IPv6 AddressBuilt from 192.254.10.17

LDPv4 Binds Labelto 192.254.10.17

2001:0421::

IGPv4 Advertises

Reachability of192.254.10.17

2001:0420::

6PE Routing/Label Distribution


70/94


6PE-2

6PE-1

P1 P2

2001:0420::

192.254.10.17

192.72.170.13

IGPv6 or MP-BGP

Advertising

2001:0421::

IGPv6 or MP-BGPAdvertising

2001:0421::

LDPv4 Binds Labelto 192.254.10.17

6PE-2 Sends MP-iBGP Advertisement to 6PE-1 which Says:

2001:0421:: Is Reachable

via BGP Next Hop = 192.254.10.17 (6PE-2)

Bind BGP Label to 2001:0421:: (*)

IGPv4 Advertises Reachabilityof 192.254.10.17

2001:0421::

(*) The 2nd Label Allows Operations with Penultimate Hop Popping (PHP)(which Is Typically Used in Current MPLS Networks)It Is an Aggregate Label

6PE Forwarding


71/94


6PE-2

6PE-1

P1 P2

2001:0421::

192.254.10.17

192.72.170.13IPv6 Packet

to 2001:0421::

2001:0420::

6PE Forwarding (6PE-1)


72/94


6PE-2

6PE-1

P1P2

192.72.170.13

192.254.10.17

IPv6 Forwarding andLabel Imposition:

6PE-1 receives an IPv6 packet

Lookup is done on IPv6 prefix

Result is:

Labelz Binded by MP-BGPto 2001:0421::

Label1 Binded by LDP/IGPv4

to the IPv4 Addressof BGP Next Hop (6PE-2)

LDP/IGPv4Label1 to

6PE-2

IPv6 Packetto

2001:421::

MP-BGPLabel to

2001:421::

IPv6 Packet

to 2001:0421::2001:0421::

2001:0420::

6PE Forwarding (P1)


73/94


6PE-2

6PE-1

P1

192.72.170.13

192.254.10.17

P2

IPv6-UNaware MPLSLabel Switching:

P1 receives an MPLS packet

Lookup is done on Label1

Result is Label2

LDP/IGPv4Label2

to 6PE-2

IPv6Packet to2001:421::

MP-BGPLabel to

2001:421::

IPv6 Packet

to 2001:0421::2001:0421::

LDP/IGPv4Label1 to

6PE-2

MP-BGPLabel to

2001:421::

IPv6 Packetto

2001:421::

2001:0420::

6PE Forwarding (P2)


74/94


6PE-2

6PE-1

P1

2001:0420::

192.72.170.13

LDP/IGPv4Label1 to

6PE-2

MP-BGPLabel to

2001:421::

192.254.10.17

P2

LDP/IGPv4Label2

to 6PE-2


MP-BGPLabel to

2001:421::

IPv6-UNaware MPLSLabel Switching:

P2 receives an MPLS packet

Lookup is done on Label2

Result includes pop label (PHP)


MP-BGPLabel to

2001:421::

IPv6 Packet

to 2001:0421::2001:0421::

IPv6 Packetto

2001:421::

6PE Forwarding (6PE-2)


75/94


6PE-2

6PE-1

P1

192.72.170.13

LDP/IGPv4Label1 to

6PE-2

MP-BGPLabel to

2001:421::

192.254.10.17

P2

LDP/IGPv4Label2

to 6PE-2


MP-BGPLabel to

2001:421::


MP-BGPLabel to

2001:421::

IPv6Packet to

2001:421::

MPLS Label Pop andIPv6 Forwarding:

6PE-2 receives an MPLS packet

Lookup is done on Label

Result is:

Pop the Label and Do IPv6 Lookupon IPv6 Destination

IPv6 Packet

to 2001:0421::2001:0421::

IPv6 Packetto

2001:421::

2001:0420::

6PE configuration


76/94


ipv6 cef

mpls label protocol ldp

mpls ipv6 source-interface Loopback0mpls ldp router-id loopback0

!

interface Loopback0

ip address 10.10.20.2 255.255.255.255

ipv6 address 2003::/64 eui-64

!

router bgp 100

no synchronizationno bgp default ipv4-unicast

bgp log-neighbor-changes

neighbor 10.10.20.1 remote-as 100

neighbor 10.10.20.1 update-source Loopback0

!

address-family ipv6neighbor 10.10.20.1 activate

neighbor 10.10.20.1 send-labelredistribute connected

redistribute rip ripv6CE1

exit-address-family!

6PE

PStaticv6RIPv6

ISISv6

eBGPv6

6CE

ip cef

mpls label protocol ldp

tag-switching tdp router-id

loopback0!

interface Serial2/0

ip address 10.10.10.2

255.255.255.252

ip router isis

mpls label protocol ldptag-switching ip

!

6PE Standardization


77/94


See :BGP Tunnelling

Co-authored by Cisco Generic solution for transport of IPv6 over any

tunnelling technique (including MPLS) using MP-

BGP

IETF working group document

6PE is Cisco IOS implementation of BGPTunnelling over MPLS

FCSed on Cisco 12000 series with Cisco IOS

12.0(22)S, on Cisco 7200/7500 with 12.2(11)S

So What ?


78/94


Home Users

6to4, future: native IPv6

Enterprises

Start with Configured Tunnels, ISATAP

future: Dual-Stack SP

Offer 6to4 & 6to4 relay, future: native IPv6

Configured Tunnels, 6PE

Future: Dual-Stack & 6PE


79/94


IPv6 @ Cisco

Cisco IPv6 Initiative


80/94


Integration and co-existence

As stated in March 2000 at the U.S. IPv6 Forum Telluride

Standardizations involvementIETF IPv6, NGTrans, DHCPv6 WG (co) chair

Control plane focus to build large scale end-to-endinfrastructures

IPv6 deployment is not just a single box consideration

Technology innovation

IPv6 over MPLS (6PE) architectureGMPLS-ready

IPv6 access feature set development to enable IPv6 to thehome deployment

More to be expected

Cisco IPv6 Initiative (Cont.)


81/94


Interoperability verificationand testing

Before 12.2T release, Cisco IOS IPv6 EFT software wasfree access on CCO for 3 years

Cisco IOS IPv6 6Bone connection is operationalsince 10/1996

Participation to TAHI, ETSI interoperability events

Participation to IPv6 showcases in JP

Investment protection

Cisco IOS IPv6 statement of direction published inJune 2000

Cisco IOS routers are IPv6-enabled through

software upgrade

Cisco IPv6 Initiative (Cont.)


82/94


IPv6 Forum member since May 1999

Customers support

Worldwide TAC IPv6 support

IPv6 training available from Cisco learning partners

IPv6 deployment scenarios documented on CCO

Learning and supporting large scale deployment

European 6NET project

ISP trial and commercial services

IT internal deployment

Cisco IOS IPv6: 3 Phases Roadmap


83/94


Market Target

Phase IIIH2 CY 2002 and later

Phase IIIOS 12.2T, 12.2S,

12.0S

Phase IIOS 12.2(2)T, (4)T Early Adopter Deployment

Production Backbone

Deployment

Enhanced IPv6 Services

Cisco IOSRelease

Done

Ongoing

UnderDevelo

pment

Cisco IOS IPv6 Phase I


84/94


IPv6 Features SupportedCisco IOSRelease

Phase IEarly AdoptersCisco IOS

12.2(2)T, (4)T

Any Router Ableto Run 12.2T,

from

Cisco 800 to

Cisco 7500

IP Plus,

Enterprise and

SP images

IPv6 Basic Specification (RFC 2460)ICMPv6, Neighbor Discovery

Stateless Auto-configuration

RIPv6 (RFC 2080)

Multi-Protocol Extensions for BGP4(RFC 2545 and 2858)

Configured and Automatic Tunnels

6to4 Tunnel

Standard Access List

IPv6 over Ethernet (10/100/1000Mb/s),FDDI, Cisco HDLC, ATM and FR PVC,

PPP (Serial, POS, ISDN)

Ping, Traceroute, Telnet, TFTP

Cisco IOSUpgrade

=

Free IPv6

Cisco IOS IPv6 Phase II


85/94


Cisco IOSRelease

Phase IIBackbone

Deployment

EFTN

ow

12.2T, 12.2S, 12.0S

12.0(22)S

12.2(8)T

IPv6 Features under Development

i/IS-ISv6CEFv6/dCEFv6

AAA/Dialer Pool, NAT-PT

Extended Access Control List

IPv6 over IPv4 GRE TunnelsIPv6 Provider Edge Router (6PE)

over MPLS

DNS AAAA client

Link-Local BGP PeeringCDP, SSH, IPv6 MIB

Phase I Sustaining

Extensive Platform Support


86/94


Check latest release number & availability with your local Cisco team

Cisco IOS 12.2TCisco IOS 12.2T

Cisco 800 series Routers




Cisco 2500 series Routers[12.2(4)T]




Cisco 4500/4700 series

Routers [12.2(2)T only]




Cisco IOS 12.0STCisco IOS 12.0ST


Cisco IOS 12.2SCisco IOS 12.2S






Catalyst 6500 series

Cisco IOS Cable RoutersCisco IOS Cable Routers

Cisco ubr7100, ubr7200,

IPv6 over IPv4 Tunnels only

Cisco IOS 12.2Cisco IOS 12.2BB

Cisco 7200, 7400

Cisco IOS IPv6 EFT onlyCisco IOS IPv6 EFT only

AS5300, 5400

Cisco IOS IPv6 Release Trains


87/94


Cisco IOS 12.2T

Current version is 12.2(11)T, no new IPv6 featurescompared to 12.2(8)T

Next release with new IPv6 feature set is 12.2(5th)Tscheduled for Q4 CY02

Cisco IOS 12.2S

New release is 12.2(11)S CCO July 1st, 2002

Cisco IOS 12.0S for Cisco 12000 seriesNew release is 12.0(22)S CCO July 22nd, 2002

Cisco IOS IPv6 Phase II Status


88/94


12.0S/ST

12.0(22)S

12.0(23)S

N/A

12.0(21)ST1

12.0(21)ST1

N/A

12.0(22)S

12.2T

H1 CY03

H2 CY02

H2 CY02

12.2(8)T

H2 CY02

H2 CY02

H1 CY03

12.2S

12.2(11)S

12.2(11)S

H1 CY03

H1 CY03

12.2(9)S

12.2(11)S

IS-IS for IPv6

CEFv6/dCEFv6

Extended ACL

6PE

NAT-PT

Access

MIB


89/94


Conclusion

IPv6Conclusion


90/94


IPv6 Ready for Production Deployment?

Core IPv6 specifications are well-tested and stableSome of the advanced features of IPv6 still need specification,implementation, and deployment work

Application, middleware and scalable deployment

scenario are IPv6 focus and challenge

Service development for service providers

Plan for IPv6 integration and IPv4-IPv6 co-existence

Training, applications inventory, and IPv6 deployment planning

Cisco is committed to deliver advanced IPv6 capabilitiesto the Internet industry

http://www.cisco.com/ipv6 and http://www.cisco.com/go/abc
http://www.cisco.com/ipv6http://www.cisco.com/ipv6http://www.cisco.com/ipv6


91/94


Deploying IPv6 Networks

Session RST-231


92/94


Please Complete YourEvaluation Form

RST-231

Date post:	07-Apr-2018
Category:	Documents
Upload:	sadzvokora
View:	223 times
Download:	0 times

Deploying IPv6 Networks

Documents