The Correspondence between Packets and SRv6 Tunnels

Introduction In SRv6 networks, the software-defined network (SDN) controller serves as a core component, responsible for the centralized management and dynamic configuration of network resources. It is crucial for achieving network flexibility and intelligence. Currently, the controller's perception of SRv6 message paths relies on theoretical derivation, with limitations in timeliness and accuracy. State update latency and acquisition malfunctions pose challenges for real-time scenarios. Using the configuration of multipath tunnels as an example, ideally, it should dynamically adjust traffic routing based on the master-standby relationships and priority levels of the three preconfigured tunnels. This adjustment is crucial for ensuring the high availability and operational efficiency of the network. In practical applications, controller state-sensing latency causes failure to react promptly to network linkage changes, leading to inaccurate path determinations and affecting traffic-related operations.. Moreover, In tunnel load-balancing scenarios with multiple parallel sub-paths, hashing/random-based traffic distribution strategies boost bandwidth efficiency but increase maintenance complexity as real-time packet route tracking is difficult. To address these issues, this paper defines a new SRH extension header called "SRv6 Policy Key," which is used to identify the tunnel.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

SRv6 Policy KEY We define a new SRH extension header called "SRv6 Policy Key," which is used to identify the tunnel. This identifier is conveyed through the message header and communicated to the controller by the network node. This process empowers the controller to discern the SR path, thereby enhancing its state-aware capabilities within the Segment Routing domain. As a result, the controller can apprehend the network's real-time status with greater speed and accuracy, significantly aiding in the facilitation of operational maintenance decision-making processes.

Format of an SRv6 Policy KEY

SRv6 Policy KEY TLV

Type: An 8-bit code point.
Length: The length of the variable-length data field in bytes 6.
Flags: 8bit, marks list.
Preference: 32bit, marks SRv6 Policy Candidate Path.
Policy Color: 32bit, a Color of SRv6 Policy.
Headend: 128bit, first node of SRv6 Policy.
Endpoint: 128bit, destination address of SRv6 Policy.

Functional Description

Function1: Path Consistency Verification The awareness of actual paths ensures the controller can accurately evaluate the congruence between the factual routes of data transmission and the pre-established ideal paths. This procedure encompasses a systematic comparison of network packets'forwarding trajectories against the planned routes, aiming to detect and rectify potential deviations in path. Consequently, this boosts the network's reliability and operational efficiency.

Function2: Service flow analysis function A network node can document the traversal of SRv6 Policies, Candidate Paths, and Lists, and accumulate statistics in accordance with the service logic at these three hierarchical levels. In instances of node upgrade or relocation, the impacted services can thus be identified. Network nodes are capable of gathering traffic statistics based on the SRv6 Policies, Candidate Paths, and Lists that traverse the node, correlating these statistics with the service logic at the three tiers.

Function3: Controller path visualization The controller gathers the header information from packets processed at each network node and conducts statistical analyses, thereby enriching the visibility and manageability of network path data. -------------- | controller |---------------<-------------| | +-+-+-+-+-+-+-+-+-+-+-+ | | | | | | | |Telementry |Telementry |Telementry | | | | | | | | | | | | | SRv6 Policy +-+-+-+-+-+-+-+-+-+-+-+ SRv6 Policy | |------------->-------------- | P1 |--------------->-------------| | +-+-+-+-+-+-+-+-+-+-+-+ | | | | +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ | CE1 |----------------- | PE1 |----------------- | P2 |----------------- | PE2 |----------------- | CE2 | +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+ | | | | +-+-+-+-+-+-+-+-+-+-+-+ | |-----------------------------| P3 |------------------------------ +-+-+-+-+-+-+-+-+-+-+-| ]]> Enable SRv6 Policy Path Identifier Function. Enable this function at the head node (PE1) of the SRv6 Policy either through the controller or the device command-line interface. When a packet enters the head node of the SRv6 tunnel, the head node adds the SRv6 Policy Key to the packet. Packet Identification and Path Awareness.

Enable the detection function at the intermediate nodes (P1,P2,P3) or the destination node (PE2) either through the controller or the device command-line interface.
Nodes will parse all SRv6 Policy packets passing through themselves and extract service information and the SRv6 Policy Key from these packets. Within a specific time period, statistics on the service information associated with each SRv6 Policy Key are collected and the statistical results are reported to the controller. The controller uses the SRv6 Policy Key to query the candidate path list under the corresponding SRv6 policy, so as to obtain the service details of each path passing through this node, thereby perceiving the real path of the packet.

Use Case

Case 1: Enhancing Real-Time Path Recognition The controller can't sense packet paths in real-time. The SRv6 Policy Key provides unique path identifiers, enhancing real-time path-identification ability. Latency in path-information sensing hampers the accuracy of deducing real paths. Link-state update delays and revalidation needs pose challenges. The SRv6 Policy Key strengthens the controller's instant path-recognition capacity, addressing network device configuration update delays. By embedding unique path identifiers, the SRv6 Policy Key eases path-decision-making based on immediate info, ensuring network control accuracy and efficiency. This is evident in two scenarios: - In the architectural design featuring triple-redundant tunnels, achieving a seamless switch-over between the primary and backup tunnels necessitates precise awareness of the state of each path to uphold uninterrupted service delivery. - Under the single-tunnel multipath policy, traffic is dynamically distributed according to link conditions and priority levels, needing accurate path awareness for efficient handling and network performance optimization.

Case 2: Improving Path Visibility The controller cannot sense the actual paths in real-time. In intricate network load-balancing scenarios, a single path is bifurcated into three concurrent sub-paths to collaboratively bear the traffic load, with allocation executed randomly by devices following designated hash rules. Through the SRv6 Policy Key, the controller can attain real-time visibility of paths, thereby overcoming the uncertainty and unpredictability of paths engendered by the original random allocation mechanism.

Security Considerations TBD.

IANA Considerations TBD.