BGP Flow-Spec Redirect to IP Action
draft-ietf-idr-flowspec-redirect-ip-02
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jim Uttaro , Jeffrey Haas , Matthieu Texier , akarch@cisco.com , Saikat Ray , Adam Simpson , Wim Henderickx | ||
| Last updated | 2015-08-09 (Latest revision 2015-02-05) | ||
| Replaces | draft-simpson-idr-flowspec-redirect | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 VPN infrastructure. This draft defines a new redirect-to-IP flow-spec action that provides a simpler method of policy-based forwarding. The details of the action, including the IPv4 or IPv6 target address, are encoded in newly defined BGP extended communities.
Authors
Jim Uttaro
Jeffrey Haas
Matthieu Texier
akarch@cisco.com
Saikat Ray
Adam Simpson
Wim Henderickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)