%% You should probably cite draft-ali-spring-bfd-sr-policy-10 instead of this revision. @techreport{ali-spring-bfd-sr-policy-01, number = {draft-ali-spring-bfd-sr-policy-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ali-spring-bfd-sr-policy/01/}, author = {Zafar Ali and Ketan Talaulikar and Clarence Filsfils}, title = {{Bidirectional Forwarding Detection (BFD) for Segment Routing Policies for Traffic Engineering}}, pagetotal = 8, year = 2018, month = oct, day = 9, abstract = {Segment Routing (SR) allows a headend node to steer a packet flow along any path using a segment list which is referred to as a SR Policy. Intermediate per-flow states are eliminated thanks to source routing. The header of a packet steered in an SR Policy is augmented with the ordered list of segments associated with that SR Policy. Bidirectional Forwarding Detection (BFD) is used to monitor different kinds of paths between node. BFD mechanisms can be also used to monitor the availability of the path indicated by a SR Policy and to detect any failures. Seamless BFD (SBFD) extensions provide a simplified mechanism which is suitable for monitoring of paths that are setup dynamically and on a large scale. This document describes the use of Seamless BFD (SBFD) mechanism to monitor the SR Policies that are used for Traffic Engineering (TE) in SR deployments.}, }