IPv6 Routing via Prefix Reduction Option Header
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet Protocol routing tables, particularly IPv4 and IPv6, are excessively large, leading to memory limitations and latency issues due to the need to store and look up extensive address information across different autonomous systems.
Innovation Solution
Implementing a Prefix Reduction Option (PRO) within the IPv6 Destination Option header to store IPv6 addresses of source and destination endpoints and gateways, allowing intermediate routers to route packets without advertising endpoint addresses publicly, thereby reducing the size of routing tables and lookup latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IPv6 address information for source and destination endpoints is stored in routing tables, then packet routing between autonomous systems can be achieved, but routing table size increases significantly causing memory limitations and latency issues
Solution Approach 1:
The patent extracts endpoint address information from the public routing table and places it into the IPv6 Destination Option header. This allows intermediate routers to route packets using only gateway addresses in their routing tables, while endpoint addresses are carried privately in the packet header, thereby reducing routing table size while maintaining routing capability.
Solution Approach 2:
The patent introduces gateway addresses as intermediaries between source/destination endpoints. Routers use gateway addresses (which are publicly advertised and stored in routing tables) to forward packets, rather than storing endpoint addresses directly. The endpoint addresses are transported through the packet's Destination Option header, serving as intermediary carriers.
2Loss of information
If IPv6 address information is stored in routing tables, then complete routing information is available, but lookup time increases causing latency issues
Solution Approach 1:
The patent extracts endpoint address information from the routing table lookup process and places it in the packet header's Destination Option. This allows routers to perform lookups only on gateway addresses (reducing lookup time) while still having access to complete endpoint information through the packet header, thus resolving the trade-off between information completeness and lookup speed.
3Loss of information
If endpoint addresses are publicly advertised, then routing information is complete, but routing table memory requirements increase
Solution Approach 1:
The patent extracts endpoint address information from public advertising and routing tables, and instead transports it privately within the IPv6 packet's Destination Option header. This allows complete routing information to be preserved in the packet while routing tables contain only essential gateway addresses, significantly reducing memory requirements for stationary routing data.
Solution Approach 2:
The patent moves endpoint address information from the traditional routing table dimension (stored in router memory) to the packet dimension (transported in the Destination Option header). This dimensional shift allows routing information to be complete in the packet while routing tables remain compact, effectively resolving the memory constraint.
Data Source
AI summary
Systems, methods, architectures, mechanisms or apparatus for routing packets between source and destination endpoints associated with different autonomous systems without requiring public advertising of the addresses of the source and destination endpoints to other autonomous systems (ASN).