datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

Revised Validation Procedure for BGP Flow Specifications
draft-ietf-idr-bgp-flowspec-oid-02

Document type: Expired Internet-Draft (idr WG)
Document stream: IETF
Last updated: 2014-07-21 (latest revision 2014-01-17)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-ietf-idr-bgp-flowspec-oid-02.txt

Abstract

This document describes a modification to the validation procedure defined in RFC 5575 for the dissemination of BGP flow specifications. RFC 5575 requires that the originator of the flow specification matches the originator of the best-match unicast route for the destination prefix embedded in the flow specification. This allows only BGP speakers within the data forwarding path (such as autonomous system border routers) to originate BGP flow specifications. Though it is possible to disseminate such flow specifications directly from border routers, it may be operationally cumbersome in an autonomous system with a large number of border routers having complex BGP policies. The modification proposed herein enables flow specifications to be originated from a centralized BGP route controller.

Authors

Jim Uttaro <ju1738@att.com>
Clarence Filsfils <cf@cisco.com>
David Smith <djsmith@cisco.com>
Juan Alcaide <jalcaide@cisco.com>
Pradosh Mohapatra <mpradosh@yahoo.com>

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