IPV6 Advances and Deployments

1
IPV6 Advances and Deployments
Think Ahead ...... ..... Stay Ahead
LOGO

• Regional Seminar on IP Communications
• 24-25 November 2008
• Hammamet, Tunisia

Alaa Al-Din (Aladdin ) Jawad Kadhem Al-Radhi
Consultant Engineer and Researcher
alradhi2000_at_yahoo.ca alaalradhi_at_hotmail.com
962 796347600
2
Contents
1
Background
2
IPv4 address space is running out
3
The solution IPv6
4
IPv6 Main differences than IPv4
5
IPv6 Addressing
6
Living in 2 Worlds IPv4 IPv6
7
IPv4 to IPv6 Transition
8
Migration Checklist
9
IPv6 Global Deployment Status
10
IPv6 Research Promoters
11
ITU highlights on IPv6
12
3
Background
1

• Original IPv4 address plan was split in A (/8), B
  (/16), C (/24) ,which was supposed to correspond
  to the different needs of different users
• The address blocks was originally handed out more
  or less arbitrary
• In 1991, 4 things worried the network operators
• Router memory exhaustion due to the number of
  routes.
• The Network Information Centers (NICs) were
  running out of Class B IPv4 addresses to assign
  to new networks.
• Address exhaustion was forecasted within 10-15
  years.
• Network administration was expensive, error prone
  and largely manual due to the lack of
  auto-configuration capabilities.
• Some techniques were used with address shortage
  in IPv4
• Sub-netting
• Classless Inter Domain Routing (CIDR)
• Network Address Translation (NAT)
• In parallel in 1992, discussions about a new
  addressing model and address plan started

4
Face the Fact IPv4 address space is running out!
2
IPv4 Exhaustion Counter
http//potraoo.net/tools/ipv4
5
Face the Fact IPv4 address space is running out!
2
Only 15 of the IPv4 addresses have NOT been
allocated. (39 out of 256 blocks)
http//www.ipv6forum.com/ipv4_exhaustion.php
6
Face the Fact IPv4 address space is running out!
2
http//www.iana.org/assignments/ipv4-address-space

7
The solution IPv6
3

• IPv4 defines a 32 bit, that will give us
  (4,294,967,296) IP addresses, while there were
  550 Million Users on Internet as of 2005!
• Other problems like
• P2P applications Need to reserve an IP address
  to each peer.
• Always-on devices Mobile Phones, ADSL, and
  Intelligent Home ...ect.
• So its time to IPv6 with its many benefits.

8

The solution IPv6 Key Features
3

• 128 bit address space, for IP growth, structured
  for
• Ease of routing
• Deprecating NAT
• IPv4 interoperability
• Nomadic computing (e.g. all cell phones)
• Features
• Stateless auto configuration (Plug and Play)
• Security authentication and encryption ( IPSec)
• Mobility management
• Multicast
• QoS parameters for real-time audio and video.
• Full P-2-P functionality

9
Main differences than IPv4
4
All fields are of a predefined and static
size Faster processing NO Initial Header
Length (IHL) needed Header checksum is
removed Speeds up processing of packets in
intermediary hops, as NO new checksum calculation
is needed Packets can be misrouted due to bit
errors, but the risk is extremely low The
payload often has it own checksums
Fragmentation is gone IPv6 does NOT have a TOS
field The fields have changed names Packet
length -gt Payload length Protocol type -gt Next
header Time to live -gt Hop Limit
10
IPv6 Addressing Format
5

