[Idr] I-D Action: draft-ietf-idr-bgp-flowspec-oid-09.txt

internet-drafts@ietf.org Mon, 08 July 2019 23:50 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8A11203B2; Mon, 8 Jul 2019 16:50:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: idr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.3
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <156262980675.865.14835007046260285344@ietfa.amsl.com>
Date: Mon, 08 Jul 2019 16:50:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9nI2cIXePVn1jOUV0UzA2Ku6L60>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-flowspec-oid-09.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2019 23:50:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : Revised Validation Procedure for BGP Flow Specifications
        Authors         : James Uttaro
                          Juan Alcaide
                          Clarence Filsfils
                          David Smith
                          Pradosh Mohapatra
	Filename        : draft-ietf-idr-bgp-flowspec-oid-09.txt
	Pages           : 11
	Date            : 2019-07-08

Abstract:
   This document describes a modification to the validation procedure
   defined in RFC 5575bis for the dissemination of BGP Flow
   Specifications.  RFC 5575bis 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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-flowspec-oid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-bgp-flowspec-oid-09
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-flowspec-oid-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-flowspec-oid-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/