BGP Dissemination of L2VPN Flow Specification Rules
draft-ietf-idr-flowspec-l2vpn-09

Document Type Active Internet-Draft (idr WG)
Last updated 2019-01-03
Replaces draft-hao-idr-flowspec-evpn
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             W. Hao
Internet-Draft                                               D. Eastlake
Intended status: Standards Track                                  Huawei
Expires: July 7, 2019                                          J. Uttaro
                                                                    AT&T
                                                            S. Litkowski
                                                 Orange Business Service
                                                               S. Zhuang
                                                                  Huawei
                                                        January 03, 2019

          BGP Dissemination of L2VPN Flow Specification Rules
                    draft-ietf-idr-flowspec-l2vpn-09

Abstract

   This document defines a BGP flow-spec extension to disseminate L2 VPN
   Ethernet traffic filtering rules.  SAFI=134 in [RFC5575] is redefined
   for this purpose.  A new subset of component types and extended
   community also are defined.  A new subset of component types and new
   extended community also are defined.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 July 7, 2019.

Hao, et al.               Expires July 7, 2019                  [Page 1]
Internet-Draft               L2VPN Flow Spec                January 2019

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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Layer 2 Flow Specification encoding in BGP  . . . . . . . . .   3
   3.  Ethernet Flow Specification encoding in BGP . . . . . . . . .   4
     3.1.  Order of Traffic Filtering Rules  . . . . . . . . . . . .   6
   4.  Ethernet Flow Specification Traffic Actions . . . . . . . . .   7
     4.1.  VLAN-action . . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  TPID-action . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   BGP Flow-spec is an extension to BGP that supports the dissemination
   of traffic flow specification rules.  It leverages the BGP Control
   Plane to simplify the distribution of ACLs.  Using this extension new
   filter rules can be injected to all BGP peers simultaneously without
   changing router configuration.  The typical application of BGP Flow-
   spec is to automate the distribution of traffic filter lists to
   routers for DDOS mitigation, access control, etc.

   [RFC5575] defines a new BGP Network Layer Reachability
   Information(NLRI) format used to distribute traffic flow
   specification rules.  NLRI (AFI=1, SAFI=133) is for IPv4 unicast
   filtering.  NLRI (AFI=1, SAFI=134) is for BGP/MPLS VPN filtering.
   The Flow specification match part only includes L3/L4 information

Hao, et al.               Expires July 7, 2019                  [Page 2]
Show full document text