• TWO logical parts
• 64 bit (sub-)network prefix.
• 64 bit host part. (automatically generated from
  the interface's MAC address).

64 Bit Host
64 Bit Sub-Network prefix
11
IPv6 Addressing Types
5

• Unicast ONE-To-ONE It corresponds to a single
  computer. A datagram sent to the address is
  routed along a shortest path to the computer.
• Multicast ONE-To-MANY It corresponds to a set
  of computers. Membership in the set can change at
  any time. When a datagram is sent to the address,
  IPv6 delivers one copy of the datagram to each
  member of the set.
• Anycast ONE-To-Nearest It corresponds to a set
  of computers that share a common address prefix.
  A datagram sent to the address is routed along a
  shortest path and then delivered to exactly one
  of the computers (Cluster addressing). Anycast
  permits replication of services.
• There are NO broadcast addresses in IPv6, their
  function being superseded by multicast addresses.
  

12
IPv6 Addressing Notation
5

• 8 groups of 4 hexadecimal numbers. An example
• 20010db885a308d313198a2e03707334
• 4-digit groups of 0000, can be omitted and
  replaced with two colons( ). An example
• 20010db80000000000000000142857ab
• is equal to
• 20010db8
  142857ab
• A sequence of 4 bytes at the end can also be
  written in decimal, using dots as separator
• In a URL the IPv6 Address is enclosed in brackets
  ( a drawback as it is hard to remember!)
• http//20010db800142857ab/

13
6
Living in 2 worlds IPv4 IPv6

• The two numbering technologies are NOT mutually
  compatible. You must support IPv6 in addition to
  IPv4 to be accessible to IPv6 clients.
• Tunnelling Hide IPv6 inside IPv4 / UDP /
• Translation Convert IPv6 into IPv4
• Proxies Someone speaks IPv6 on your behalf

14
IPv4 to IPv6 Transition Strategies
7

• IPv6 was designed, at the beginning, with
  transition in mind.
• IPv4 and IPv6 are incompatible protocols.
  Transition
• ISPs deploy IPv6 first in the network then
  connect with other ISPs to offer end to-end IPv6.
  Money!
• Then, customers are offered the new IPv6 and
  begins to use it.
• Transition mechanisms are needed for IPv6 only
  host to reach IPv4 services
• Dual stack.
• Node has both IPv4 and IPv6 stacks and addresses
• DNS resolver returns IPv6, IPv4 or both to
  application
• IPv6 application can communicate with IPv4 nodes
• Tunneling.
• Translation.

15
IPv4 to IPv6 Transition Implementations
Challenges
7

• When introducing IPv6 into a network, a number of
  issues might occur
• All hardware in the network might NOT support
  IPv6
• The Internet provider may NOT support IPv6
• The network is behind a firewall (NAT device)
  that does NOT support IPv6
• All applications does NOT support IPv6
• What problems you might encounter is very much
  dependent on what type of network it is

16
IPv4 to IPv6 Transition Implementations
Challenges
7

• IETF , IPv6 WG decided to define a number of
  scenarios
• Enterprise
• ISP
• Applications
• 3GPP
• Campus
• Each scenario specifies problems and requirements
  on the solutions to those problems
• The thought was that based on this, a decision
  could be made between the various transition
  technologies that where proposed

17
IPv4 to IPv6 Transition Tunneling
7

• Static e.g. permanently configured
• Dynamic Dial-on-demand, established when
  needed
• Between
• Host-Host
• Host-Router
• Router-Router

18
IPv4 to IPv6 Transition Tunneling Example 1
7
19
IPv4 to IPv6 Transition Tunneling Example 2
7
20
Migration Checklist 1. Address Application
8

• Apply for addresses from RIPE NCC or your ISP
• Log into the RIPE NCC LIR portal
  https//lirportal.ripe.net
• Go to request forms and IPv6 initial assignments
• After receiving the IPv6 allocation, put the
  appropriate route object into the RIPE database.
• Applying for IPv6 address space from your ISP.
  Most ISPs will give out /48s to end-users, but
  also /56 are becoming common
• Start with assessing your minimum needs
• Assume a /64 per broadcast domain, i.e. / each
  Ethernet / VLAN
• The assessment shall meet your needs for the
  coming two years
• Contact the ISPs to find out what their policy is
  and how you order
• Everything you know about BGP4, Subnet Masks,
  OSPF, Route-Maps, Prefix-lists, AS-Path,
  Filter-Lists..etc is still valid more or less.
• Dual Stack (IPv4 / IPv6 on the same equipment)
  works well.
• Do NOT think of deploying IPv6-Tunnels (unless
  you are a DSL/Cable user).

21
Migration Checklist 2. Make an Address Plan
8

• In the begging you where supposed to run EUI64
  addresses everywhere, and router advertisement to
  announce it
• First of all, try and use the same binary-chop
  method as the RIR / LIRs do, but you can adjust
  it to your own needs. RIPE allocation to the LIR
  is a /32, while customer Assignments are usually
  a /48
• Use a /48 for loopbacks
• Use another /48 for Point-to-Point links
• Always allocate /64 to services
• That is so you can later migrate them to their
  own LANs if you have to
• Do not you use EUI64 address for services
• Allocate static address for services

22
Migration Checklist 3. Inventory
8

• Make an inventory of internal systems and the use
  of IPv4 addresses in internal system
• List workstations
• Servers and services addresses
• Analyze DNS and DHCP servers
• Verify which clients will try and use IPv6 as
  transport
• Can the associated servers reply over IPv6
  transport?
• Are IPv4 used in referrals?

23
Migration Checklist 4. Test to migrate
8

• Make a migration calendar
• Check your IPv6 Connectivity. If you do NOT have
  an IPv6-enabled client, try, for e.g. the tools
  of SixXS
• http//ipv4gate.sixxs.net
• http//www.sixxs.net
• Start to migrate. Good luck!

24
Migration Checklist Things to Remember!
8

• Start with configuring IPv6 addresses on
  infrastructure, such as routers, switches etc.
• Continue to activate IPv6 on services
• Configure IPv6 on clients
• Update DNS
• Can be hard to decide in which order to do
• Will depend on how Client / Serves will handle
  IPv6

25
Migration Checklist Things to Remember!
8

• IPv6 Neighbor Discovery
• Described in RFC 4861
• Used for
• Finding link-layer addresses of nodes on the same
  Link
• Delete state that is no longer in valid
• Find routers that are willing to forward packets
• Verify reach ability on a link

26
Migration Checklist Things to Remember!
8

• Router Advertisement
• Routers announce themselves to a multicast group
  (if the link layer supports it)
• Nodes then listen to multicast announcements
• Includes information on how nodes are expected to
  obtain an address
• Neighbor solicitation
• Nodes ask others to send their link-layer address
• Sent to a multicast group
• IPv6 ND corresponds to IPv4
• ARP
• ICMP redirect
• ICMP router discovery
• Router solicitation Sent by nodes to the routers
  to force more frequent Router Advertisement

27
IPv6 Deployment Status Global Perspective
9
28
IPv6 Research Promoters Examples
10

• IPv6 Forum http//ipv6forum.com
• IPv6 Task Force http//www.ipv6tf.org/
• EU 27/5/08 issues on IPv6 promoting 1
• OECD 7/3/08 on the IPv4 to IPv6 transition 2

1 http//ec.europa.eu/information_society/poli
cy/ipv6/docs/european_day/comm-ipv6-final_en.pdf
2 http//www.oecd.org/dataoecd/7/1/40605942.pd
f
29
ITU Highlights on IPv6
11
ITU Workshop on IPv6 , 4, 5 September 2008, Geneva

• Inputs from
• ITU Study groups 3 and 2
• 150 participants from over 45 countries, number
  of RIRs, private sector and other organizations.
• Key issues
• Economic aspects of IP address allocation (
  tariffs, secondary markets, migration costs..etc)
• Raise awareness of IPv6 deployment importance and
  opportunities.
• Q/A on international public policy issues of IPv4
  to IPv6 migration.
• ITU future standardization and international
  collaboration roles
• DNS and ICANN roles
• Country cases, for e.g. Bulgaria , china
  Olympics 2008
• Capacity buildings for development countries
• .Others.

http//www.itu.int/ITU-T/worksem/ipv6/200809/
30

• Thank You!

Questions?