IPV6 @ Tata Communications Ltd.

(VSNL)
Shailesh Gupta, Vice President Raju Raghavan, Manager

Contents
Tata Communications ISP Network Journey since Aug15th, 1995 Advantages of IPV6 over IPV4 IPV6 Drivers & design in TCL Network IPV6 Customers of TCL, India Expectations from GOI/DOT/TEC for promoting IPV6 in India Thanks

TCL Global Network

TCL - 3-Gig

London Dallas Palo Alto New York New Jersey Madrid

Amsterdam Frankfurt Paris Dubai EMIX-2 x DS3

NTT-GIG TCL -2 fGig Google - Gig

KDDI-2XDS3

Tokyo PLDT-DS3 CT -DS3 Mumbai

China
Hong Kong

Santa Clara

Chicago

TCL -7xGig

TCL -8xGig TCL -4xSTM4 TCL - 2*10GIG Google-3Gig Ernakulam

GoogleChennai 3Gig Singapore

Korea Telecom STM1 STM1

5
CAT Thailand DS3

Colombo TCL -4xSTM16 TCL 2*10GIG

TCL -2xSTM-4

Singtel-STM1 TM-DS3 CHT-DS3

Sydney

MSN-Gig

SMW-3 TAT-14 AC-1 PEB TIC SAFE+TM+APCN-2+J-US Reach IPLC

* Dual stack edge and core . ** Independent core topologies for IPv4 and IPv6

International Connectivity

FLAG SEA-ME-WE3
Kolkat a

MUMBAI

CHENNAI SEA-ME-WE2 COCHIN SEA-ME-WE3

SEA-ME-WE4 Network(RFS by Mid Rights Administration 2005)

TATA Indicom Chennai, India India Singapore Cable 5.12 Tbps System

Atlantic Route
Submarine Cable & Carrier Level Redundancy TATA Indicom is the Only Carrier having capacity on 5 out of 5 cables into India

Pacific Route Pacific route

SINGAPORE

SAFE

Tata Communications - India Network Footprint

Its all about connectivity ....All Over India

117 location across the the India. 3-tier Hierarchical topology for better management. 9 Big Tier 1 cities including 4 metros 7 Major Tier 2 cities. 101 Tier 3 cities

* Serves the length and breadth of India. ** IPv6 Dual stack edge with MPLS tunneled core.

International Bandwidth Growth (Mbps)

International Usable Bandwidth

Usable Bandwidth 80000 70000 60000 50000 40000 30000 20000 10000 0

73000 55000 40000 800010928 4800

6 Fe b' 07 H2 09 20 08 20 09 20

0.064 10
n'9 6

24
n'9 7

69 211 666 816 834 848 1160 2480

n'9 8 n'0 0 n'0 3 n'0 4 n'9 9 n'0 2 n'0 5 1 Fe b'0

g'9 5

n'0 6 Ja

Au

1140625 times growth in 15 Years

De

Ja

Ja

Ja

Ja

Ja

Ja

Ja

Ja

Ja

c'0

IPV6 Pool allocated to TCL from APNIC

IPv6 Drivers and design in the TCL network.

A perspective on Global IPv6 Business drivers:

Global IPv6 Routes Global IPv6 ASes

The IPv6 routes in the global routing table has grown from 500 prefixes in 2004 to around 1200 prefixes in 2008. The IPv6 ASes in the global routing table has gone from 400 ASes in 2004 to around 900 ASes in 2008. A two fold increase. (IPv4 ASes - 28000 )

One of the prime drivers for IPv6 adoption globally has been Service Differentiation and the pursuit of competitive advantage (First Mover).

IPv6 Technical strengths over IPv4:

Variable Length
Fixed Length of 40 bytes = no length field

13 Fields
Remove unwanted header fields Simple header.

8 Fields

Less fields means lesser processing good for devices which have lesser processing power?

IPv6 Technical strengths over IPv4: Key Highlights:

Quality of service Model Enhancements

Preserve existing DiffServ model Plus Flow Label More granularity in classifications based on flows.

Plug and Play Architecture:

IPv6 is designed with plug and play in mind. Stateless Auto configuration auto IP Addressing (In the absence of a DHCP server). Link Local auto generated address.

