This document discusses IPv4 and IPv6. It begins by explaining that IPv4 uses 32-bit addresses while IPv6 uses 128-bit addresses. It notes that while IPv4 and IPv6 can communicate within the same version, communication between the two versions requires transition mechanisms. The document then explains that the original plan was to deploy IPv6 before IPv4 addresses were exhausted, but that IPv4 exhaustion occurred before significant IPv6 deployment. As a result, IPv4 and IPv6 must now coexist and translation between the two versions is necessary. It concludes by discussing some challenges with IPv6 deployment and transition mechanisms between the two protocols.
10. 96 extra bits – no MAGIC
• IPv4 : 4 blocks of numbers separated by dots
• 1.2.3.4
32bit
• IPv6 : 8 blocks of numbers separated by colons
• 2001:2:3:4:5:6:7:8
• v4 to v4, v6 to v6
128bit
no problem, no magic
IPv4
IPv4
IPv4
IPv6
IPv6
IPv6
• v4 to v6, v6 to v4
parallel universes !
10
11. We had a plan....
years ago.......
–
–
–
–
v4/v6 are not compatible on the wire
We cant just add v6
So dual stack everywhere (ie v4/v6)
As v6 increases, we gain critical mass,
v4 quietly goes away
IANA:
Feb 2011
APNIC:
May 2011
RIPE: Oct 2012
11
13. What happened ?
• years ago.......
–
–
–
–
v4/v6 are not compatible on the wire
We cant just add v6
So dual stack everywhere (ie v4/v6)
As v6 increases, we gain critical mass,
v4 quietly goes away
• the reality, today:
– v6 deployment today is sparse at best
– v4 is really running out
– v4/v6 coexistence is inevitable
IANA:
APNIC:
RIPE:
Feb 2011
May 2011
Oct 2012
13
14. The new plan and challenges
Scenario
From
To
How ?
Today
IPv4
IPv4
This is how we work today
Today
IPv4
IPv6
Transition Mechanisms
Future
IPv6
IPv6
Native v6
Future
IPv4 / IPv6
IPv4 or IPv6
Best of both worlds
(Dual Stack)
Future
IPv6 only
IPv4 only
(v4 ran out)
CG NAT/NAT64
(no v6 yet at this network)
14
15. The “Just add more NAT” approach
•
•
•
•
Multi Level NAT
ISP gives out private IPv4 and does NAT again
How far can it scale ?
How much will it break ?
• When does IPv6 start being more appealing ?
16. Transition Mechanisms
• IPv6 through a tunnel in a v4 network
– Dependent on v4
– Tunnels have issues with performance
– But it kind of works
• Various Types
–
–
–
–
6to4
Teredo
ISATAP
6in4
17. The Other Option: use IPv6 !
• Dual stack
• Inevitably v4 will run out before we fully rely
on v6
• So translation is inevitable
18. IPv6: its BIG
18,446,744,073,709,500,000
no, its not the total IPv6 space, that would be
340,282,366,920 billion billion billion
It’s the number of unique v6 IPs in /64
/64 is the minimum space given to an end user
That’s ridiculous!
18 billion billion : /64 in IPv6
7 billion : population of the world in 2014
22. A walk along the v6 internet
1
1 ms
10ge3-1.core1.lon2.he.net (2001:470:0:2cd::1)
2
72 ms
100ge1-1.core1.nyc4.he.net (2001:470:0:2cf::2)
3
131 ms
10ge10-3.core1.lax1.he.net (2001:470:0:10e::1)
4
136 ms
5
6
7
281 ms
273 ms
275 ms
8
287 ms
9
287 ms
10 286 ms
11 285 ms
lapeer-equinix.net.reach.com
(2001:504:0:3::4637:1)
2403:e800:ff00:110::f
2403:e800:100:1b::2
2001:8000:0:2030:101:401:0:1
bundle-ether5.cha-core4.brisbane.telstra.net
(2001:8000:0:2000:3001:6001:0:6)
tengigabitethernet7-1.cha30.brisbane.telstra.net
(2001:8000:0:6001::60:10b)
2001:8000:106::2
2001:dd8:8:701::244
23. How to connect - today
Scenario
From
To
How ?
Today
IPv4
IPv6
6to4 – public ipv4 address
Teredo – private ipv4 address
Today
IPv4
IPv6
Tunnel (HE/SixxS/Other)
Future
IPv6
IPv6
Native v6 from ISP
- Stop 6to4 or other tunnels
- upgrade os
- upgrade home router/access points
25. The omitted complexity....
New concepts in IPv6, not in IPv4:
•
•
•
•
•
•
•
•
RA
RS
Rogue RA
Neighbour Discovery
Protocol
Neighbour Advertisement
Neighbour Solicitation
DAD
DHCPv6
•
•
•
•
•
•
•
•
•
Big In IPv4, not in IPv6:
•
•
ARP
Broadcast
6to4
6rd
Teredo
AAAA
/64, /48, /56, /128
Link Local
Unique Local
Unique Global
OSPF v3
•
•
•
•
•
•
•
•
•
•
CGN
NAT64
DNS64
6PE
6VPE
SLAAC
AFTR
Dual Stack
DS-Lite
DHCPv6-PD
And many other considerations:
•
•
•
Old OS/App works fine on v4. Switch on v6 it may break.
Upgrade to fix a v6 issue, and you may find a new v4
bug you didnt have before
Parallel running two stacks uses more resources
25