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

Document Type Expired Internet-Draft (idr WG)
Last updated 2020-02-10 (latest revision 2019-08-09)
Replaces draft-djsmith-bgp-flowspec-oid
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Revised I-D Needed - Issue raised by WGLC
Document shepherd Susan Hares
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Susan Hares <shares@ndzh.com>

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-10.txt

Abstract

This document describes a modification to the validation procedure defined in [RFC5575bis] for the dissemination of BGP Flow Specifications. [RFC5575bis] 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)
Juan Alcaide (jalcaide@cisco.com)
Clarence Filsfils (cf@cisco.com)
David Smith (djsmith@cisco.com)
Prodosh Mohapatra (mpradosh@yahoo.com)

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