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

internet-drafts@ietf.org Mon, 12 April 2021 23:11 UTC

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
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <161826909901.17780.11455822325038429084@ietfa.amsl.com>
Date: Mon, 12 Apr 2021 16:11:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/55Mziqa5dXxdDtnajxVO3K9ebIU>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-flowspec-oid-13.txt

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-13.txt
	Pages           : 12
	Date            : 2021-04-12

Abstract:
   This document describes a modification to the validation procedure
   defined for the dissemination of BGP Flow Specifications.  The
   dissemination of BGP Flow Specifications 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.  For an iBGP received route, the originator is
   typically a border router within the same autonomous system.  The
   objective is to allow only BGP speakers within the data forwarding
   path to originate BGP Flow Specifications.  Sometimes it is desirable
   to originate the BGP Flow Specification any place within the
   autonomous system itself, for example, from a centralized BGP route
   controller.  However, the validation procedure will fail in this
   scenario.  The modification proposed herein relaxes the validation
   rule to enable Flow Specifications to be originated within the same
   autonomous system as the BGP speaker performing the validation.
   Additionally, this document revises AS_PATH validation rules so Flow
   Specifications received from an eBGP peer can be validated when such
   peer is a BGP route server.

   This document updates the validation procedure in RFC8955.


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-13
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-flowspec-oid-13

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


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/

[Idr] I-D Action: draft-ietf-idr-bgp-flowspec-oid… internet-drafts