<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.vandevelde-idr-flowspec-path-redirect" target="https://datatracker.ietf.org/doc/html/draft-vandevelde-idr-flowspec-path-redirect-03">
   <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="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Nokia</organization>
      </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Sreekantiah" fullname="Arjun Sreekantiah">
         <organization>Cisco Systems</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="N." surname="Wu" fullname="Nan Wu">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="July" day="8" year="2016" />
      <abstract>
	 <t>   Flowspec is an extension to BGP that allows for the dissemination of
   traffic flow specification rules.  This has many possible
   applications but the primary one for many network operators is the
   distribution of traffic filtering actions for DDoS mitigation.  The
   flow-spec standard RFC5575 [2] defines a redirect-to-VRF action for
   policy-based forwarding but this mechanism is not always sufficient,
   particularly if the redirected traffic needs to be steered into an
   engineered path or into a service plane.

   This document defines a new extended community known as redirect-to-
   indirection-id (32-bit) flowspec action to provide advanced
   redirection capabilities on flowspec clients.  When activated, the
   flowspec extended community is used by a flowspec client to find the
   correct next-hop entry within a localised indirection-id mapping
   table.

   The functionality present in this draft allows a network controller
   to decouple flowspec functionality from the creation and maintainance
   of the network&#x27;s service plane itself including the setup of tunnels
   and other service constructs that could be managed by other network
   devices.


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