Overview
IPv6 Transition Fundamentals
As IPv4 address exhaustion intensifies, migration to IPv6 becomes critical. However, IPv4 networks will persist due to operational continuity requirements. Transition technologies enable coexistence during this evolution phase.
IPv6 over IPv4 Tunneling
Encapsulates IPv6 packets within IPv4 headers to traverse IPv4 networks. Edge routers implement dual-stack and tunnnel configurations:
- Source router encapsulates IPv6 packets with IPv4 headers
- Intermediate IPv4 nodes forward encapsulated packets
- Destination router decapsulates and forwards native IPv6 packets
Manual Tunnels: Require static configuration of destination IPv4 addresses
Automatic Tunnels: Derive destination IPv4 from embedded IPv6 addresses
6PE Technology
MPLS-Based IPv6 Connectivity
Leverages existing IPv4/MPLS infrastructure to connect IPv6 networks. Provider Edge (PE) routers:
- Use MP-BGP to distribute IPv6 routes with MPLS labels
- Establish LSP tunnels across IPv4 backbone
- Employ dual-stack for IPv6 customer edge connectivity
Label Optimization
Explicit Null Label (value 2) enables route-label sharing, reducing label consumption by eliminating per-route label allocation.
6VPE Implementation
IPv6 VPN Architecture
Extends MPLS VPNs to IPv6, providing logical isolation between VPNs. Key characteristics:
- MP-BGP exchanges VPNv6 routes over IPv4 sessions
- Uses LSP/TE tunnels for data transport
- PE-CE routing follows IPv6 protocols
Configuration Example
// Configure VPN instance
[Router] vpn-instance NET_A
[Router-vpn-instance] ipv6-family
[Router-vpn-instance-ipv6] route-distinguisher 65000:1
[Router-vpn-instance-ipv6] vpn-target 64512:1
// Bind interface to VPN
[Router-GigabitEthernet0/0/0] vpn-binding NET_A
[Router-GigabitEthernet0/0/0] ipv6 address 2001:db8:1::1/64
// Establish MP-BGP peering
[Router] bgp 65000
[Router-bgp] neighbor 192.0.2.1 remote-as 65000
[Router-bgp] address-family vpnv6
[Router-bgp-vpnv6] neighbor 192.0.2.1 activate
IPv4 over IPv6 Tunneling
Encapsulates IPv4 packets in IPv6 headers for traversal across IPv6 networks. Dual-stack border routers:
- Statically configure tunnel endpoints
- Process encapsulation/decapsulation
- Maintani IPv4 and IPv6 routing domains
NAT64 Translation
Address Conversion Mechanism
Enables communication between IPv6 and IPv4 networks through prefix-based translation:
- Well-known prefix: 64:FF9B::/96
- Custom prefixes (32-96 bit lengths)
Dynamic Mapping
Creates on-demand translations using address pools:
// Configure NAT pool
[Firewall] nat-pool DYNAMIC_POOL
[Firewall-nat-pool] pat-mode
[Firewall-nat-pool] range 203.0.113.10 203.0.113.20
// Apply NAT policy
[Firewall] policy-nat
[Firewall-policy] rule NAT64_DYN
[Firewall-policy-rule] nat64 dynamic DYNAMIC_POOL
Static Mapping
Defines fixed IPv4-IPv6 addresss bindings:
// Create static entry
[Firewall] nat64 static 2001:db8:a::1 192.0.2.100
IVI Translation
Stateless address mapping technique using reserved IPv4 blocks mapped to dedicated IPv6 prefixes, enabling bidirectional IPv4/IPv6 communication through gateway translation.