draft-ietf-idr-flowspec-l2vpn-13.txt   draft-ietf-idr-flowspec-l2vpn-14.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
INTERNET-DRAFT W. Hao INTERNET-DRAFT W. Hao
Intended Status: Proposed Standard Huawei Technologies Intended Status: Proposed Standard Huawei Technologies
D. Eastlake D. Eastlake
Futurewei Technologies Futurewei Technologies
J. Uttaro J. Uttaro
AT&T AT&T
S. Litkowski S. Litkowski
Cisco Systems Cisco Systems
S. Zhuang S. Zhuang
Huawei Technologies Huawei Technologies
Expires: June 30, 2020 December 31, 2019 Expires: October 11, 2020 April 12, 2020
BGP Dissemination of L2 Flow Specification Rules BGP Dissemination of L2 Flow Specification Rules
draft-ietf-idr-flowspec-l2vpn-13 draft-ietf-idr-flowspec-l2vpn-14
Abstract Abstract
This document defines a Border Gateway Protocol (BGP) Flow-spec This document defines a Border Gateway Protocol (BGP) Flow
extension to disseminate Ethernet Layer 2 (L2) and Layer 2 Virtual Specification (flowspec) extension to disseminate Ethernet Layer 2
Private Network (L2VPN) traffic filtering rules either by themselves (L2) and Layer 2 Virtual Private Network (L2VPN) traffic filtering
or in conjunction with L3 Flow-specs. AFI/SAFI 6/133 and 25/134 are rules either by themselves or in conjunction with L3 flowspecs.
used for these purposes. New component types and an extended AFI/SAFI 6/133 and 25/134 are used for these purposes. New component
community also are defined. types and an extended community also are defined.
Status of This Document Status of This Document
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Distribution of this document is unlimited. Comments should be sent Distribution of this document is unlimited. Comments should be sent
to the authors or the IDR Working Group mailing list <idr@ietf.org>. to the authors or the IDR Working Group mailing list <idr@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1. Introduction............................................3 1. Introduction............................................3
1.1 Terminology............................................4 1.1 Terminology............................................4
2. Layer 2 Flow Specification Encoding.....................5 2. Layer 2 Flow Specification Encoding.....................5
2.1 L2 Component Types.....................................6 2.1 L2 Component Types.....................................6
2.1.1 Type 1 - Ethernet Type (EtherType)...................6 2.1.1 Type 1 - Ethernet Type (EtherType)...................6
2.1.2 Type 2 - Source MAC..................................7 2.1.2 Type 2 - Source MAC..................................7
2.1.3 Type 3 - Destination MAC.............................7 2.1.3 Type 3 - Destination MAC.............................7
2.1.4 Type 4 - DSAP (Destination Service Access Point).....7 2.1.4 Type 4 - DSAP (Destination Service Access Point).....7
2.1.5 Type 5 - SSAP (Source Service Access Point)..........7 2.1.5 Type 5 - SSAP (Source Service Access Point)..........7
2.1.6 Type 6 - Control field in LLC........................7 2.1.6 Type 6 - Control field in LLC........................8
2.1.7 Type 7 - SNAP........................................8 2.1.7 Type 7 - SNAP........................................8
2.1.8 Type 8 - VLAN ID.....................................8 2.1.8 Type 8 - VLAN ID.....................................8
2.1.9 Type 9 - VLAN PCP....................................8 2.1.9 Type 9 - VLAN PCP....................................8
2.1.10 Type 10 - Inner VLAN ID.............................8 2.1.10 Type 10 - Inner VLAN ID.............................9
2.1.11 Type 11 - Inner VLAN PCP............................9 2.1.11 Type 11 - Inner VLAN PCP............................9
2.1.12 Type 12 - VLAN DEI..................................9 2.1.12 Type 12 - VLAN DEI..................................9
2.1.13 Type 13 - Inner VLAN DEI............................9 2.1.13 Type 13 - Inner VLAN DEI...........................10
2.1.14 Type 14 - Source MAC Special Bits...................9 2.1.14 Type 14 - Source MAC Special Bits..................10
2.1.15 Type 15 - Destination MAC Special Bits.............10 2.1.15 Type 15 - Destination MAC Special Bits.............10
2.2 Order of L2 Traffic Filtering Rules...................10 2.2 Order of Traffic Filtering Rules......................10
3. L2VPN Flow Specification Encoding in BGP...............12 3. L2VPN Flow Specification Encoding in BGP...............12
3.1 Order of L2VPN Filtering Rules........................12 3.1 Order of L2VPN Filtering Rules........................12
4. Ethernet Flow Specification Traffic Actions............13 4. Ethernet Flow Specification Traffic Actions............13
4.1 VLAN-action...........................................13 4.1 VLAN-action...........................................13
4.2 TPID-action...........................................15 4.2 TPID-action...........................................15
5. Flow Spec Validation...................................16 5. Flow Spec Validation...................................16
6. IANA Considerations....................................17 6. IANA Considerations....................................17
7. Security Considerations................................19
7. Security Considerations................................18 8. Acknowledgements.......................................19
8. Acknowledgements.......................................18 9. Contributors...........................................19
9. Contributors...........................................18
Normative References......................................19 Normative References......................................20
Informative References....................................20 Informative References....................................21
Authors' Addresses........................................22
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
1. Introduction 1. Introduction
Border Gateway Protocol (BGP) Flow-spec [RFC5575bis] is an extension Border Gateway Protocol (BGP) Flow Specification [RFC5575bis]
to BGP that supports the dissemination of traffic flow specification (flowspec) is an extension to BGP that supports the dissemination of
rules and actions to be taken on packets in a specified flow. It traffic flow specification rules and actions to be taken on packets
leverages the BGP Control Plane to simplify the distribution of ACLs in a specified flow. It leverages the BGP Control Plane to simplify
(Access Control Lists). Using the Flow-spec extension new filter the distribution of ACLs (Access Control Lists). Using the Flow
rules can be injected to all BGP peers simultaneously without Specification extension new filter rules can be injected to all BGP
changing router configuration. A typical application is to automate peers simultaneously without changing router configuration. A
the distribution of traffic filter lists to routers for DDoS typical application is to automate the distribution of traffic filter
(Distributed Denial of Service) mitigation, access control, and lists to routers for DDoS (Distributed Denial of Service) mitigation,
similar applications. access control, and similar applications.
BGP Flow-spec [RFC5575bis] defines a BGP Network Layer Reachability BGP Flow Specification [RFC5575bis] defines a BGP Network Layer
Information (NLRI) format used to distribute traffic flow Reachability Information (NLRI) format used to distribute traffic
specification rules. NLRI (AFI=1, SAFI=133) is for IPv4 unicast flow specification rules. The NLRI for (AFI=1, SAFI=133) specifies
filtering. NLRI (AFI=1, SAFI=134) is for IPv4 BGP/MPLS VPN filtering IPv4 unicast filtering. The NLRI for (AFI=1, SAFI=134) specifies
[RFC7432]. The Flow specification match part defined in [RFC5575bis] IPv4 BGP/MPLS VPN filtering [RFC7432]. The Flow Specification match
only includes L3/L4 information like IPv4 source/destination prefix, part defined in [RFC5575bis] only includes L3/L4 information like
protocol, ports, and the like, so traffic flows can only be filtered IPv4 source/destination prefix, protocol, ports, and the like, so
based on L3/L4 information. This has been extended by [FlowSpecV6] traffic flows can only be filtered based on L3/L4 information. This
which covers IPv6 (AFI=2) L3/L4. has been extended by [FlowSpecV6] to cover IPv6 (AFI=2) L3/L4.
Layer 2 Virtual Private Networks (L2VPNs) have been deployed in an Layer 2 Virtual Private Networks (L2VPNs) have been deployed in an
increasing number of networks. Such networks also have requirements increasing number of networks. Such networks also have requirements
to deploy BGP Flow-spec to mitigate DDoS attack traffic. Within an to deploy BGP Flow Specification to mitigate DDoS attack traffic.
L2VPN network, both IP and non-IP Ethernet traffic maybe exist. For Within an L2VPN network, both IP and non-IP Ethernet traffic may
IP traffic filtering, the VPN Flow specification rules defined in exist. For IP traffic filtering, the VPN Flow Specification rules
[RFC5575bis] and/or [FlowSpecV6], which include match criteria and defined in [RFC5575bis] and/or [FlowSpecV6], which include match
actions, can still be used. Flow specification rules received via the criteria and actions, can still be used. For non-IP Ethernet traffic
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 filtering, Layer 2 related information like source/destination MAC
and VLAN must be considered. and VLAN must be considered.
There are different kinds of L2VPN networks like EVPN [RFC7432], BGP There are different kinds of L2VPN networks like EVPN [RFC7432], BGP
VPLS [RFC4761], LDP VPLS [RFC4762] and border gateway protocol (BGP) VPLS [RFC4761], LDP VPLS [RFC4762] and border gateway protocol (BGP)
auto discovery [RFC6074]. Because the Flow-spec feature relies on auto discovery [RFC6074]. Because the Flow Specification feature
the BGP protocol to distribute traffic filtering rules, it can only relies on the BGP protocol to distribute traffic filtering rules, it
be incrementally deployed in those L2VPN networks where BGP has can only be incrementally deployed in those L2VPN networks where BGP
already been used for auto discovery and/or signaling purposes such has already been used for auto discovery and/or signaling purposes
as BGP-based VPLS [RFC4761], EVPN and LDP-based VPLS [RFC4762] with such as BGP-based VPLS [RFC4761], EVPN, and LDP-based VPLS [RFC4762]
BGP auto-discovery [RFC6074]. with BGP auto-discovery [RFC6074].
This draft defines new Flow-spec component types and two new extended This document defines new flowspec component types and two new
communities to support L2 and L2VPN Flow-spec applications. The extended communities to support L2 and L2VPN flowspec applications.
Flow-spec rules can be enforced on all border routers or on some The flowspec rules can be enforced on all border routers or on some
interface sets of the border routers. SAFI=133 in [RFC5575bis] and interface sets of the border routers. SAFI=133 in [RFC5575bis] and
[FlowSpecV6] is extended for AFI=6 as specified in Section 2 to cover [FlowSpecV6] is extended for AFI=6 as specified in Section 2 to cover
L2 traffic filtering information and in Section 3 SAFI=134 is L2 traffic filtering information and in Section 3 SAFI=134 is
extended for AFI=25 to cover the L2VPN environment.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
extended for AFI=25 to cover the L2VPN environment.
1.1 Terminology 1.1 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
The following acronyms are used in this document: The following acronyms and terms are used in this document:
AFI - Address Family Identifier AFI - Address Family Identifier
ACL - Access Control List ACL - Access Control List
DDoS - Distributed Denial of Service DDoS - Distributed Denial of Service
DEI - Drop Eligible Indicator
EVPN - Ethernet VPN [RFC7432] EVPN - Ethernet VPN [RFC7432]
flowspec - BGP Flow Specification
L2 - Layer 2 L2 - Layer 2
L2VPN - Layer 2 VPN L2VPN - Layer 2 VPN
L3 - Layer 3 L3 - Layer 3
L3VPN - Layer 3 VPN L3VPN - Layer 3 VPN
NLRI - Network Layer Reachability Information NLRI - Network Layer Reachability Information
skipping to change at page 5, line 16 skipping to change at page 5, line 16
2. Layer 2 Flow Specification Encoding 2. Layer 2 Flow Specification Encoding
[RFC5575bis] defines SAFI 133 and SAFI 134, with AFI=1, for [RFC5575bis] defines SAFI 133 and SAFI 134, with AFI=1, for
"dissemination of IPv4 flow specification rules" and "dissemination "dissemination of IPv4 flow specification rules" and "dissemination
of VPNv4 flow specification rules", respectively. [FlowSpecV6]] of VPNv4 flow specification rules", respectively. [FlowSpecV6]]
extends [RFC5575bis] to also allow AFI=2 thus making it applicable to extends [RFC5575bis] to also allow AFI=2 thus making it applicable to
both IPv4 and IPv6 applications. This document further extends both IPv4 and IPv6 applications. This document further extends
SAFI=133 for AFI=6 and SAFI=134 for AFI=25 to make them applicable to SAFI=133 for AFI=6 and SAFI=134 for AFI=25 to make them applicable to
L2 and L2VPN applications. This document also provides for the L2 and L2VPN applications. This document also provides for the
optional inclusion of L3 flow specifications with the L2 flow optional combination of L3 flow specifications with these L2 flow
specifications. specifications.
This section specifies the L2 Flow Spec for AFI=6/SAFI=133. (SAFI=133 This section specifies the L2 flowspec for AFI=6/SAFI=133. To
is updated by the [FlowSpecV6] draft so as to not be restricted to simplify assignments, a new registry is used for L2 flowspec. Since
the Layer of the AFI with which it operates.) To simplify it is frequently desirable to also filter on L3/L4 fields, provision
assignments, a new registry is used for L2 Flow-spec. Since it is is made for their inclusion along with an indication of the L3
frequently desirable to also filter on L3/L4 fields, provision is protocol involved (IPv4 or IPv6).
made for their inclusion along with an indication of the L3 protocol
involved (IPv4 or IPv6).
The NLRI part of the MP_REACH_NLRI and MP_UNREACH_NLRI is encoded as The NLRI part of the MP_REACH_NLRI and MP_UNREACH_NLRI is encoded as
a 1- or 2-octet total NLRI length field followed by several fields as a 1- or 2-octet total NLRI length field followed by several fields as
described below. described below.
+-------------------------------+ +-------------------------------+
| total-length (0xnn or 0xfnnn) | 2 or 3 octets | total-length (0xnn or 0xfnnn) | 2 or 3 octets
+-------------------------------+ +-------------------------------+
| L3-AFI | 2 octets | L3-AFI | 2 octets
+-------------------------------+ +-------------------------------+
| L2-length (0xnn or 0xfnnn) | 2 or 3 octets | L2-length (0xnn or 0xfnnn) | 2 or 3 octets
+-------------------------------+ +-------------------------------+
| NLRI-value | variable | NLRI-value | variable
+-------------------------------+ +-------------------------------+
Figure 1: Flow Specification NLRI for L2 Figure 1: Flow Specification NLRI for L2
The fields show in Figure 1 are further specified below: The fields show in Figure 1 are further specified below:
total-length: The length of the subsequent fields (L3 AFI, total-length: The length of the subsequent fields (L3 AFI,
L2-length, and NRLI-vaue) encoded as provided in Section 4.1 of L2-length, and NRLI-value) encoded as provided in Section 4.1
[RFC5575bis]. If this field is less than 4, which is the of [RFC5575bis]. If this field is less than 4, which is the
minimum valid value, then the NLRI is malformed in which case a minimum valid value, then the NLRI is malformed in which case a
NOTIFICATION message is sent and the BGP connection closed as NOTIFICATION message is sent and the BGP connection closed as
provided in Section 6.3 of [RFC4271]. provided in Section 6.3 of [RFC4271].
L3-AFI: If no L3/L4 filtering is desired, this two octet field L3-AFI: If no L3/L4 filtering is desired, this two octet field
MUST be zero. Otherwise it indicates the L3 protocol involved MUST be zero which is a reserved AFI value. Otherwise L3-AFI
by giving its AFI (0x0001 for IPv4 or 0x0002 for IPv6). If the indicates the L3 protocol involved by giving its AFI (0x0001
receiver does not understand the value of this field, the for IPv4 or 0x0002 for IPv6). If the receiver does not
MP_REACH or MP_UNREACH attribute is ignored. understand the value of the L3-AFI field, the MP_REACH or
MP_UNREACH attribute is ignored.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
L2-length: The length of the L2 components at the beginning of the L2-length: The length of the L2 components at the beginning of the
NLRI-value field encoded as provided in Section 4.1 of NLRI-value field encoded as provided in Section 4.1 of
[RFC5575bis]. If the value of this field indicates that the L2 [RFC5575bis]. If the value of this field indicates that the L2
components extend beyond the total-length, the NLRI is components extend beyond the total-length, the NLRI is
malformed in which case a NOTIFICATION message is sent and the malformed in which case a NOTIFICATION message is sent and the
BGP connection closed as provided in Section 6.3 of [RFC4271]. BGP connection closed as provided in Section 6.3 of [RFC4271].
N2-length MAY be zero although, in that case, it would have N2-length MAY be zero although, in that case, it would have
been more efficient to encode the attribute as an L3 Flow spec been more efficient to encode the attribute as an L3 Flow spec
unless it is desired to apply an L2 action (see Section 4). A unless it is desired to apply an L2 action (see Section 4). A
null L2 Flow-spec always matches. null L2 flowspec always matches.
NLRI-value: This consists of the L2 Flow Spec, of length NLRI-value: This consists of the L2 flowspec, of length L2-length,
L2-length, followed by an optionally present L3 Flow. The followed by an optionally present L3 flowspec. The result can
result can be treated in most ways as a single Flow spec, be treated in most ways as a single flowspec, matching the
matching the intersection (AND) of all the components except intersection (AND) of all the components except that the
that the components in the initial L2 region are interpreted as components in the initial L2 region are interpreted as L2
L2 components and the remainder as L3 components per the L3-AFI components and the remainder as L3 components per the L3-AFI
field. This is necessary because there are different registries field. This is necessary because there are different registries
for the L2, L3 IPv4, and L3 IPv6 component types. If the L3 for the L2, L3 IPv4, and L3 IPv6 component types. If the L3
Flow-spec is null (length zero), it always matches. flowspec is null (length zero), it always matches.
2.1 L2 Component Types 2.1 L2 Component Types
The L2 Flow-spec portion of NLRI-value consists of Flow-spec The L2 flowspec portion of the NLRI-value consists of flowspec
components as in [RFC5575bis] but using L2 components and types as components as in [RFC5575bis] but using L2 components and types as
specified below. All components start with a type octet followed by a specified below. All components start with a type octet followed by a
length octet followed by any additional information needed. The length octet followed by any additional information needed. The
length octet give the length, in octets, of the information after the length octet give the length, in octets, of the information after the
length octet. This structure applies to all new components to be length octet. This structure applies to all new components to be
defined in the L2 Flow-spec Component Registry (see Section 6) and to defined in the L2 Flow-spec Component Registry (see Section 6) and to
all existing components except Types 2 and 3 where the length is in all existing components except Types 2 and 3 where the length is in
bits. bits.
2.1.1 Type 1 - Ethernet Type (EtherType) 2.1.1 Type 1 - Ethernet Type (EtherType)
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match the two- Defines a list of {operation, value} pairs used to match the two-
octet EtherType field. op is encoded as specified in Section 4.2.1.1 octet EtherType field. op is encoded as specified in Section 4.2.1.1
of [RFC5575bis]. Values are encoded as 2-octet quantities. Ethernet of [RFC5575bis]. Values are encoded as 2-octet quantities. Ethernet
II framing defines the two-octet Ethernet Type (EtherType) field in II framing defines the two-octet Ethernet Type (EtherType) field in
an Ethernet frame, preceded by destination and source MAC addresses, an Ethernet frame, preceded by destination and source MAC addresses,
that identifies an upper layer protocol encapsulating the frame data. that identifies an upper layer protocol encapsulating the frame data.
The match fails if LLC encoding is being used rather than EtherType
encoding.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
2.1.2 Type 2 - Source MAC 2.1.2 Type 2 - Source MAC
Encoding: <type (1 octet), MAC Prefix length (1 octet), MAC Prefix> Encoding: <type (1 octet), MAC Prefix length (1 octet), MAC Prefix>
Defines the source MAC Address prefix to match encoded as in BGP Defines the source MAC Address prefix to match encoded as in BGP
UPDATE messages [RFC4271]. Prefix length is in bits and the MAC UPDATE messages [RFC4271]. Prefix length is in bits and the MAC
Prefix is fill out with unused bit to an integer number of octets. Prefix is fill out with from 1 to 7 padding bits so that it is an
integer number of octets. These padding bits are ignored for matching
purposes.
2.1.3 Type 3 - Destination MAC 2.1.3 Type 3 - Destination MAC
Encoding: <type (1 octet), MAC Prefix length (1 octet), MAC Prefix> Encoding: <type (1 octet), MAC Prefix length (1 octet), MAC Prefix>
Defines the destination MAC Address to match encoded as in BGP UPDATE Defines the destination MAC Address to match encoded as in BGP UPDATE
messages [RFC4271]. Prefix length is in bits and the MAC Prefix is messages [RFC4271]. Prefix length is in bits and the MAC Prefix is
fill out with unused bit to an integer number of octets. fill out with from 1 to 7 padding bits so that it is an integer
number of octets. These padding bits are ignored for matching
purposes.
2.1.4 Type 4 - DSAP (Destination Service Access Point) 2.1.4 Type 4 - DSAP (Destination Service Access Point)
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match the 1-octet Defines a list of {operation, value} pairs used to match the 1-octet
DSAP in the IEEE 802.2 LLC (Logical Link Control Header). Values are DSAP in the IEEE 802.2 LLC (Logical Link Control Header). Values are
encoded as 1-octet quantities. op is encoded as specified in Section encoded as 1-octet quantities. op is encoded as specified in Section
4.2.1.1 of [RFC5575bis]. 4.2.1.1 of [RFC5575bis]. The match fails if EtherType L2 header
encoding is being used rather than LLC encoding.
2.1.5 Type 5 - SSAP (Source Service Access Point) 2.1.5 Type 5 - SSAP (Source Service Access Point)
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match the 1-octet Defines a list of {operation, value} pairs used to match the 1-octet
SSAP in the IEEE 802.2 LLC. Values are encoded as 1-octet SSAP in the IEEE 802.2 LLC. Values are encoded as 1-octet
quantities. op is encoded as specified in Section 4.2.1.1 of quantities. op is encoded as specified in Section 4.2.1.1 of
[RFC5575bis]. [RFC5575bis]. The match fails if EtherType L2 header encoding is
being used rather than LLC encoding.
INTERNET-DRAFT L2 Flow Spec
2.1.6 Type 6 - Control field in LLC 2.1.6 Type 6 - Control field in LLC
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 1-octet Defines a list of {operation, value} pairs used to match the 1-octet
control field in the IEEE 802.2 LLC. Values are encoded as 1-octet control field in the IEEE 802.2 LLC. Values are encoded as 1-octet
quantities. op is encoded as specified in Section 4.2.1.1 of quantities. op is encoded as specified in Section 4.2.1.1 of
[RFC5575bis]. [RFC5575bis]. The match fails if EtherType L2 header encoding is
being used rather than LLC encoding.
INTERNET-DRAFT L2 Flow Spec
2.1.7 Type 7 - SNAP 2.1.7 Type 7 - SNAP
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 5-octet SNAP Defines a list of {operation, value} pairs used to match 5-octet SNAP
(Sub-Network Access Protocol) field. Values are encoded as 5-octet (Sub-Network Access Protocol) field. Values are encoded as 5-octet
quantities. op is encoded as specified in Section 4.2.1.1 of quantities. op is encoded as specified in Section 4.2.1.1 of
[RFC5575bis]. [RFC5575bis]. The match fails if EtherType L2 header encoding is
being used rather than LLC encoding.
2.1.8 Type 8 - VLAN ID 2.1.8 Type 8 - VLAN ID
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match VLAN ID. Defines a list of {operation, value} pairs used to match VLAN ID.
Values are encoded as 2-octet quantities, where the four most Values are encoded as 2-octet quantities, where the four most
significant bits are zero and the 12 least significant bits contain significant bits are set to zero and ignored for matching and the 12
the VLAN value. op is encoded as specified in Section 4.2.1.1 of least significant bits contain the VLAN value. op is encoded as
[RFC5575bis]. specified in Section 4.2.1.1 of [RFC5575bis].
In the virtual local-area network (VLAN) stacking case, the VLAN ID In the virtual local-area network (VLAN) stacking case, the VLAN ID
is the outer VLAN ID. is the outer VLAN ID.
2.1.9 Type 9 - VLAN PCP 2.1.9 Type 9 - VLAN PCP
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 3-bit VLAN Defines a list of {operation, value} pairs used to match 3-bit VLAN
PCP fields [802.1Q]. Values are encoded using a single octet, where PCP (priority code point) fields [802.1Q]. Values are encoded using
the five most significant bits are zero and the three least a single octet, where the five most significant bits are set to zero
significant bits contain the VLAN PCP value. op is encoded as and ignored for matching and the three least significant bits contain
specified in Section 4.2.1.1 of [RFC5575bis]. the VLAN PCP value. op is encoded as specified in Section 4.2.1.1 of
[RFC5575bis].
INTERNET-DRAFT L2 Flow Spec
In the virtual local-area network (VLAN) stacking case, the VLAN PCP In the virtual local-area network (VLAN) stacking case, the VLAN PCP
is outer VLAN PCP. is part of the outer VLAN tag.
2.1.10 Type 10 - Inner VLAN ID 2.1.10 Type 10 - Inner VLAN ID
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match the inner Defines a list of {operation, value} pairs used to match the inner
VLAN ID using for virtual local-area network (VLAN) stacking or Q-in- VLAN ID using for virtual local-area network (VLAN) stacking or Q-in-
Q use. Values are encoded as 2-octet quantities, where the four most Q use. Values are encoded as 2-octet quantities, where the four most
significant bits are zero and the 12 least significant bits contain significant bits are set to zero and ignored for matching and the 12
the VLAN value. op is encoded as specified in Section 4.2.1.1 of least significant bits contain the VLAN value. op is encoded as
specified in Section 4.2.1.1 of [RFC5575bis].
INTERNET-DRAFT L2 Flow Spec
[RFC5575bis].
In the single VLAN case, this component type MUST NOT be used. If it In the single VLAN case, this component type MUST NOT be used. If it
appears the match will fail. appears the match will fail.
2.1.11 Type 11 - Inner VLAN PCP 2.1.11 Type 11 - Inner VLAN PCP
Encoding: <type (1 octet), length (1 octet), [op, value]+> Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 3-bit inner Defines a list of {operation, value} pairs used to match 3-bit inner
VLAN PCP fields [802.1Q] using for virtual local-area network (VLAN) VLAN PCP fields [802.1Q] using for virtual local-area network (VLAN)
stacking or Q in Q use. Values are encoded using a single octet, stacking or Q in Q use. Values are encoded using a single octet,
where the five most significant bits are zero and the three least where the five most significant bits are set to zero and ignored for
significant bits contain the VLAN PCP value. op is encoded as matching and the three least significant bits contain the VLAN PCP
specified in Section 4.2.1.1 of [RFC5575bis]. value. op is encoded as specified in Section 4.2.1.1 of [RFC5575bis].
In the single VLAN case, this component type MUST NOT be used. If it In the single VLAN case, this component type MUST NOT be used. If it
appears the match will fail. appears the match will fail.
2.1.12 Type 12 - VLAN DEI 2.1.12 Type 12 - VLAN DEI
Encoding: <type (1 octet), length (1 octet), op (1 octet)> Encoding: <type (1 octet), length (1 octet), op (1 octet)>
This type tests the DEI bit in the VLAN tag. If op is zero, it This type tests the DEI (Drop Eligible Indicator) bit in the VLAN
matches if and only if the DEI bit is zero. If op is non-zero, it tag. If op is zero, it matches if and only if the DEI bit is zero. If
matches if and only if the DEI bit is one. op is non-zero, it matches if and only if the DEI bit is one.
In the virtual local-area network (VLAN) stacking case, the VLAN DEI
is part of the outer VLAN tag.
INTERNET-DRAFT L2 Flow Spec
2.1.13 Type 13 - Inner VLAN DEI 2.1.13 Type 13 - Inner VLAN DEI
Encoding: <type (1 octet), length (1 octet), op (1 octet)> Encoding: <type (1 octet), length (1 octet), op (1 octet)>
This type tests the DEI bit in the inner VLAN tag. If op is zero, it This type tests the DEI bit in the inner VLAN tag. If op is zero, it
matches if and only if the DEI bit is zero. If op is non-zero, it matches if and only if the DEI bit is zero. If op is non-zero, it
matches if and only if the DEI bit is one. matches if and only if the DEI bit is one.
In the single VLAN case, this component type MUST NOT be used. If it In the single VLAN case, this component type MUST NOT be used. If it
appears the match will fail. appears the match will fail.
2.1.14 Type 14 - Source MAC Special Bits 2.1.14 Type 14 - Source MAC Special Bits
Encoding: <type (1 octet), length (1 octet), op (1 octet)> Encoding: <type (1 octet), length (1 octet), op (1 octet)>
INTERNET-DRAFT L2 Flow Spec
This type tests the bottom nibble of the top octet of the Source MAC This type tests the bottom nibble of the top octet of the Source MAC
address. The two low order bits of that nibble have long been the address. The two low order bits of that nibble have long been the
local bit (0x2) and the group addressed bit (0x1). However, recent local bit (0x2) and the group addressed bit (0x1). However, recent
changes in IEEE 802 have divided the local address space into 4 changes in IEEE 802 have divided the local address space into 4
quadrants specified by the next two bits (0x4 and 0x8) [RFC7042bis]. quadrants specified by the next two bits (0x4 and 0x8) [RFC7042bis].
This type permits testing, for example, that a MAC is group addressed This flowspec component permits testing, for example, that a MAC is
or is a local address in a particular quadrant. The encoding is as group addressed or is a local address in a particular quadrant. The
given in Section 4.2.1.2 of [RFC5575bis]. encoding is as given in Section 4.2.1.2 of [RFC5575bis].
2.1.15 Type 15 - Destination MAC Special Bits 2.1.15 Type 15 - Destination MAC Special Bits
Encoding: <type (1 octet), length (1 octet), op (1 octet)> Encoding: <type (1 octet), length (1 octet), op (1 octet)>
As discussed in Section 2.1.14 but for the Destination MAC Address. As discussed in Section 2.1.14 but for the Destination MAC Address.
2.2 Order of L2 Traffic Filtering Rules 2.2 Order of Traffic Filtering Rules
L2 Flow-specs take precedence over L3 Flow-specs. Between two L2 The existing rules in Section 5.1 of [RFC5575bis] and in [FlowSpecV6]
Flow-specs, precedence is determined as specified in this section for the ordering of traffic filtering are extended as follows:
after this paragraph. If the L2 Flow-specs are the same, then the L3
Flow-specs are compared as specified in [RFC5575bis or [FlowSpecV6] L2 flowspecs (AFI = 6, 25) take precedence over L3 flowspecs (AFI =
as appropriate. Note: if the L3-AFI fields are different between two 1, 2). Between two L2 flowspecs, precedence of the L2 portion is
L2 Flow-specs, they will never match the same packet so it will not determined as specified in this section after this paragraph. If the
be necessary to prioritize two Flow-specs with different L3-AFI L2 flowspec L2 portions are the same and the L3-AFI is nonzero, then
values. the L3 portions are compared as specified in [RFC5575bis] or
[FlowSpecV6] as appropriate. Note: if the L3-AFI fields are different
between two L2 flowspecs, they will never match the same packet so it
will not be necessary to prioritize two flowspecs with different
L3-AFI values.
INTERNET-DRAFT L2 Flow Spec
The original definition for the order of traffic filtering rules can The original definition for the order of traffic filtering rules can
be reused for L2 with new consideration for the MAC Address offset. be reused for L2 with new consideration for the MAC Address offset.
As long as the offsets are equal, the comparison is the same, As long as the offsets are equal, the comparison is the same,
retaining longest-prefix-match semantics. If the offsets are not retaining longest-prefix-match semantics. If the offsets are not
equal, the lowest offset has precedence, as this flow matches the equal, the lowest offset has precedence, as this flow matches the
most significant bit. most significant bit.
INTERNET-DRAFT L2 Flow Spec
Pseudocode: Pseudocode:
flow_rule_L2_cmp (a, b) flow_rule_L2_cmp (a, b)
{ {
comp1 = next_component(a); comp1 = next_component(a);
comp2 = next_component(b); comp2 = next_component(b);
while (comp1 || comp2) { while (comp1 || comp2) {
// component_type returns infinity on end-of-list // component_type returns infinity on end-of-list
if (component_type(comp1) < component_type(comp2)) { if (component_type(comp1) < component_type(comp2)) {
return A_HAS_PRECEDENCE; return A_HAS_PRECEDENCE;
} }
skipping to change at page 12, line 10 skipping to change at page 12, line 10
} }
} }
return EQUAL; return EQUAL;
} }
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
3. L2VPN Flow Specification Encoding in BGP 3. L2VPN Flow Specification Encoding in BGP
The NLRI format for AFI=25/SAFI=134 (L2VPN), as with the other VPN The NLRI format for AFI=25/SAFI=134 (L2VPN), as with the other VPN
Flow-spec AFI/SAFI pairs, is the same as the non-VPN Flow-Spec but flowspec AFI/SAFI pairs, is the same as the non-VPN Flow-Spec but
with the addition of a Route Distinguisher to identify the VPN to with the addition of a Route Distinguisher to identify the VPN to
which the Flow-spec is to be applied. which the flowspec is to be applied.
In addition, the IANA entry for SAFI 134 is slightly generalized as In addition, the IANA entry for SAFI 134 is slightly generalized as
specified at the beginning of Section 6. specified at the beginning of Section 6.
The NLRI format is as follows: The L2VPN NLRI format is as follows:
+-------------------------------+ +-------------------------------+
| total-length (0xnn or 0xfnnn) | 2 or 3 octets | total-length (0xnn or 0xfnnn) | 2 or 3 octets
+-------------------------------+ +-------------------------------+
| Route Distinguisher | 8 octets | Route Distinguisher | 8 octets
+-------------------------------+ +-------------------------------+
| L3-AFI | 2 octets | L3-AFI | 2 octets
+-------------------------------+ +-------------------------------+
| L2-length (0xnn or 0xfnnn) | 2 or 3 octets | L2-length (0xnn or 0xfnnn) | 2 or 3 octets
+-------------------------------+ +-------------------------------+
skipping to change at page 13, line 9 skipping to change at page 13, line 9
The order between L2VPN filtering rules is determined as specified in The order between L2VPN filtering rules is determined as specified in
Section 2.2. Note that if the Route Distinguisher is different Section 2.2. Note that if the Route Distinguisher is different
between two L2VPN filtering rules, they will never both match the between two L2VPN filtering rules, they will never both match the
same packet so they need not be prioritized. same packet so they need not be prioritized.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
4. Ethernet Flow Specification Traffic Actions 4. Ethernet Flow Specification Traffic Actions
The default action for a layer 2 traffic filtering flow specification The default action for an L2 traffic filtering flowspec is to accept
is to accept traffic that matches that particular rule. The traffic that matches that particular rule. The following extended
following extended community values per [RFC5575bis] can be used to community values per [RFC5575bis] can be used to specify particular
specify particular actions in an L2 VPN network: actions in an L2 VPN network:
+--------+--------------------+----------------------------+ +--------+--------------------+----------------------------+
| type | extended community | encoding | | type | extended community | encoding |
+--------+--------------------+----------------------------+ +--------+--------------------+----------------------------+
| 0x8006 | traffic-rate | 2-octet as#, 4-octet float | | 0x8006 | traffic-rate | 2-octet as#, 4-octet float |
| 0x8007 | traffic-action | bitmask | | 0x8007 | traffic-action | bitmask |
| 0x8008 | redirect | 6-octet Route Target | | 0x8008 | redirect | 6-octet Route Target |
| 0x8009 | traffic-marking | DSCP value | | 0x8009 | traffic-marking | DSCP value |
+--------+--------------------+----------------------------+ +--------+--------------------+----------------------------+
skipping to change at page 14, line 11 skipping to change at page 14, line 11
VLAN-action extended community, such as SwapPop, PushSwap, etc. For VLAN-action extended community, such as SwapPop, PushSwap, etc. For
example, SwapPop action is the sequence of two actions, the first example, SwapPop action is the sequence of two actions, the first
action is Swap and the second action is Pop. action is Swap and the second action is Pop.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|PO1|PU1|SW1|RI1|RO1| Resv |PO2|PU2|SW2|RI2|RO2| Resv | |PO1|PU1|SW1|RI1|RO1| Resv |PO2|PU2|SW2|RI2|RO2| Resv |
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| VLAN ID1 |PCP1 |DE1| | VLAN ID1 | PCP1 |DE1|
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| VLAN ID2 |PCP2 |DE2| | VLAN ID2 | PCP2 |DE2|
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
PO1: Pop action. If the PO1 flag is one, it indicates the outmost PO1: Pop action. If the PO1 flag is one, it indicates the outmost
VLAN should be removed. VLAN should be removed.
PU1: Push action. If PU1 is one, it indicates VLAN ID1 will be PU1: Push action. If PU1 is one, it indicates VLAN ID1 will be
added, the associated PCP and DEI are PCP1 and DE1. added, the associated PCP and DEI are PCP1 and DE1.
SW1: Swap action. If the SW1 flag is one, it indicates the outer SW1: Swap action. If the SW1 flag is one, it indicates the outer
VLAN and inner VLAN should be swapped. VLAN and inner VLAN should be swapped.
PO2: Pop action. If the PO2 flag is one, it indicates the outmost PO2: Pop action. If the PO2 flag is one, it indicates the outmost
VLAN should be removed. VLAN should be removed.
PU2: Push action. If PU2 is one, it indicates VLAN ID2 will be PU2: Push action. If PU2 is one, it indicates VLAN ID2 will be
added, the associated PCP and DEI are PCP2 and DE2. added, the associated PCP and DEI are PCP2 and DE2.
SW2: Swap action. If the SW2 flag is one, it indicates the outer SW2: Swap action. If the SW2 flag is one, it indicates the outer
VLAN and inner VLAN should be swapped. VLAN and inner VLAN should be swapped.
RI1 and RI2: Rewrite inner VLAN action. If the RI flag is one, it RI1 and RI2: Rewrite inner VLAN action. If the RIx flag is one
indicates the inner VLAN should be replaced by a new VLAN where the (where "x" is "1" or "2"), it indicates the inner VLAN should be
new VLAN is VLAN ID1 and the associated PCP and DEO are PCP1 and DE1. replaced by a new VLAN where the new VLAN is VLAN IDx and the
If the VLAN ID1 is 0, the action is to only modify the PCP and DEI associated PCP and DEI are PCPx and DEx. If the VLAN IDx is 0, the
value of the inner VLAN. action is to only modify the PCP and DEI value of the inner VLAN.
RO1 and RO2: Rewrite outer VLAN action. If the RO flag is one, it RO1 and RO2: Rewrite outer VLAN action. If the ROx flag is one
indicates the outer VLAN should be replaced by a new VLAN where the (where "x" is "1" or "2"), it indicates the outer VLAN should be
new VLAN is VLAN ID and the associated PCP and DEI are PCP2 and DE2. replaced by a new VLAN where the new VLAN is VLAN IDx and the
If the VLAN ID2 is 0, the action is to only modify the PCP and DEI associated PCP and DEI are PCPx and DEx. If the VLAN IDx is 0, the
value of the outer VLAN. action is to only modify the PCP and DEI value of the outer VLAN.
Resv, R1, and R2: Reserved for future use. MUST be sent as zero and Resv: Reserved for future use. MUST be sent as zero and ignored on
ignored on receipt. receipt.
Giving an example below: if the action of PUSH Inner VLAN 10 with PCP Giving an example below: if the action of PUSH Inner VLAN 10 with PCP
value 5 DEI value 0 and Outer VLAN 20 with PCP value 6 DEI value 0 is value 5 and DEI value 0 and PUSH Outer VLAN 20 with PCP value 6 and
needed, the format of the VLAN-action extended community is as DEI value 0 is needed, the format of the VLAN-action extended
follows: community is as follows:
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|0 |1 |0 |0 |0 |0 |0 |0 |0 |1 |0 |0 |0 |0 |0 |0 | |0 |1 |0 |0 |0 |0 |0 |0 |0 |1 |0 |0 |0 |0 |0 |0 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 10 |1 |0 |1 |0 | | 10 |1 |0 |1 |0 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 20 |1 |1 |0 |0 | | 20 |1 |1 |0 |0 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
4.2 TPID-action 4.2 TPID-action
The TPID-action extended community consists of 6 octets which The TPID-action extended community consists of 6 octets which
includes the fields of action Flags, TPID1 and TPID2. includes the fields of action Flags, TP ID1 and TP ID2.
0 15 0 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|TI|TO| Resv | |TI|TO| Resv |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TP ID1 | | TP ID1 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TP ID2 | | TP ID2 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
skipping to change at page 16, line 9 skipping to change at page 16, line 9
the outer TP ID should be replaced by a new TP ID, the new TP ID is the outer TP ID should be replaced by a new TP ID, the new TP ID is
TP ID2. TP ID2.
Resv: Reserved for future use. MUST be sent as zero and ignored on Resv: Reserved for future use. MUST be sent as zero and ignored on
receipt. receipt.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
5. Flow Spec Validation 5. Flow Spec Validation
Flow-specs received over AFI=25/SAFI=134 are validated against Flow Specifications received over AFI=25/SAFI=134 are validated
routing reachability received over AFI=25/SAFI=128 as modified to against routing reachability received over AFI=25/SAFI=128 as
conform to [FlowSpecOID]. modified to conform to [FlowSpecOID].
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
6. IANA Considerations 6. IANA Considerations
IANA is requested to change the description for SAFI 134 [RFC5575bis] IANA is requested to change the description for SAFI 134 [RFC5575bis]
to read as follows and to change the reference for it to [this to read as follows and to change the reference for it to [this
document]: document]:
134 VPN dissemination of flow specification rules 134 VPN dissemination of flow specification rules
IANA is requested to create an L2 Flow Spec Component Type registry IANA is requested to create an L2 Flow Specification Component Type
on the Flow Spec Component Types registries web page as follows: registry on the Flow Spec Component Types registries web page as
follows:
Name: L2 Flow Spec Component Types Name: L2 Flow Specification Component Types
Reference: [this document] Reference: [this document]
Registration Procedures: Registration Procedures:
0 Reserved 0 Reserved
1-127 Specification Required 1-127 Specification Required
128-255 First Come First Served 128-255 First Come First Served
Initial contents: Initial contents:
+------+-----------------------+------------------------------+ +------+-----------------------+------------------------------+
| type | Reference | description | | type | Reference | description |
+------+-----------------------+------------------------------+ +------+-----------------------+------------------------------+
skipping to change at page 17, line 46 skipping to change at page 17, line 47
| 7 | [this document] | SNAP | | 7 | [this document] | SNAP |
| 8 | [this document] | VLAN ID | | 8 | [this document] | VLAN ID |
| 9 | [this document] | VLAN PCP | | 9 | [this document] | VLAN PCP |
| 10 | [this document] | Inner VLAN ID | | 10 | [this document] | Inner VLAN ID |
| 11 | [this document] | Inner VLAN PCP | | 11 | [this document] | Inner VLAN PCP |
| 12 | [this document] | VLAN DEI | | 12 | [this document] | VLAN DEI |
| 13 | [this document] | Inner VLAN DEI | | 13 | [this document] | Inner VLAN DEI |
| 14 | [this document] | Source MAC Special Bits | | 14 | [this document] | Source MAC Special Bits |
| 15 | [this document] | Destination MAC Special Bits| | 15 | [this document] | Destination MAC Special Bits|
|16-254| [this document] | unassigned | |16-254| [this document] | unassigned |
| 255 | [this document] | reserved | | 255 | [this document] | Reserved |
+------+-----------------------+------------------------------+ +------+-----------------------+------------------------------+
IANA is requested to assign two values from the "BGP Extended IANA is requested to assign two values from the "BGP Extended
Communities Type - extended, transitive" registry [suggested value Communities Type - extended, transitive" registry [suggested value
provided in square brackets]: provided in square brackets]:
INTERNET-DRAFT L2 Flow Spec
Type value Name Reference Type value Name Reference
------------ ------------------------ --------------- ------------ ------------------------ ---------------
TBD1[0x080A] Flow spec VLAN action [this document] TBD1[0x080A] Flow spec VLAN action [this document]
TBD2[0x080B] Flow spec TPID action [this document] TBD2[0x080B] Flow spec TPID action [this document]
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
7. Security Considerations 7. Security Considerations
For General BGP Flow-spec Security Considerations, see [RFC5575bis]. For General BGP Flow Specification Security Considerations, see
[RFC5575bis].
VLAN tagging identifies Layer 2 communities which are commonly VLAN tagging identifies Layer 2 communities which are commonly
expected to be isolated except when higher layer connection is expected to be isolated except when higher layer connection is
provided, such as Layer 3 routing. The ability of the Flow-spec VLAN provided, such as Layer 3 routing. Thus, the ability of the flowspec
action to change the VLAN ID in a frame may thus compromise security. VLAN action to change the VLAN ID in a frame might compromise
security.
8. Acknowledgements 8. Acknowledgements
The authors wish to acknowledge the important contributions and The authors wish to acknowledge the important contributions and
suggestions of the following: suggestions of the following:
Hannes Gredler, Xiaohu Xu, Zhenbin Li, Lucy Yong, and Feng Dong. Hannes Gredler, Xiaohu Xu, Zhenbin Li, Lucy Yong, and Feng Dong.
9. Contributors 9. Contributors
skipping to change at page 19, line 50 skipping to change at page 20, line 50
Mohapatra, P., draft-ietf-idr-bgp-flowspec-oid, work in Mohapatra, P., draft-ietf-idr-bgp-flowspec-oid, work in
progress. progress.
[FlowSpecV6] McPherson, D., Raszuk, R., Pithawala, B., [FlowSpecV6] McPherson, D., Raszuk, R., Pithawala, B.,
akarch@cisco.com, a., and S. Hares, "Dissemination of Flow akarch@cisco.com, a., and S. Hares, "Dissemination of Flow
Specification Rules for IPv6", draft-ietf-idr-flow-spec- Specification Rules for IPv6", draft-ietf-idr-flow-spec-
v6-10. Work in progress. v6-10. Work in progress.
[RFC5575bis] Hares, S., Loibl, C., Raszuk, R., McPherson, D., Bacher, [RFC5575bis] Hares, S., Loibl, C., Raszuk, R., McPherson, D., Bacher,
M., "Dissemination of Flow Specification Rules", draft- M., "Dissemination of Flow Specification Rules", draft-
ietf-idr-rfc5575bis-18, Work in progress. ietf-idr-rfc5575bis, Work in progress.
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
Informative References Informative References
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
2015, <https://www.rfc-editor.org/info/rfc7432>. 2015, <https://www.rfc-editor.org/info/rfc7432>.
skipping to change at page 22, line 9 skipping to change at page 23, line 9
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: zhuangshunwan@huawei.com Email: zhuangshunwan@huawei.com
INTERNET-DRAFT L2 Flow Spec INTERNET-DRAFT L2 Flow Spec
Copyright, Disclaimer, and Additional IPR Provisions Copyright, Disclaimer, and Additional IPR Provisions
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
 End of changes. 67 change blocks. 
161 lines changed or deleted 185 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/