<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.liu-bess-srv6-l3vpn-fast-reoute" target="https://datatracker.ietf.org/doc/html/draft-liu-bess-srv6-l3vpn-fast-reoute-01">
   <front>
      <title>SRv6 L3VPN Fast Reroute</title>
      <author initials="Y." surname="Liu" fullname="Yisong Liu">
         <organization>China Mobile</organization>
      </author>
      <author initials="C." surname="Lin" fullname="Changwang Lin">
         <organization>New H3C Technologies</organization>
      </author>
      <author initials="Y." surname="Liu" fullname="Yao Liu">
         <organization>ZTE</organization>
      </author>
      <date month="January" day="24" year="2026" />
      <abstract>
	 <t>   In some multihoming SRv6 L3VPN scenarios, once fast reroute has
   taken place, a second fast reroute is undesirable and may cause
   looping. This document proposes a mechanism to prevent further fast
   reroutes by advertising No-Further-FRR behaviors for L3 SRv6 Service
   SIDs in BGP messages.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-liu-bess-srv6-l3vpn-fast-reoute-01" />
   
</reference>
