<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf0-idr-srv6-flowspec-path-redirect" target="https://datatracker.ietf.org/doc/html/draft-ietf0-idr-srv6-flowspec-path-redirect-15">
   <front>
      <title>Flowspec Indirection-id Redirect for SRv6</title>
      <author initials="G." surname="Van de Velde" fullname="Gunter Van de Velde">
         <organization>Nokia</organization>
      </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Arrcus</organization>
      </author>
      <author initials="Z." surname="Li" fullname="Zhenbin Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="S." surname="Zhuang" fullname="Shunwan Zhuang">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="H." surname="Chen" fullname="Huaimo Chen">
         <organization>Futurewei</organization>
      </author>
      <date month="March" day="19" year="2026" />
      <abstract>
	 <t>   This document defines extensions to &quot;FlowSpec Redirect to
   indirection-id Extended Community&quot; for SRv6.  This extended community
   can trigger advanced redirection capabilities to flowspec clients for
   SRv6.  When activated, this flowspec extended community is used by a
   flowspec client to retrieve the corresponding next-hop and encoding
   information within a localised indirection-id mapping table.

   The functionality detailed in this document allows a network
   controller to decouple the BGP flowspec redirection instruction from
   the operation of the available paths.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf0-idr-srv6-flowspec-path-redirect-15" />
   
</reference>
