[Idr] I-D Action: draft-hr-idr-rfc5575bis-03.txt

internet-drafts@ietf.org Tue, 14 February 2017 18:10 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 CA1DA12949F; Tue, 14 Feb 2017 10:10:28 -0800 (PST)
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.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148709582882.9946.11698348034112788191.idtracker@ietfa.amsl.com>
Date: Tue, 14 Feb 2017 10:10:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mxZiXDtur0rlfeLhn5qibIgIphM>
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-hr-idr-rfc5575bis-03.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: Tue, 14 Feb 2017 18:10:29 -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           : Dissemination of Flow Specification Rules
        Authors         : Susan Hares
                          Robert Raszuk
                          Danny McPherson
                          Christoph Loibl
                          Martin Bacher
	Filename        : draft-hr-idr-rfc5575bis-03.txt
	Pages           : 30
	Date            : 2017-02-14

   This document updates RFC5575 which defines a Border Gateway Protocol
   Network Layer Reachability Information (BGP NLRI) encoding format
   that can be used to distribute traffic flow specifications.  This
   allows the routing system to propagate information regarding more
   specific components of the traffic aggregate defined by an IP
   destination prefix.  This draft specifies IPv4 traffic flow
   specifications via a BGP NLRI which carries traffic flow
   specification filter, and an Extended community value which encodes
   actions a routing system can take if the packet matches the traffic
   flow filters.  The flow filters and the actions are processed in a
   fixed order.  Other drafts specify IPv6, MPLS addresses, L2VPN
   addresses, and NV03 encapsulation of IP addresses.

   This document updates RFC5575 to correct unclear specifications in
   the flow filters and to provide rules for actions which interfere
   (e.g. redirection of traffic and flow filtering).

   Applications which use the bgp flow specification are: 1) application
   which automate of inter-domain coordination of traffic filtering,
   such as what is required in order to mitigate (distributed) denial-
   of-service attacks; 2) application which control traffic filtering in
   the context of a BGP/MPLS VPN service, and 3) applications with
   centralized control of traffic in a SDN or NFV context.  Some of
   deployments of these three applications can be handled by the strict
   ordering of the BGP NLRI traffic flow filters, and the strict actions
   encoded in the Extended Community Flow Specification actions.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

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: