Host Node NAT64 Prefix Management for IPv6-IPv4 Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems using NAT64 and DNS64 nodes fail to maintain connectivity between IPv6 nodes and IPv4 nodes when a mobile or multi-homed node moves between networks, as each network uses distinct prefixes for virtual IPv6 addresses, leading to loss of connection if the prefix is unknown to other networks.
Innovation Solution
A host node with connections to multiple networks maintains connectivity by storing prefixes from DHCP or access routers in a translation binding table, looking up the appropriate prefix for the selected network, and replacing the generic prefix in virtual IPv6 addresses to ensure seamless communication with IPv4 nodes across different NAT64 nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each network uses distinct prefixes for virtual IPv6 addresses to enable local NAT64 translation, then IPv6 nodes can communicate with IPv4 nodes on that specific network, but connectivity is lost when the host node moves to a different network with an unknown prefix
Solution Approach 1:
The host node proactively discovers and stores NAT64 prefixes from multiple networks in advance by listening to DHCP or Router Advertisement messages. When moving between networks, the host already has prefix information available, eliminating connectivity interruptions and avoiding the need for reactive prefix discovery.
Solution Approach 2:
The host node acts as an intermediary that translates between generic virtual IPv6 addresses and network-specific virtual IPv6 addresses by substituting the appropriate prefix. This mediation enables seamless communication across networks with different NAT64 prefixes without requiring changes to the corresponding node or network infrastructure.
2Reliability
If the host node stores multiple NAT64 prefixes from different networks, then connectivity can be maintained when moving between networks, but the device complexity increases due to prefix management requirements
Solution Approach 1:
The host node automatically discovers NAT64 prefixes by listening to DHCP or Router Advertisement messages on each network interface without requiring manual configuration or external management. The system self-maintains the prefix information, reducing operational complexity despite storing multiple prefixes.
Solution Approach 2:
The host node dynamically changes the prefix parameter in virtual IPv6 addresses based on the current network context. By substituting the appropriate stored prefix into the generic virtual IPv6 address format, the host adapts to different networks efficiently without complex management overhead.
Data Source
AI summary
A method is implemented in a host node for communicating with a corresponding node. The host node has connections to a plurality of networks, where each of the plurality of networks includes a network address translation 64 (NAT64) node, each NAT64 node utilizes a distinct prefix to generate virtual Internet Protocol version 6 (IPv6) addresses, each of the plurality of networks is an IPv6 network, but the corresponding node is an Internet protocol version 4 (IPv4) node. The host node implementing this method is able to maintain connectivity with the corresponding node despite having connections to the plurality of networks that each have NAT64 nodes that utilize distinct prefixes for virtual IPv6 addresses.