[Idr] I-D Action: draft-ietf-idr-rfc5575bis-06.txt

internet-drafts@ietf.org Wed, 25 October 2017 10:07 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
Message-ID: <150892607370.4792.9365719407694033564@ietfa.amsl.com>
Date: Wed, 25 Oct 2017 03:07:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/t-QQ4Lmw-MJP28s8_aSulqM3vVE>
Subject: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-06.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           : Dissemination of Flow Specification Rules
        Authors         : Susan Hares
                          Christoph Loibl
                          Robert Raszuk
                          Danny McPherson
                          Martin Bacher
	Filename        : draft-ietf-idr-rfc5575bis-06.txt
	Pages           : 33
	Date            : 2017-10-25

Abstract:
   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.

   It 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 inter-domain coordination of traffic filtering, such
   as what is required in order to mitigate (distributed) denial-of-
   service attacks; 2) applications 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
   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:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc5575bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-06
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc5575bis-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rfc5575bis-06


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-rfc5575bis-06.txt internet-drafts