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

internet-drafts@ietf.org Mon, 13 March 2017 21:26 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 8F733129406; Mon, 13 Mar 2017 14:26:27 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148944038756.20276.10433880975348907444@ietfa.amsl.com>
Date: Mon, 13 Mar 2017 14:26:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/p_gkzmEJn_EdX4wniT0O_dvgToI>
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-flowspec-oid-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Mar 2017 21:26:27 -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 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-04.txt
	Pages           : 9
	Date            : 2017-03-13

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.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-bgp-flowspec-oid-04

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


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/