Skip to main content

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

The information below is for an old version of the document.
Document Type Expired Internet-Draft (idr WG)
Authors Jim Uttaro , Juan Alcaide , Clarence Filsfils , David Smith , Prodosh Mohapatra
Last updated 2017-09-14 (Latest revision 2017-03-13)
Replaces draft-djsmith-bgp-flowspec-oid
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Reviews
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 can be found at:
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-flowspec-oid-04.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
Juan Alcaide
Clarence Filsfils
David Smith
Prodosh Mohapatra

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