SRV6OPS Y. Liu Internet-Draft W. Cheng Intended status: Informational China Mobile Expires: 19 May 2027 C. Lin New H3C Technologies X. Min ZTE Corp. 15 November 2026 Operational Guidelines for BFD Monitoring in SRv6 Policies draft-liu-srv6ops-bfd-srv6-policy-encap-02 Abstract This document provides operational guidelines for Bidirectional Forwarding Detection (BFD) when applied to Segment Routing over IPv6 (SRv6) Policies. While the packet encapsulation mechanisms are standardized, this document focuses on the decisions network operators must make regarding mode selection, address management, traffic engineering integration, and troubleshooting strategies to ensure reliable service protection and efficient resource utilization. It addresses practical challenges such as handling diverse tail-end node capabilities (IPv4/IPv6), managing BFD session overhead in large-scale segment lists, and diagnosing failure detection anomalies in source-routed paths. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 19 May 2027. Liu, et al. Expires 19 May 2027 [Page 1] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Motivation for Operational Guidelines . . . . . . . . . . 2 2. Operational Considerations for Mode Selection . . . . . . . . 3 2.1. Insert-Mode vs. Encaps-Mode Decision Criteria . . . . . . 3 2.2. Impact on Tail-End Nodes and Interoperability . . . . . . 4 3. Address Management and Policy Configuration . . . . . . . . . 4 3.1. Headend Source Address Selection . . . . . . . . . . . . 4 3.2. Tail-End Destination Address Resolution . . . . . . . . . 5 4. Resource Management and Scalability . . . . . . . . . . . . . 5 4.1. BFD Session Overhead . . . . . . . . . . . . . . . . . . 6 4.2. Mitigating State Explosion in Large Segment Lists . . . . 6 5. Troubleshooting and Diagnostics . . . . . . . . . . . . . . . 6 5.1. Verifying Path Correctness . . . . . . . . . . . . . . . 6 5.2. Diagnosing False Failures and Timeout Issues . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. Normative References . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction 1.1. Motivation for Operational Guidelines Segment Routing over IPv6 (SRv6) allows network operators to steer traffic along explicit paths defined by Segment Routing Policies (SR Policies). To meet carrier-grade availability requirements, fast failure detection is critical. Bidirectional Forwarding Detection (BFD) [RFC5880] is commonly used to monitor the continuity of these policies. Liu, et al. Expires 19 May 2027 [Page 2] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 However, simply implementing BFD for SRv6 presents operational complexities. Unlike traditional IP forwarding where the path is dynamic and determined by the routing protocol, SRv6 paths are explicitly coded into the packet header. This introduces unique challenges for operators: Encapsulation Choice: Operators must decide between Insert-Mode and Encaps-Mode, which have different implications for tail-end compatibility and bandwidth overhead. Address Complexity: The source and destination addresses of the BFD packets vary depending on the encapsulation mode and the state of the packet along the path (e.g., SRH popping). Troubleshooting Difficulty: Standard BFD debugging tools may misinterpret the changing headers (such as the shifting Destination Address due to SRH segment popping) as packet anomalies or forwarding loops. This document does not define new encapsulation protocols but rather provides guidance on how to deploy, configure, and maintain BFD monitoring for SRv6 Policies in real-world networks. 2. Operational Considerations for Mode Selection There are two primary methods for encapsulating BFD packets for SRv6 Policies: Insert-Mode and Encaps-Mode. The choice between them is a key operational decision. 2.1. Insert-Mode vs. Encaps-Mode Decision Criteria Insert-Mode inserts the SRH directly into the original BFD packet. Encaps-Mode wraps the entire BFD packet (including its IP header) in an outer IPv6/SRH header. Network operators should consider the following factors when selecting the mode: Older Devices: If the tail-end node is an older device that does not support SRv6 decryption or termination of the specific SRH flavors used by the policy, Encaps-Mode is recommended. In Encaps-Mode, the outer headers are stripped by the penultimate hop (or specified endpoint), exposing the inner BFD packet (which typically uses standard BFD headers) to the final destination. Full SRv6 Support: If all nodes in the path support SRv6 and can process the SRH fully, Insert-Mode is preferred to reduce overhead. Liu, et al. Expires 19 May 2027 [Page 3] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 Bandwidth Overhead: Insert-Mode: Has lower overhead because it reuses the existing IPv6 header of the BFD packet and only adds the SRH. Encaps-Mode: Adds a full additional IPv6 header, SRH, and potentially increases the packet size significantly, especially if the Segment List is long. This may be a concern for high-frequency BFD packets (e.g., 1ms intervals). Debugging Visibility: Encaps-Mode: The inner packet remains constant. Tools capturing packets at intermediate nodes can clearly see the inner BFD headers, making it easier to identify the intended source and destination IPs without parsing the entire SRH. Insert-Mode: The Destination Address changes at each hop as segments are popped. This can confuse simple packet captures unless they account for SRH semantics. 2.2. Impact on Tail-End Nodes and Interoperability Operators must verify the SRv6 Function of the last Segment in the Policy [RFC8986]. End.Adj / End.X SIDs: If the last segment is an adjacency SID, the node may not decapsulate the packet entirely. In Insert-Mode, the tail-end must understand how to extract the BFD payload after the SRH processing. In Encaps-Mode, the penultimate hop should perform Ultimate Segment Decapsulation (USD) to expose the inner packet to the actual tail-end endpoint. Binding SIDs (BSID): If the policy uses a BSID, the terminating node processes the BSID and may terminate the SRH. Operators must ensure that the BFD packet arriving at the local loopback or interface is parseable by the BFD agent. Encaps-Mode is generally safer here as it keeps the BFD packet self-contained. 3. Address Management and Policy Configuration Proper address configuration is critical for BFD session establishment and correct packet delivery. 3.1. Headend Source Address Selection The Source Address (SA) of the outer IPv6 header determines the return path for BFD Echo responses or potential ICMP errors. Liu, et al. Expires 19 May 2027 [Page 4] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 Recommendation: Use a stable, routable IPv6 address associated with the headend node's role in the SR Policy (e.g., a loopback address or a dedicated SVI interface). Avoid Link-Local Addresses: Do not use link-local addresses as the Source Address for the outer header unless the immediate next-hop is the only destination. SR Policies often traverse multiple hops; a globally unique or domain-routable SA ensures that return traffic (if any) is handled correctly. Multi-Homed Headends: If the headend has multiple egress interfaces for the same SR Policy, consistent SA selection helps in maintaining session state clarity during failures. 3.2. Tail-End Destination Address Resolution The Destination Address (DA) behavior depends on the encapsulation mode. For Insert-Mode: The initial DA in the IPv6 header matches the first segment in the SRH. However, as the packet traverses the path, the SRH pointer advances, and the DA changes to the next segment. Operational Implication: When troubleshooting, do not assume the initial DA is the final destination. The BFD process must track the active Segment List. For Encaps-Mode: The inner IPv6 header's DA is fixed to the tail-end node's address (e.g., its Loopback0 or an interface IP). Operational Implication: This provides a stable visibility into the true end-point of the BFD session. Operators can verify reachability to this specific DA using tools like ping or traceroute from intermediate nodes (if permitted) to debug path issues. Unspecified Address (::) Handling: If the SR Policy is defined with an unspecified endpoint (::), the operator MUST explicitly configure the tail-end IPv6 address in the BFD configuration. Failure to do so will result in BFD packet drops or undefined behavior. 4. Resource Management and Scalability SRv6 Policies can contain long Segment Lists. Monitoring every segment or the entire path via BFD has significant resource implications. Liu, et al. Expires 19 May 2027 [Page 5] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 4.1. BFD Session Overhead One-to-Many Mapping: A single SR Policy might consist of multiple Candidate Paths, each with multiple Segment Lists. If BFD is instantiated per Segment List, the number of BFD sessions can grow exponentially. Recommendation: Implement BFD at the Candidate Path level rather than the Segment List level, if possible. This reduces the number of sessions. If fine-grained monitoring (per Segment List) is required, ensure the controller/headend has sufficient CPU/Memory to handle the session state transitions. 4.2. Mitigating State Explosion in Large Segment Lists For policies with very long Segment Lists, generating BFD packets for every hop can be inefficient. S-BFD (Seamless BFD): Use S-BFD [RFC7880] where available. S-BFD removes the need for a bidirectional handshake per path segment, reducing CPU load on intermediate nodes and simplifying the state model. The reflexion point is configured statically or via controller push, avoiding session negotiation overhead. Sampling: For non-critical paths, consider increasing the BFD transmit interval or using lower sensitivity timers, accepting a slight increase in detection time in exchange for reduced control plane overhead. 5. Troubleshooting and Diagnostics Diagnosing BFD failures in SRv6 requires understanding the interaction between the control plane (BFD) and the data plane (SRH processing). 5.1. Verifying Path Correctness To confirm that BFD packets are following the intended SR Policy: Check SRH Structure: Verify that the SRH inserted/encapsulated at the headend contains the correct Segment List corresponding to the active BFD session. Verify Segment List[0]: Ensure that Segment List[0] in the SRH correctly points to the next-hop segment or tail-end, depending on the mode. A mismatch here causes packets to take a wrong path or get dropped. Liu, et al. Expires 19 May 2027 [Page 6] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 Packet Capture: In Encaps-Mode, look for the outer IPv6 header matching the SR Policy's start segment and the inner header matching the tail-end. In Insert-Mode, observe the change in IPv6 Destination Address across nodes. If the DA does not match the expected next segment, there is a misconfiguration in the Segment List or SRH processing. 5.2. Diagnosing False Failures and Timeout Issues Jitter and Loss: BFD timers are sensitive. If the SR Policy traverses congested links, BFD packets (which are small and frequent) might be dropped or delayed. Action: Ensure strict QoS priority for BFD packets. Even in SRv6, BFD packets are UDP/ICMP and may be subject to default queuing policies. Configure a dedicated Class of Service (CoS) for BFD traffic. Asymmetric Routes: In some SR implementations, the forward path (BFD packets) and the reflection path (Echo replies) might differ if not carefully configured. Ensure that the SR Policy for the return traffic (if any) or the default return path allows BFD Echo replies to reach the headend. Node Processing Delay: Intermediate nodes performing complex SRv6 functions (like End.MAC, End.DX2, etc.) may introduce latency. Adjust BFD transmit/receive multipliers accordingly. 6. Security Considerations BFD Authentication: As per [RFC5880], operators should enable MD5 or SHA-based authentication for BFD sessions to prevent spoofing. In SRv6 environments, ensuring that authenticated BFD packets are not dropped due to checksum verification issues is crucial. SRH Protection: While not part of BFD directly, operators should ensure that the SR Policy itself is protected against unauthorized manipulation to prevent traffic steering attacks. 7. IANA Considerations This document has no IANA actions. 8. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Liu, et al. Expires 19 May 2027 [Page 7] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, . [RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S. Pallagatti, "Seamless Bidirectional Forwarding Detection (S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016, . [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., Decraene, B., Litkowski, S., and R. Shakir, "Segment Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, July 2018, . [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, . [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 (SRv6) Network Programming", RFC 8986, DOI 10.17487/RFC8986, February 2021, . [RFC9256] Filsfils, C., Talaulikar, K., Ed., Voyer, D., Bogdanov, A., and P. Mattes, "Segment Routing Policy Architecture", RFC 9256, DOI 10.17487/RFC9256, July 2022, . Authors' Addresses Yisong Liu China Mobile 32 Xuanwumen West Street Beijing Xicheng District, 100053 China Email: liuyisong@chinamobile.com Weiqiang Cheng China Mobile 32 Xuanwumen West Street Beijing Xicheng District, 100053 China Email: chengweiqiang@chinamobile.com Liu, et al. Expires 19 May 2027 [Page 8] Internet-Draft Operational Guidelines for BFD in SRv6 November 2026 Changwang Lin New H3C Technologies 8 Yongjia North Road Beijing Haidian District, 100094 China Email: linchangwang.04414@h3c.com Xiao Min ZTE Corp. China Email: xiao.min2@zte.com.cn Liu, et al. Expires 19 May 2027 [Page 9]