<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-flowspec-path-redirect" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-flowspec-path-redirect-12">
   <front>
      <title>Flowspec Indirection-id Redirect</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>
      <date month="November" day="24" year="2022" />
      <abstract>
	 <t>   This document defines a new extended community known as &quot;FlowSpec
   Redirect to indirection-id Extended Community&quot;.  This extended
   community triggers advanced redirection capabilities to flowspec
   clients.  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-ietf-idr-flowspec-path-redirect-12" />
   
</reference>
