--- 1/draft-ietf-idr-flowspec-l2vpn-07.txt 2018-07-02 09:13:21.082463388 -0700 +++ 2/draft-ietf-idr-flowspec-l2vpn-08.txt 2018-07-02 09:13:21.110464057 -0700 @@ -1,138 +1,138 @@ Network Working Group W. Hao Internet-Draft Q. Liang Intended status: Standards Track Huawei -Expires: January 4, 2018 J. Uttaro +Expires: January 4, 2019 J. Uttaro AT&T S. Litkowski Orange Business Service S. Zhuang Huawei - July 03, 2017 + July 03, 2018 Dissemination of Flow Specification Rules for L2 VPN - draft-ietf-idr-flowspec-l2vpn-07 + draft-ietf-idr-flowspec-l2vpn-08 Abstract - This document defines BGP flow-spec extension for Ethernet traffic + This document defines BGP Flow-Spec extension for Ethernet traffic filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for dissemination traffic filtering information in an L2VPN environment. A new subset of component types and 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 http://datatracker.ietf.org/drafts/current/. + 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 January 4, 2018. + This Internet-Draft will expire on January 4, 2019. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 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 + (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 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 - 8.2. Informative References . . . . . . . . . . . . . . . . . 12 + 8.2. Informative References . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction BGP Flow-spec is an extension to BGP that allows for the dissemination of traffic flow specification rules. It leverages the BGP Control Plane to simplify the distribution of ACLs, 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 + [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 like source/destination prefix, protocol, ports, and etc, so traffic flows can only be selectively filtered based on L3/L4 information. Layer 2 Virtual Private Networks (L2VPNs) have already been deployed in an increasing number of networks today. In L2VPN network, we also - have requirement to deploy BGP Flow-spec to mitigate DDoS attack + have requirement to deploy BGP Flow-Spec to mitigate DDoS attack traffic. Within L2VPN network, both IP and non-IP Ethernet traffic maybe exist. For IP traffic filtering, the Flow specification rules defined in [RFC5575] which include match criteria and actions can still be used, flow specification rules received via new NLRI format apply only to traffic that belongs to the VPN instance(s) in which it is imported. For non-IP Ethernet traffic filtering, Layer 2 related information like source/destination MAC and VLAN should be considered. But the flow specification match criteria defined in - RFC5575 only include layer 3 and layer 4 IP information, layer 2 + [RFC5575] only include layer 3 and layer 4 IP information, layer 2 Ethernet information haven't been included. - There are different kinds of L2VPN networks like EVPN [EVPN], BGP + There are different kinds of L2VPN networks like EVPN [RFC7432], BGP VPLS [RFC4761], LDP VPLS [RFC4762] and border gateway protocol (BGP) auto discovery [RFC 6074]. Because the flow-spec feature relies on BGP protocol to distribute traffic filtering rules, so it can only be incrementally deployed in those L2VPN networks where BGP has already been used for auto discovery and/or signaling purposes such as BGP- - based VPLS [4761], EVPN and LDP-based VPLS [4762] with BGP auto- - discovery [6074]. + based VPLS [RFC4761], EVPN [RFC7432] and LDP-based VPLS [RFC4762] + with BGP auto-discovery [RFC6074]. This draft proposes a new subset of component types and extended community to support L2VPN flow-spec application. The flow-spec rules can be enforced on all border routers or on some interface sets of the border routers. SAFI=134 in [RFC5575] is redefined for dissemination traffic filtering information in an L2VPN environment. 2. Layer 2 Flow Specification encoding in BGP The [RFC5575] defines SAFI 133 and SAFI 134 for "dissemination of IPv4 flow specification rules" and "dissemination of VPNv4 flow - specification rules" respectively. [draft-ietf-idr-flow-spec-v6-06] + specification rules" respectively. [I-D.ietf-idr-flow-spec-v6] redefines the [RFC5575] SAFIs in order to make them applicable to both IPv4 and IPv6 applications. This document will further redefine the SAFI 134 in order to make them applicable to L2VPN applications. The following changes are defined: "SAFI 134 for dissemination of L3VPN flow specification rules" to now be defined as "SAFI 134 for dissemination of VPN flow specification rules" @@ -146,23 +146,23 @@ The NLRI format for this address family consists of a fixed-length Route Distinguisher field (8 bytes) followed by a flow specification, following the encoding defined in this document. The NLRI length field shall include both the 8 bytes of the Route Distinguisher as well as the subsequent flow specification. Flow specification rules received via this NLRI apply only to traffic that belongs to the VPN instance(s) in which it is imported. Flow rules are accepted by default, when received from remote PE routers. - Besides the component types defined in [RFC5575] and [draft-ietf-idr- - flow-spec-v6-06], this document proposes the following additional - component types for L2VPN Ethernet traffic filtering: + Besides the component types defined in [RFC5575] and + [I-D.ietf-idr-flow-spec-v6], this document proposes the following + additional component types for L2VPN Ethernet traffic filtering: Type 14 - Ethernet Type Encoding: Defines a list of {operation, value} pairs used to match two-octet field. Values are encoded as 2-byte quantities. Ethernet II framing defines the two-octet Ethernet Type field in an Ethernet frame, preceded by destination and source MAC addresses, that identifies an upper layer protocol encapsulating the frame data. @@ -292,21 +292,21 @@ // equal, longest string has precedence } } return EQUAL; } 4. Ethernet Flow Specification Traffic Actions The default action for a layer 2 traffic filtering flow specification is to accept traffic that matches that particular rule. The - following extended community values per RFC5575 can be used to + following extended community values per [RFC5575] can be used to specify particular actions in L2VPN network: +--------+--------------------+--------------------------+ | type | extended community | encoding | +--------+--------------------+--------------------------+ | 0x8006 | traffic-rate | 2-byte as#, 4-byte float | | 0x8007 | traffic-action | bitmask | | 0x8008 | redirect | 6-byte Route Target | | 0x8009 | traffic-marking | DSCP value | +--------+--------------------+--------------------------+ @@ -413,21 +413,21 @@ 5. IANA Considerations IANA is requested to rename currently defined SAFI 134 per [RFC5575] to read: 134 VPN dissemination of flow specification rules IANA is requested to create and maintain a new registry for "Flow spec L2VPN Component Types". For completeness, the types defined in - [RFC5575] and [draft-ietf-idr-flow-spec-v6-06] also are listed here. + [RFC5575] and [I-D.ietf-idr-flow-spec-v6] also are listed here. +--------+-------------------------------+--------------------------+ | type | RFC or Draft | discription | +--------+-------------------------------+--------------------------+ | 1 |RFC5575 | Destination Prefix | | 1 |draft-ietf-idr-flow-spec-v6-06 | Destination IPv6 Prefix | | 2 |RFC5575 | Source Prefix | | 2 |draft-ietf-idr-flow-spec-v6-06 | Source IPv6 Prefix | | 3 |RFC5575 | IP Protocol | | 3 |draft-ietf-idr-flow-spec-v6-06 | Next Header | @@ -467,58 +467,64 @@ 0x080B Flow spec TPID action [this document] 6. Security Considerations No new security issues are introduced to the BGP protocol by this specification. 7. Acknowledgements The authors wish to acknowledge the important contributions of Hannes - Gredler, Xiaohu Xu, Zhenbin Li and Lucy Yong. + Gredler, Xiaohu Xu, Zhenbin Li, Lucy Yong and Feng Dong. 8. References 8.1. Normative References + [I-D.ietf-idr-flow-spec-v6] + McPherson, D., Raszuk, R., Pithawala, B., + akarch@cisco.com, a., and S. Hares, "Dissemination of Flow + Specification Rules for IPv6", draft-ietf-idr-flow-spec- + v6-09 (work in progress), November 2017. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, - . + . [RFC4761] Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007, - . + . [RFC4762] Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007, - . + . [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., and D. McPherson, "Dissemination of Flow Specification Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, - . + . [RFC6074] Rosen, E., Davie, B., Radoaca, V., and W. Luo, "Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)", RFC 6074, DOI 10.17487/RFC6074, January 2011, - . + . 8.2. Informative References [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February - 2015, . + 2015, . Authors' Addresses Weiguo Hao Huawei 101 Software Avenue, Nanjing 210012 China Email: haoweiguo@huawei.com