BGP Flow-Spec Extended Community for Traffic Redirect to IP Next Hop
draft-simpson-idr-flowspec-redirect-02

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2013-05-30 (latest revision 2012-11-26)
Replaced by draft-ietf-idr-flowspec-redirect-ip
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-idr-flowspec-redirect-ip
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-simpson-idr-flowspec-redirect-02.txt

Abstract

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.

Authors

Jim Uttaro (ju1738@att.com)
Matthieu Texier (mtexier@arbor.net)
David Smith (djsmith@cisco.com)
Pradosh Mohapatra (pmohapat@cisco.com)
Wim Henderickx (wim.henderickx@alcatel-lucent.be)
Adam Simpson (adam.simpson@alcatel-lucent.com)

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