Dissemination of Flow Specification Rules
draft-hares-idr-rfc5575bis-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-05
Replaced by draft-hr-idr-rfc5575bis
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                               S. Hares
Internet-Draft                                                    Huawei
Intended status: Standards Track                            J. McPherson
Expires: January 6, 2017                                        Verisign
                                                                J. Mauch
                                                             NTT America
                                                            July 5, 2016

               Dissemination of Flow Specification Rules
                   draft-hares-idr-rfc5575bis-00.txt

Abstract

   This document 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 (IPv4,
   IPv6), MPLS addresses, L2VPN addresses, and NV03 encapsulation of IP
   addresses.  The information is carried via the BGP, thereby reusing
   protocol algorithms, operational experience, and administrative
   processes such as inter-provider peering agreements.

   This document provides the definition of a BGP NLRI which carries
   traffic flow specification filters, and Extended Community values
   which encode the actions a routing system can take if a packet
   matches the traffic flow filters.  The specification requires that
   the BGP Flow Specification traffic filters follows a string ordering,
   and that the BGP Flow Specification Extended Communities actions are
   processed in a defined order.  This BGP Flow Specification is denoted
   as BGP Flow Specification version 1.

   There are three applications of that encoding format: 1) automation
   of inter-domain coordination of traffic filtering, such as what is
   required in order to mitigate (distributed) denial-of-service
   attacks; 2) enable traffic filtering in the context of a BGP/MPLS VPN
   service, and 3) aid 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.  Other deployments (especially SDN/NFV) need
   to be able to allow the user to order the flow specification.
   Another BGP Flow Specification (version 2) is being defined for user-
   ordered filters, and user-ordered actions encoded in Wide
   Communities.

Hares, et al.            Expires January 6, 2017                [Page 1]
Internet-Draft                 RFC5575bis                      July 2016

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 http://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 January 6, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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  . . . . . . . . . . .   6
   3.  Flow Specifications . . . . . . . . . . . . . . . . . . . . .   6
   4.  Traffic Filtering . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Support for other AFIs  . . . . . . . . . . . . . . . . .   8
   5.  Dissemination of IPv4 FLow Specification Information  . . . .   8
     5.1.  Length Encoding . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  NLRI Value Encoding . . . . . . . . . . . . . . . . . . .   9
       5.2.1.  Type 1 - Destination Prefix . . . . . . . . . . . . .  12
       5.2.2.  Type 2 - Source Prefix  . . . . . . . . . . . . . . .  12
       5.2.3.  Type 3 - Source Prefix  . . . . . . . . . . . . . . .  12
Show full document text