Network Working Group James Uttaro
Internet Draft AT&T
Updates: 5575 Clarence Filsfils
Intended Status: Proposed Standard Pradosh Mohapatra
Expiration Date: July 2013 David Smith
Cisco
January 22, 2013
Revised Validation Procedure for BGP Flow Specifications
draft-ietf-idr-bgp-flowspec-oid-01
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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
Uttaro, et al. [Page 1]
Internet Draft Revised Flowspec Validation Procedure June 2012
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 1, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1 Specification of Requirements ...................... 2
2 Motivation ......................................... 3
3 Introduction ....................................... 5
4 Revised Validation Procedure ....................... 6
5 Security Considerations ............................ 7
6 IANA Considerations ................................ 7
7 Normative References ............................... 7
8 Acknowledgements ................................... 8
9 Authors' Addresses ................................. 8
1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Uttaro, et al. [Page 2]
Internet Draft Revised Flowspec Validation Procedure June 2013
2. Motivation
Step (a) of the validation procedure in [RFC5575], section 6 is
defined with the underlying assumption that the flow specification
NLRI traverses the same path, in the inter-domain and intra-domain
route distribution graph, as that of the longest-match unicast route
for the destination prefix embedded in the flow specification.
datatracker.ietf.org