Tata Communications IPv6 Enabled networks overview

o TCL India Network:

Serves the length and breadth of India. IPv6 Dual stack edge with MPLS tunneled core.

o TCL Global network:

Dual stack edge and core . Independent core topologies for IPv4 and IPv6.

Tata Communications India model | IPv6 deployment Model :

We had to choose a mechanism that helps in seamless migration without disrupting existing services. The TCL network is end to end MPLS enabled.
The obvious choice was to tunnel IPv6 packets over MPLS using the 6PE mechanism.
IPV6 internet
RR

Dual stack enable the PE routers.

TCL IPv4 MPLS Cloud

Establish Connection to IPv6 Internet

IPV6 Customer Network

Enable labeled IPv6 signaling over the BGP session to RR

IPV6 Customer Network

TCL International Network | Dual Stack/Multi Topology:

o o Dual stack Backbone and Edge Routers. Independent topologies for IPv4 and IPv6 to cater to H/W limitations/issues.

Multi-Topology ISIS protocol builds separate topologies for IPv4 and IPv6 A B

- IPv4 Topology - IPv6 Topology

- Dual Stack PoPs

C E D F

A few TCL IPv6 highlights globally over the years:

o TCL promoted the experimentation of IPv6 and the 6bone/6TAP initiative as a member of the Canarie Policy Board. o TCL is a founding member of the IPv6 Forum . o TCL provided IPv6 connection to the last SANOG meeting.

IPV6 Live customers with TCL, India

Tata - NIXI Mumbai connectivity Getting few prefixes from RIC & Netmagic 3 prefixes ,one /48 from NIXI (2001:DE8:1::/48), one each from Netmagic & RIC Honesty (ISP) at Mumbai IIT Kanpur 1 Gb 40+ international IPV6 customers

IPv6 Enterprise Customer Deployment

IPV4 - 3.4 L+ routes in global routing table IPV6 15000 routes in global routing table

Expectations from GOI/Regulator/Licensor

NIR for IPV6 to manage resources in a better way & promote usage of IPV6 in India IPV6 workshop/training for SPs / Corporates. APNIC already organizes such trainings Invite equipment vendors and Applications vendors to collaborate and create a multivendor IPv6 test bed. (This will help in increasing the IPv6 acceptance in the India Enterprises) This should demonstrate IPv6 application interoperability across multiple applications vendors like Oracle, SAP, Windows, Linux, database applications etc., This should demonstrate IPv6 transport interoperability across many IP equipment vendors such as Cisco, Juniper, Huawei Alcatel etc., Free/Subsidized IPV6 session/port with NIXI Extended Support of OEM for upgrading box to support IPV6. IPV6 discussion forum for resolving day-day issues

The more seemingly impossible the goal, the more glorious is the triumph of achievement!

Together we can, together we will!

Backup Slides

1. IPv6 Enterprise Customer Deployment (Honesty, Mumbai)

Customer Expectations: Reachability of customer IPv4 and IPv6 prefixes in Internet Domain. Customer required Full IPv6 route from Tata Communications (15 K) Both IPv4 and IPv6 sessions on same link.

Scenario Customer is having IPv6 prefixes with his own AS number. wants to run IPv6 BGP session with Tata communications on his existing IPv4 link. Customer is already running IPv4 BGP session on same link for his IPv6 Prefixes.

IPv6 Enterprise Customer Deployment

Challenges: Propagating Customer IPv6 prefixes in Internet Domain. ensuring propagation within Tata communication domain ensuring propagation within Tele globe domain. ensuring proper Hand-off between these Two domains. Establishment of IPv6 BGP session and IPv4 BGP session on same link. Configuring proper route-map and IPv6 Prefix lists. Proper network and mask configuration w.r.t. /128 mask to avoid route leakage and improper announcements to Customer as well as to upstream provider. Testing

IPv6 Enterprise Customer Deployment

