Network Device Adjacency Table Segmentation for IPv4 Packet Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network devices face inefficiencies in forwarding data packets due to the inability to support and apply different types of ACLs, particularly IPV6 egress ACLs, leading to unnecessary recirculation of IPV4 packets when IPV6 next hops are used for both IPV4 and IPV6 routes, which increases latency and resource usage.
Innovation Solution
The network device uses separate entries in the adjacency table for IPV4 and IPV6 packets that share the same IPV6 next hop, allowing it to avoid recirculating IPV4 packets when an IPV6 egress ACL is used, thereby improving forwarding efficiency and reducing computational resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the network device uses a single adjacency table entry for both IPV4 and IPV6 packets with the same next hop, then the device complexity is reduced, but unnecessary recirculation of IPV4 packets occurs when IPV6 egress ACLs are used, increasing latency and resource usage
Solution Approach 1:
The patent segments the adjacency table into separate entries for IPV4 and IPV6 packets, even when they share the same next hop. This segmentation allows the network device to distinguish between packet types and apply appropriate ACL processing, preventing unnecessary recirculation of IPV4 packets when IPV6 egress ACLs are used.
Solution Approach 2:
The patent applies local quality by associating different properties with IPV4 and IPV6 entries in the adjacency table. Each entry is tailored to its specific protocol requirements, allowing IPV6 entries to be marked for egress ACL processing while IPV4 entries are not, thereby optimizing processing behavior for each packet type locally.
2Reliability
If the network device recirculates IPV4 packets to apply IPV6 egress ACLs, then ACL security policies are maintained, but resource utilization increases due to unnecessary processing
Solution Approach 1:
The patent segments the ACL application logic by protocol type. IPV6 entries in the adjacency table are marked to trigger egress ACL processing, while IPV4 entries are explicitly excluded from this processing path. This segmentation ensures that ACL policies are enforced only when necessary, eliminating wasteful computational resource usage.
Solution Approach 2:
The patent changes the protocol version parameter in the adjacency table entries to control ACL processing behavior. By setting different protocol version indicators for IPV4 and IPV6 entries, the system dynamically adjusts whether egress ACLs are applied, ensuring security policies are maintained while avoiding unnecessary processing.
3Reliability
If the network device applies IPV6 egress ACLs to all packets using IPV6 next hops, then consistent security policy is achieved, but IPV4 packet forwarding efficiency decreases due to unnecessary processing
Solution Approach 1:
The patent applies local quality by making ACL processing behavior dependent on the specific packet protocol type. IPV6 packets trigger egress ACL processing as expected, while IPV4 packets are explicitly excluded from this processing. This localized approach maintains security policy consistency for IPV6 while preserving forwarding efficiency for IPV4.
Solution Approach 2:
The patent uses the protocol version parameter to control the application of egress ACLs. By checking the protocol version in the adjacency table entry, the system dynamically enables or disables ACL processing based on whether the packet is IPV4 or IPV6, thereby maintaining security consistency where needed while optimizing throughput where not needed.
Data Source
AI summary
In one embodiment, a method is provided. The method includes receiving a data packet via an ingress interface of the network device. The method also includes determining whether the data packet comprises an Internet Protocol version 4 (IPV4) or an Internet Protocol version 6 (IPV6) packet. The method further includes in response to determining that the packet comprises an IPV4 packet, identifying a first entry in an adjacency table. The first entry is associated with an address prefix. The address prefix is associated with first Internet Protocol (IP) address of the data packet. The first entry indicates a next hop for the data packet. The adjacency table comprises a second entry associated with the address prefix. The method further includes forwarding the packet to the next hop indicated by the first entry in the adjacency table, via an egress interface of the network device.