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

Document Type Active Internet-Draft (idr WG)
Last updated 2019-11-04
Replaces draft-hr-idr-rfc5575bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Jie Dong
Shepherd write-up Show (last changed 2019-07-09)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Jie Dong <jie.dong@huawei.com>, aretana.ietf@gmail.com
IDR Working Group                                               C. Loibl
Internet-Draft                                 Next Layer Communications
Obsoletes: 5575,7674 (if approved)                              S. Hares
Intended status: Standards Track                                  Huawei
Expires: May 7, 2020                                           R. Raszuk
                                                            Bloomberg LP
                                                            D. McPherson
                                                                Verisign
                                                               M. Bacher
                                                        T-Mobile Austria
                                                        November 4, 2019

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

Abstract

   This document obsoletes both RFC5575 and RFC7674.

   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.

   It also specifies BGP Extended Community encoding formats, that can
   be used to propagate Traffic Filtering Actions along with the Flow
   Specification NLRI.  Those Traffic Filtering Actions encode actions a
   routing system can take if the packet matches the Flow Specification.

   Additionally, it defines two applications of that encoding format:
   one that can be used to automate inter-domain coordination of traffic
   filtering, such as what is required in order to mitigate
   (distributed) denial-of-service attacks, and a second application to
   provide traffic filtering in the context of a BGP/MPLS VPN service.
   Other applications (ie. centralized control of traffic in a SDN or
   NFV context) are also possible.  Other drafts specify IPv6, MPLS
   addresses, L2VPN addresses, and NV03 encapsulation of IP addresses as
   Flow Specification extensions.

   The information is carried via the BGP, thereby reusing protocol
   algorithms, operational experience, and administrative processes such
   as inter-provider peering agreements.

Loibl, et al.              Expires May 7, 2020                  [Page 1]
Internet-Draft             Flow Specification              November 2019

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 May 7, 2020.

Copyright Notice

   Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . .   5
   4.  Dissemination of IPv4 FLow Specification Information  . . . .   6
     4.1.  Length Encoding . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  NLRI Value Encoding . . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Operators . . . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Components  . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Examples of Encodings . . . . . . . . . . . . . . . . . .  13
   5.  Traffic Filtering . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  Ordering of Flow Specifications . . . . . . . . . . . . .  17
   6.  Validation Procedure  . . . . . . . . . . . . . . . . . . . .  18
   7.  Traffic Filtering Actions . . . . . . . . . . . . . . . . . .  19
     7.1.  Traffic Rate in Bytes (traffic-rate-bytes) sub-type 0x06   20

Show full document text