PE Configs :
interface Vlan2455 description 022100167783/Honesty net solutions (India) Private Limited/Bhandup (West) Mumbai/STDILL/20MB/VBL ip address 115.113.128.85 255.255.255.252 ipv6 address 2403:0:100::1/126 ipv6 enable address-family ipv6 no synchronization network 2403:0:100::/126 neighbor 2403:0:100::2 activate neighbor 2403:0:100::2 prefix-list HONESTY_IPV6 in neighbor 2403:0:100::2 maximum-prefix 1000 100 restart ipv6 prefix-list HONESTY_IPV6: 1 entries seq 10 permit 2401:4800::/32 le 64

Testing:
PE#sh bgp ipv6 sum BGP router identifier 192.168.196.5, local AS number 4755 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 0 0 3w4d 1

2403:0:100::2 4 38457 39935 653236 3495885

IPv6 Enterprise Customer Deployment

Testing:
PE#sh bgp ipv6 unicast neighbors 2403:0:100::2 routes BGP table version is 1572300, local router ID is 192.168.196.5 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 2401:4800::/32 2403:0:100::2 50 0 38457 i *> 2401:4800:1::/64 2403:0:100::2 50 0 38457 i *> 2401:4800:11::/64 2403:0:100::2 50 0 38457 ? Total number of prefixes 3 mu-lvs-lvs-mi01-rt01 ICG#sh ipv6 route 2401:4800:0:21::1 IPv6 Routing Table - 1585 entries Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP U - Per-user Static route I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 B 2401:4800::/32 [200/50] via ::FFFF:192.168.196.5, IPv6-mpls

IPv6 Enterprise Customer Deployment

Testing:
Trace from Looking Glass

Router: gin-mtt-mcore3 Site: CA, Montreal - MTT, TATA COMM. INT. CENTER Command: traceroute ipv6 2401:4800:1::2 Tracing the route to 2401:4800:1::2 1 if-13-0.mcore4.nqt-newyork.ipv6.as6453.net (2001:5A0:300:100::2) 8 msec 8 msec 8 msec 2 2001:5A0:400:100::16 204 msec 200 msec 200 msec 3 2001:5A0:2300:100::6 204 msec 204 msec 200 msec 4 2401:4800:1::2 208 msec 204 msec 208 msec 5 2401:4800:1::2 204 msec 208 msec 204 msec

2. IPV6 Deployment NIXI, Mumbai mu-mhp-vas-mi04-rt01 192.168.132.232 7606 Gi2/13 Tata-Mumbai-Vashi Fibre-to-Elect Convertor(gig) NIXI router 7606

Peering IP:2001:DE8:1::1 ASN : 24029 Note 1:Advertising specific 4755 IPv6 network, 2403::/32 on this session while accepting specific NIXI customer (Reliance & Netmagic) ipv6 n/w with no-export Note2:The ipv6 networks from 6453 (around 1600 prefixes) and 4755 ipv6 n/w available in Mumbai ICG were passed to Vashi Micropop during this implementation to cater NIXI customers as well as our customers

mu-mhp-vas-mi04-rt01#sh run | inc 2001:DE8:1::1 neighbor 2001:DE8:1::1 remote-as 24029 neighbor 2001:DE8:1::1 description ***eBGP IPV6 with NIXI *** no neighbor 2001:DE8:1::1 activate neighbor 2001:DE8:1::1 activate neighbor 2001:DE8:1::1 route-map NIXIV6-IN in neighbor 2001:DE8:1::1 route-map NIXIV6-OUT out neighbor 2001:DE8:1::1 maximum-prefix 1000 100 restart 30 mu-mhp-vas-mi04-rt01#sh route-map NIXIV6-IN route-map NIXIV6-IN, permit, sequence 10 Match clauses: as-path (as-path filter): 100 Set clauses: community 4755:98 4755:2255 no-export Policy routing matches: 0 packets, 0 bytes mu-mhp-vas-mi04-rt01#sh ip as-path-access-list 100 AS path access list 100 permit ^24029$ permit 18101 permit 17439 mu-mhp-vas-mi04-rt01#sh route-map NIXIV6-OUT route-map NIXIV6-OUT, permit, sequence 10 Match clauses: ipv6 address prefix-list TATAV6 Set clauses: Policy routing matches: 0 packets, 0 bytes mu-mhp-vas-mi04-rt01#sh ipv6 prefix-list TATAV6 ipv6 prefix-list TATAV6: 1 entries seq 5 permit 2403::/32

