Durga Prasad AlladaDurga.allada@gmail.comDurga.allada@ieee.orgPh: +91 9880494945

March 2013

Trends, Directions and Considerations for Ipv6

2

Agenda• Why IPv6?• A Proven Methodology for Migrating to IPv6• Strategic Opportunity Areas for Ipv6 Migration• Considerations for App Migration to /.Dev in IPv6• IPv6 Migration Case Studies• It is not a question …. It is the Answer • IPv6 Is…..• Busting the Myth• The starting Point… the Journey… the Destination• The Mile Stones On The Way• Planning• What if Everything is not Ready• Executing• Connecting• Circumvent The Roadblocks

3

Why IPv6?

For Next generation Networks

No need to hide Many Hosts behind a Limited IP

New Apps ( IPT, Multi-Media, Games, Ecommerce

Enhanced Mobility support

Enhanced UX,

Smart Dev

Social Media

Digital Life

Universal Connectivity

Transportation Habitat

Education Utility Services

Financial InstitutionsHealth care

Applications in various Domains

More Devices,

More Hosts

More Applications

increased NW pervasiveness

Address Space from 2^128

Scoped Address

Guarantees (Best effort Service Assured QoS

Enhanced Security

Multi Homing

Flexible methods to change ISP

Connection survivability for a Mobile node

Mobile IPv6

Eliminate use of NAT

Improved and more efficient Routing

Reduced management

4

A Time tested Methodology to move to IPv6

Evangelize

Enable

Execute

Assess

Analyze

Empower

Extend

IPv6 BenefitsMigration ApproachStrategic Focus areas

End-user / Orgn/ISP

Pilot/PoC in identified AppCOE/Innovation Centers

Enable complete Ipv6 Environment

Hand Hold and Hand OverPilot-Shadow- Pass Steering

As-is -> To-BeImpact ReviewData collection and AnalysisMigration Strategy

(For Infra and Apps)

5

Migration Assessment and Implementation services

Applications of Utility Services Companies Service provider Infrastructure (Current IPv4) Current e-Commerce Scenarios

Migration and Implementation Services for

Public / Citizen/ Stake Holder Facing portals Applications Of Government Agencies PSUs and Banks and Financial Institutions

New Ipv6 Arch , Design and deployment

e- Governance, e-Society Services Smart Grids Smart Buildings &Energy Mgmt. Transportation and Public Transport

New Ipv6 Arch , Design and deployment

Mobile and Fixed line convergence Tele-Medicine, Tele Radiology, Emergency Response Digital Class Rooms Digital Convergence

Strategic areas for IPv6 Move for faster RoI

6

Considerations in App Migration/Dev in IPv6

Our Experience 15 Primary Attributes/Factors 35 Sub Attributes/Factors

Build/develop Code that is not dependent on IP address Space in App

Drivers, APIS, Interfaces, DB Tables etc.

Make use of language APIs java, C, Perl

Do away with use of NAT.

Ensure Equipment in place or refreshed supports IPv6

Protocol Considerations Analyze and define / Establish Address Schemes, assignments, Tables

7

In last Decade

A Decade+ ago

This Decade

NowTomorrow

Oh! Some

thing new coming

Let us see when we reach

there

Not a Must Ipv4 works!!

Reaching a Y2k like scenario

IPv6 is a must and

need

"It's something of a broccoli technology, in that regard: It's better for you if you eat but it's not necessarily appealing in its own right.“

IPv6 is not the Question ……. It Is The Answer

8

IPv6 is

Proven as ready for mainstream development

Deployment needs planning and takes time and effort

Can be an opportunity, if implemented in time and is a risk, if missed

Go IPv6 Way………. Now

9

Busting the Myth

We can't migrate because most of the internet still uses IPv4

This isn't about migrating. This is about adding IPv6 capabilities to your IPv4 capabilities.

No business case .Where's the ROI? Same business case as insurance or disaster recovery. There's no immediate profit in it, but, insufficient preparation is a bet-the-company decision. The ROI is being able to continue servicing your customers when they are forced to IPv6,

IPv6 is Hard It can be,Alternatives like layered NAT and other very complex network topologies. is much harder to support than IPv6, and are much less reliable service with more limitations.

IPv6 is not as secure as IPv4+NAT Largely illusory. Attributed to NAT is provided by "Stateful Inspection". IPv6 has "Stateful Inspection”, but, not necessary to usewhile it works well enough for many applications, comes at a price. NAT doesn't add security, it removes functionality. With IPv6, without NAT, you have the choice about which hosts are and are not reachable on your network. With NAT, that choice is significantly limited.

10

Busting the Myth

IPv6 needs a killer App, to catch on. A killer App. that would catapult IPv6 adoption forward, IPv6 is getting deployed as it stands.

The reality is that we need enough addresses to support existing applications.

Today's internet is the killer app. for IPv6.

The choice then becomes whether to deploy IPv6 before that happens vs. waiting until your customers are having poor user experience because they only have IPv6 addresses and your services are unreachable or degraded by translation schemes

Carrier Grade NAT will extend IPv4 The00 experiments that have been conducted with CGN show some promise, but, generally, provide greatly degraded services compared to what IPv4 users expect today. In general, supporting CGN will likely cost more and provide less functionality with more complex troubleshooting than native IPv6 dual-stack.

11

The STARTING POINT ….. The JOURNEY …… The DESTINATION

Projected to be exhausted by 2012

Influenced by

The Projection - By 2004

12

The Mile Stones on The way…….

Technology Revamp Staff Training and Skills

Co-existence Planning Analysis

Deployment Application Refresh User experience

Address Space allocation

13

Planning

Like any major change, adding IPv6 capabilities to an environment requires planning. The amount of planning required depends on many factors, including:

Size and complexity of the environment

Number of users affected

Production Impact(s)

Customer impact(s)

Extent of changes needed

In house software

Systems

Hardware

Vendor Software upgrades

Software Vendors that are not yet IPv6 ready

Change Management Procedures

Staff Training Requirements

Testing

Resources to build development and test lab(s)

Test Plans and methodology

Successful Test Exit criteria

14

What if everything isn’t ready?

Some things may be show-stoppers.  Other things may be able to continue on for quite some time without requiring IPv6 support

Things you want IPv6 ready before customers/users depend on IPv6 in your environment:

Monitoring Systems

Logging and Billing Systems

Firewall/Intrusion Detection/Other Security Systems

Most, if not all routers and other network infrastructure

Support Department systems

Not necessarily everyone’s desktop, but, at least enough to be able to do IPv6 support.

Things that can wait:

Third party applications (in most cases)

Printers and other peripherals

Desktop Systems

Laptops

VPNs (usually)

etc.

15

Executing

The general process for change will depend a great deal on the specific needs and planning

Generally, the order will look something like this:

based on the priorities and requirements of the environment, availability of resources, and timing of maintenance opportunities.

1.Initial deployment/support staff training

2.Development work/lab

3.Test lab

4.External Connectivity

5.Network Infrastructure, Firewalls, Intrusion Detection Systems, and other Security devices

6.Domain Name Servers and Resolvers

7.Support Department(s)

8.Additional Support Staff training

9.Servers and/or Desktops (in stages, order dictated by local concerns)

10.User training (if applicable to your environment)

11.VPNs

12.Others

16

How to Connect

:

Seek Ipv6 Connectivity addresses from Same ISP from where you got IPv4 Connectivity addresses

IPv6 Tunneling wrapped in IPv4

Single host Semi-automatic Solutions (6to4, Teredo)

ISP may not be providing IPv6

Temporary Solution Performance impact Automatic process once configured

Limited options and limited operations / use

17

Circumvent Road Blocks

Technology

Dual Stack, TunnelingHomogenous IPv6Technology UpgradeAdd Ipv6 Features in existing HWFocus on phased feature UpgradeInclude Computing HW capabilities for Ipv6 in AnalysisLatency Issues – Low Latency networks and NW GearSpoke and Hub Model + NAT+ No of Hops

Services And Applications

Deploy Apps with a defined RoadmapUser facing, front end Portal AppsMedium Business critical App setBusiness Critical Apps set, after well established fall back planApplication (Code) readiness Analysis and AssessmentIn-house Apps

External Influencers

3rd party managed/supplied AppsThird Party Integration (payment gates ways, International Finance Systems)Regulatory and Statutory Compliance and InfluencersSecurityExtending Service capabilities (Mobile, On move Banking, Smart world)