BGP Flow-Spec Extended Community for Traffic Redirect to IP Next Hop

Document Type Replaced Internet-Draft (individual)
Authors Jim Uttaro  , Matthieu Texier  , David Smith  , Prodosh Mohapatra  , Wim Henderickx  , Adam Simpson 
Last updated 2013-05-30 (latest revision 2012-11-26)
Replaced by draft-ietf-idr-flowspec-redirect-ip
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-idr-flowspec-redirect-ip
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Flow-spec 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 [RFC 5575] defines a redirect-to-VRF action for policy-based forwarding but this mechanism can be difficult to use, particularly in networks without L3 VPNs. This draft proposes a new redirect-to-IP flow-spec action that provides a simpler method of policy-based forwarding. This action is indicated by the presence of a new BGP extended community in the flow-spec route. Many routers already support a redirect-to-IP filter action and, in this case, the only new functionality implied by this draft is the ability to signal the action using flow-spec.


Jim Uttaro (
Matthieu Texier (
David Smith (
Prodosh Mohapatra (
Wim Henderickx (
Adam Simpson (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)