IPv6 Made Easy

IPv6 Made Easy
Don Tan
Regional Director - South Asia & India
dtan@bluecatnetworks.com
BlueCat Networks, Inc.
Saturday, May 19, 12

We are no longer an IP
enabled world.
We are IP dependent.

The Idea that
Changed the
World

Early 1970s
— ARPA NET (1971)
— FTP (1971)
— TELNET (1972)

1980s
— 1981: TCP/IP
— 1982: SMTP
— 1983: Domain Names
— 1987: RFC 1035 (DNS Protocol)

1990s
— 1991: HTTP
— 1992: Class Structure
Fails
— 1993: CIDR
— 1994: NAT
— 1995: IP-NG (IPv5)

2000 -
— 2000: Dot-com crash
— 2003: BlackBerry Phone
— 2007: iPhone
— 2010: iPad
— 2011: IANA IPv4 Pool Depleted
— 2011: APNIC Last /8 Allocated

It’s a Numbers Game

4,294,967,296
5,000,000,000
7,000,000,000
It’s a Numbers Game

IPv4 RIR Distribution
AfriNIC
2%
LATNIC
5%
RIPE NCC
22%
ARIN
44%
APNIC
27%

IPv4 RIR Distribution
AfriNIC
2%
LATNIC
5%
RIPE NCC
22%
ARIN
44%
APNIC
27%
Pop: 3.8 B
Pop: 0.5 B
Pop: 0.8 B
Pop: 1 B
Pop: 0.6 B

RIR IPv4 End Date Predictions
ARIN
APNIC
RIPE NCC
LACNIC
AfriNIC
July 2012?
April 15, 2011
Jan 2014?
Oct 2014?
Dec 2013?

What Next?

Think about change

“By 2015, 17% of global Internet users will
be IPv6, with 28% of new Internet
connections running the protocol.”
Gartner, Dec 2010

The World is Changing
17%
419,000,000 Users
(based on 2011 data)

Addresses

340 282 366 920
938 463 463 374
607 431 768 211
456

trillion
decillion
octillion
sextillion
septillion
nonillion
quintillion
quadrillio
n
billion
million
thousand
undecillion
How Big?
340 282 366 920 938 463 463 374 607 431 768
211 456

Subnet Size
— Subnets should always be /64
— Many vendors assume 64 bit boundary
— 18.4 quintillion addresses per subnet
— Perspective:
— 31.5M seconds per year
— 2.4 B seconds in average lifetime
Interface IdentifierAddress Prefix
IPv6 Address

Address Types

Local Link Address
— Bound to local network
— Non routable
— Automatically conﬁgured
— Uses MAC address to create unique address
— Multi-homed devices use “Zones”
Local

Unique Local
— Private within organization
— Similar to RFC 1918
— Routable within organization
— 40-bit pseudo-random number for uniqueness
— Stateful or Stateless allocation
— Can be tunnelled
Unique Local
Local

Global Unicast
— Globally unique
— Public address space
— 42 Undecillion address available
— Preﬁx allocated by RIR/ISP
— Stateful or Stateless allocation
— Provides peer-to-peer connectivity
Global Unicast
Unique Local
Local

More Than Addresses

Extension Headers
— IPv6 Uses simpliﬁed header
— Chains additional headers onto one another
— QoS, IPsec, TCP, UDP and other protocols implemented
as “extension” headers
— Protocol can be extended
— Future friendly
Version Traffic Class Flow Label
Payload Length Next Header Hop Limit
Source Address
Destination Address
IPv6 Header

Neighbour Discovery
— Uses link layer for auto conﬁguration of nodes
— Provides “plug-and-play” network functionality
— Performs:
— Router discovery
— Preﬁx discovery
— Address resolution
— Parameter discovery
— Duplicate address detection

Path MTU Discovery
— Based on IPv4 feature present in many routers
— Functionality moved into core protocol
— IPv6 does not like fragmentation
— Right-sizes MTU for optimized transmission
— Performed dynamically
— Increased throughput

Multicast
— Fundamental shift from IPv4’s broadcast mechanism
— Broadcast not part of IPv6
— Allows networks to scale larger than IPv4
— Puts emphasis on the router rather than the switch
— Can be used to discover services
— Used by DHCP6 and other protocols

Mobile IP
— Documented in RFC 6275
— Allows forwarding of traffic from a “care of” address
— Maintains session when joining new networks
— Still experimental status
— Currently complicated to implement
— Will become more important as everything becomes
mobile
— LISP might be better alternative for some

Quality of Service (QoS)
— Greater ﬂexibility for managing QoS
— Implemented as an extension header
— Currently QoS in IPv6 is same as IPv4
— Has ability to provide better ﬂow control
— Future implementations will utilize more effectively

IPsec
— Part of core protocol
— Developed in conjunction with IPv6
— Applications to provide VPN functionality
— Implemented as extension header
— Changes security in IPv6
— Encrypt IPv6 tunnels

How good is
your
memory?

10.4.83.72

2001:fecd:ba23:cd1f:dcb1:1010:9234:4088

dcb1:1010:9234:408b
dcb1:1010:9234:4a88
dcb7:1010:9234:4088
dcb1:101a:9234:4088
dcb1:1010:9234:5088
dbc1:1010:9234:4088
dcb1:1010:9234:4088
dcb1:1010:8234:4088
dcd1:1010:9234:4088
dcb1:7010:9234:4088
dcb1:1011:9234:4088
Needle in a Hay Stack

Management is Key

Addresses are
not human
friendly

Allocation patterns
are sparse

IPAM key
transition
technology

Why do I need to Change?

Maintain
connectivity with
the rest of the world

Killer Apps will
fuel change

Cloud applications
require more addresses

IPv4 will move into legacy status

Challenges

Addresses will
become hidden

DNS will become
more important.

Peer-to-Peer
connectivity
will be difficult
to accept

Security will be
different

Tunnelling can be complicated.

Conclusions

IPv4 will run out
sooner than
expected

Transitioning
to IPv6 will
require a well
thought-out
plan

Peer-to-Peer
will change how
we build
applications

Networks will
become more ﬂexible

Addresses will
no longer be a scarce
resource

Questions ?

About BlueCat Networks
24x7
Coverage
Highest Rating
Possible
5
Hour On-site
Hardware Repair
Go-to Enterprise
Vendor
95%
Customer
Satisfaction
120
Partners
37%
Revenue Growth
2000
Customers
Strong Alliances

Special Offer for All Attendees
Attend Our Complimentary IPv6 Technical Seminar:
Getting Started with IPv6
‣Instructor-led 3-hour virtual seminar
‣Learn the basic concepts of IPv6
‣Lay the groundwork for IPv6 success
Watch your email for an invitation and voucher code to
redeem online during registration

Thank You

IPv6 Made Easy

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Empfohlen

Empfohlen (20)

IPv6 Made Easy