1. IPv6 Deployment in Enterprise Networks
Ivan Pepelnjak
Chief Technology Advisor, NIL Data Communications

2. ©2009 NIL 2
Scenario
• Do I care about IPv6?
• Where shall I focus my efforts?
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

3. ©2009 NIL 3
Facts of Life
• IPv6 is here, get used to it.
• You’ll get stuck on migration details.
• Start small, but start now.

4. ©2009 NIL 4
Facts of Life (NAT)
• Everyone uses 4-to-4 NAT. It’s bad.
• Slow migration to IPv6 requires more NAT.
• 6-to-4 NAT stinks.
• 4-to-6 NAT is horrendous.

5. ©2009 NIL 5
Deployment Phase 1: Dual-stack
• Some public servers are reachable over IPv6
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

6. ©2009 NIL 6
Deployment Phase 2: IPv6 Clients
• Some clients are using only IPv6: 6-to-4 NAT
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

7. ©2009 NIL 7
Deployment Phase 3: IPv6 Servers
• Some servers are reachable only over IPv6:
4-to-6 NAT
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

8. ©2009 NIL 8
Timeline Guestimate
Time [years]
IPv6
adoption
[%]
Dual-stack: now IPv6-only clients
2-3 years
IPv6-only servers
10(?) years
Knowledge
opportunity
loss
Business
opportunity
loss Nightmare

9. ©2009 NIL 9
Phase 1 Actions
Ignore IPv6 or …
• Deploy IPv6 in your DMZ infrastructure
• Dual-stack on non-critical servers
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

10. ©2009 NIL 10
Phase 2 Actions
• You are IPv6 ready in your DMZ (are you?)
• Design, test and deploy dual stack in your network
Private network
using RFC 1918 IPv4
DMZ using
public IPv4
Public Internet

11. ©2009 NIL 11
Phase 3 Actions
 Relax and enjoy
 Frantic catch-up efforts
 Suffer the consequences of 4-to-6 NAT
RFC 1918 IPv4
Public IPv6
DMZ using
public IPv4
Public Internet

12. ©2009 NIL 12
Summary
• IPv6 is here
• There’s no rush (yet)
• Use your time wisely