Dataplane-Signaled IPv6 Packet Capture via OAM Extension Header
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IPv6 networks, capturing packets for analysis, troubleshooting, and security purposes is challenging due to the lack of scalable solutions that provide full visibility across multiple points without deploying multiple packet sniffers and complex filters, especially with high-speed links like 100G and 400G.
Innovation Solution
The method involves dataplane signaling using an OAM extension header within the IPv6 packet to indicate capture instructions, allowing network nodes to selectively capture and inspect packets based on predefined policies, eliminating the need for synchronized packet sniffers and filters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If multiple packet sniffers and complex filters are deployed to capture packets across multiple points, then full visibility across the network is achieved, but infrastructure complexity and deployment cost increase significantly
Solution Approach 1:
The patent introduces an OAM extension header as an intermediary mechanism embedded within the packet itself to carry capture signaling information. This header acts as a mediator between the data plane and control plane, enabling capture requests to be propagated through the network without requiring external packet sniffers at each node. The header includes capture request flags and node identifiers that automatically route the packet to appropriate capture points.
Solution Approach 2:
The packet itself carries the information needed to identify itself for capture through the OAM extension header. Each packet is self-marked with capture signaling information, allowing network nodes to autonomously determine whether to capture the packet based on the embedded header information, eliminating the need for external control plane instructions or complex filter configurations at each node.
2Loss of information
If packet capture is implemented on high-speed links (100G, 400G), then complete traffic analysis is possible, but the scale and resource requirements become unmanageable
Solution Approach 1:
The patent extracts only the essential capture signaling information into a compact OAM extension header within the packet, separating the capture control function from the data plane traffic. This extraction allows high-speed packets to carry minimal overhead metadata that enables capture decisions without requiring full packet inspection or complex filtering at line rate, making high-speed link capture scalable.
Solution Approach 2:
The patent changes the parameter of capture signaling from external control plane instructions to embedded in-band OAM headers within the packets themselves. This parameter change enables capture decisions to be made based on packet content rather than external configuration, allowing automated capture routing and reducing the manual configuration burden on high-speed networks.
3Loss of information
If synchronized packet sniffers are deployed at multiple network points, then comprehensive packet capture is achieved, but operational complexity and synchronization requirements increase
Solution Approach 1:
The OAM extension header provides feedback mechanisms through capture request flags and node identifier fields that automatically inform network nodes whether to capture packets. This embedded feedback system replaces complex external synchronization protocols, allowing nodes to autonomously make capture decisions based on the header information carried within each packet, significantly reducing operational complexity.
Data Source
AI summary
Presented herein are methods and systems that facilitate data plane signaling of a packet as a candidate for capture at various network nodes within an IPv6 network. The signaling occurs in-band, via the data plane—that is, a capture or interrogation signal is embedded within the respective packet (e.g., in the packet header) that carries a user traffic. The signaling is inserted, preferably when the packet is classified, e.g., at the ingress node of the network, to which subsequent network nodes with the IPv6 network are signaled to capture or further inspect the packet for capture.