Dissemination of Flow Specification Rules
draft-ietf-idr-rfc5575bis-06

Document Type Active Internet-Draft (idr WG)
Last updated 2017-11-11 (latest revision 2017-10-25)
Replaces draft-hr-idr-rfc5575bis
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                               S. Hares
Internet-Draft                                                    Huawei
Obsoletes: 5575,7674 (if approved)                              C. Loibl
Intended status: Standards Track               Next Layer Communications
Expires: April 27, 2018                                        R. Raszuk
                                                            Bloomberg LP
                                                            D. McPherson
                                                                Verisign
                                                               M. Bacher
                                                        T-Mobile Austria
                                                        October 24, 2017

               Dissemination of Flow Specification Rules
                      draft-ietf-idr-rfc5575bis-06

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.

Hares, et al.            Expires April 27, 2018                 [Page 1]
Internet-Draft                 RFC5575bis                   October 2017

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 27, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions of Terms Used in This Memo  . . . . . . . . . . .   5
   3.  Flow Specifications . . . . . . . . . . . . . . . . . . . . .   6
   4.  Dissemination of IPv4 FLow Specification Information  . . . .   6
     4.1.  Length Encoding . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  NLRI Value Encoding . . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Type 1 - Destination Prefix . . . . . . . . . . . . .   8
       4.2.2.  Type 2 - Source Prefix  . . . . . . . . . . . . . . .   8
       4.2.3.  Type 3 - IP Protocol  . . . . . . . . . . . . . . . .   8
       4.2.4.  Type 4 - Port . . . . . . . . . . . . . . . . . . . .  10
Show full document text