mu-mhp-vas-mi04-rt01#sh run int gi2/13 Building configuration... Current configuration : 381 bytes ! interface GigabitEthernet2/13 description NIXI DEMO LINK FOR ipv6 TEST | Direct Physical connection to NIXI witch through Tata owned Opt-to-Elect Convertor | 16Dec08 no ip address ipv6 address 2001:DE8:1::3/64 ipv6 enable wrr-queue cos-map 3 1 7 priority-queue cos-map 1 5 6 rcv-queue cos-map 1 4 1 3 rcv-queue cos-map 1 6 0 2 4 7 rcv-queue cos-map 1 8 5 6 end mu-mhp-vas-mi04-rt01#ping ipv6 2001:DE8:1::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DE8:1::1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/4 ms

Currently, only a /36 (2403::/36) from the Global space has been used. 8 numbers of /40 used for infrastructure and other 7 cities namely Mumbai, Chennai, Ernakulam, Delhi, Bangalore, Hyderabad, Kolkata (excel sheets attached). As per IPv6 LLD we have calculated /40 subnets into smaller subnets to arrive different WAN/loopback and Customer IP E.g. Mumbai 2403:0:100:0:0:0:0:0 /40 subnetted to /48s First 2403:0:100:0:0:0:0:0/48 subnetted to /64s. For customers we will allocate /64 LAN IP. First 2403:0:100:0:0:0:0:0/64 is further subnetted till we get 2403:0:100:0:0:0:0:0 /112 and WAN IP given to first customer. Please go through the IPv6 LLD.

IPv6 business drivers : Future?

Mobile Internet age: Smart Phones? 3G and 4G with high BW internet access would be the drivers? Network Mobility IETF NEMO WG defines IPv6 on mobile networks like IPv6 on Cars etc., ? Refer rfc3963.txt for more information.
Number of IPv6 addresses : If we do some simple math: (Divide the number of IPv6 addresses by IPv4 addresses) 340,282,366,920,938,463,463,374,607,431,768,211,456 (number of IPv6 addresses) 4,294,967,296 (number of IPv4 addresses) = .792 million trillion IPv4 Internets make an IPv6 internet ( from a number of hosts perspective)

IPv6 Technical strengths over IPv4: Granular QoS:

Diffserv / IP Precedence

Diffserv / IP Precedence

Flow Label (20 bits):

Identifies application
More granularity and differentiation

flows Per flow QoS for next gen applications

IPv6 Strengths : Plug and Play:

IPv6 supports plug and play with stateless auto configuration.
Reboot

Router Solicitation = Please send subnet prefix.

Src= Link Local Address (FE80::/10) Dst = All routers multicast address (FF02::2)

L A Router Advertisement = Subnet Prefix (IPv6 prefix), lifetime and N

IPv6 Host

autoconfig flag.

Src= Link Local Address (FE80::/10) Dst = All nodes multicast address (FF02::1)

IPv6 has link local addresses, so on a local lan even without any protocol exchanges the IPv6 can start communicating.

IPv6 prefix and traffic flow in the Tata Communications network:

The Label 10 and the IPv6 prefix 2403:1::/48 is advertised to the remote PE with IPv6 mapped next hop :FFFF:192.168.1.1

A label is generated for the IPv6 prefix = Label 10

Customer Advertises an IPv6 Prefix : 2403:1::/48

TCL IPv4 MPLS Cloud RR MP BGP

BGP Update source IPv4 address = 192.168.1.1

BGP Update source IPv4 address is converted to IPv6 mapped address ::FFFF:192.168.1.1

IPv6 prefix and traffic flow in the Tata Communications network:

PoP MPLS Labels Send IPv6 packet to CPE.

IPv6 Packet

The destination PE installs the route in the routing table with ::FFFF.192.168.1. as next hop.

TCL IPv4 MPLS Cloud RR MPLS Labels MP BGP

IPv6 Packet

BGP label is configured as Inner label

The IGP label corresponding to ::FFFF.192.168.1.1 (192.168.1.1) is configured as the outer label .

IPv6 Packet