INTERNET-DRAFT W. Hao
Intended Status: Proposed Standard Huawei Technologies
D. Eastlake
Futurewei Technologies
J. Uttaro
AT&T
S. Litkowski
Orange Business Service
Cisco Systems
S. Zhuang
Huawei Technologies" Technologies
Expires: January 7, May 2, 2020 July 8, November 3, 2019
BGP Dissemination of L2VPN Flow Specification Rules
draft-ietf-idr-flowspec-l2vpn-11
draft-ietf-idr-flowspec-l2vpn-12
Abstract
This document defines a BGP flow-spec Border Gateway Protocol (BGP) Flow-spec
extension to disseminate L2 VPN Layer 2 Virtual Private Network (L2VPN)
Ethernet traffic filtering rules. AFI=25 SAFI=134 in draft-ietf-idr-
rfc5575bis is redefined used for this
purpose. A new subset of New component types and extended community also are defined. A new subset of
component types and new an extended community also are
defined.
Status of This Document
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Distribution of this document is unlimited. Comments should be sent
to the authors or the TRILL IDR Working Group mailing list
<dnsext@ietf.org>. <idr@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
INTERNET-DRAFT L2VPN Flow Spec
Table of Contents
1. Introduction............................................3
1.1 Terminology............................................4
2. Layer 2 Flow Specification encoding Encoding in BGP..............5
3. Ethernet L2VPN Flow Specification encoding Encoding in BGP.............6 BGP................6
3.1 Order of Traffic Filtering Rules.......................8
4. Ethernet Flow Specification Traffic Actions.............9 Actions............10
4.1 VLAN-action............................................9 VLAN-action...........................................10
4.2 TPID-action...........................................11 TPID-action...........................................12
5. IANA Considerations....................................12 Flow Spec Validation...................................13
6. Security Considerations................................13 IANA Considerations....................................14
7. Acknowledgements.......................................13 Security Considerations................................15
8. Contributors...........................................13 Acknowledgements.......................................15
9. Contributors...........................................15
Normative References......................................14 References......................................16
Informative References....................................14 References....................................16
Authors' Addresses........................................15 Addresses........................................17
INTERNET-DRAFT L2VPN Flow Spec
1. Introduction
BGP
Border Gateway Protocol (BGP) Flow-spec [RFC5575bis] is an extension
to BGP that supports the dissemination of traffic flow specification rules.
rules and actions to be taken on packets in a specified flow. It
leverages the BGP Control Plane to simplify the distribution of ACLs. ACLs
(Access Control Lists). Using this the Flow-spec 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
(Distributed Denial of Service) mitigation, access control, etc.
BGP Flow-spec [RFC5575bis] 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 IPv4 BGP/MPLS VPN
filtering. The Flow specification match part defined in [RFC5575bis]
only includes L3/L4 information like IPv4 source/destination prefix,
protocol, ports, and etc., the like, so traffic flows can only be
selectively filtered
based on L3/L4 information. This has been extended by [FlowSpecV6] to
cover IPv6.
Layer 2 Virtual Private Networks (L2VPNs) have already been deployed in an
increasing number of networks. Such networks today. In an L2VPN network, we also have requirements
to deploy BGP Flow-spec to mitigate DDoS attack traffic. Within an
L2VPN network, both IP and non-IP Ethernet traffic maybe exist. For
IP traffic filtering, the Flow specification rules defined in
[RFC5575bis] and/or [FlowSpecV6], which include match criteria and actions
actions, can still be used, flow used. Flow specification rules received via the
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 need to be considered. But the flow
specification match criteria defined in [RFC5575bis] only include
layer 3 and layer 4 IP information, not layer 2 Ethernet information.
There are different kinds of L2VPN networks like EVPN [RFC7432], BGP
VPLS [RFC4761], LDP VPLS [RFC4762] and border gateway protocol (BGP)
auto discovery [RFC6074]. Because the flow-spec Flow-spec feature relies on
the BGP protocol to distribute traffic filtering rules, 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 [RFC4761], EVPN and LDP-based VPLS [RFC4762] with
BGP auto-discovery [RFC6074].
This draft proposes a defines new subset of flow-spec Flow-spec component types and an two new extended community
communities to support L2VPN flow-spec Flow-spec application. The flow-
spec Flow-spec
rules can be enforced on all border routers or on some interface sets
of the border routers. SAFI=134 in [RFC5575bis] and [FlowSpecV6] is redefined
extended for dissemination of AFI=25 as specified in Section 2 to cover traffic
filtering information in an L2VPN environment.
INTERNET-DRAFT L2VPN Flow Spec
1.1 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The following acronyms are used in this document:
ACL - Access Control List
DDOS - Distributed Denial of Service
EVPN - Ethernet VPN [RFC7432]
L2VPN - Layer 2 VPN
L3VPN - Layer 3 VPN
PCP - Priority Code Point [802.1Q]
TPID - Tag Protocol ID, typically a VLAN ID
VLAN = Virtual Local Area Network
VPLS - Virtual Private Line Service [RFC4762]
VPN - Virtual Private Network
INTERNET-DRAFT L2VPN Flow Spec
2. Layer 2 Flow Specification encoding Encoding in BGP
[RFC5575bis] defines SAFI 133 and SAFI 134 134, with AFI=1, for
"dissemination of IPv4 flow specification rules" and "dissemination
of VPNv4 flow specification rules" rules", respectively. [I-D.ietf-idr-flow-spec-v6]
redefines the [FlowSpecV6]]
extends [RFC5575bis] SAFIs in order to make them also allow AFI=2 thus making it applicable to
both IPv4 and IPv6 applications. This document will further redefine extends the SAFI 134 in order to
SAFI=134 for AFI=25 and make them it applicable to L2VPN applications.
The following changes are defined: change is specified:
"SAFI 134 for dissemination of L3VPN flow specification rules" to now
be in
[FlowSpecV6] is defined as "SAFI 134 for dissemination of VPN flow specification
rules"
For SAFI 134 the indication to which address family it is referring
to will be recognized by AFI value (AFI=1 for VPNv4, AFI=2 VPNv6 and
AFI=25 for L2VPN). Such modification is fully backwards compatible
with existing implementation and production deployments.
For SAFI 134 the indication to which VPN flow
specification rules"
The address family it is referring to will be recognized which SAFI 134 refers is indicate by the AFI
value (AFI=1 for VPNv4, AFI=2 VPNv6 and AFI=25 for L2VPN). Such modification
extension is fully backwards compatible with existing implementation
and production deployments.
INTERNET-DRAFT L2VPN Flow Spec
3. Ethernet L2VPN Flow Specification encoding Encoding in BGP
The NLRI format for this address family AFI=25/SAFI=134, as with the other VPN Flow-spec
AFI/SAFI pairs, consists of an overall length encoded as provided in
Section 4.1 of [RFC5575bis], then a fixed-length Route Distinguisher
field (8 bytes) followed by octets), then a flow specification,
following specification [RFC5575bis] [FlowSpecV6]
that may include the encoding component types defined in this document. The NLRI
length field includes both the 8 bytes octets of the Route Distinguisher as
well as the subsequent flow specification.
+------------------------------+
| length (0xnn or 0xfn nn) |
+------------------------------+
| Route Distinguisher (8 bytes)|
+------------------------------+
| NLRI value (variable) |
+------------------------------+
Flow specification rules received via this NLRI apply only to traffic
that belongs to the VPN instance(s) into which it is imported. Flow
rules are accepted by default when received from remote PE routers. as specified in Section 5.
Besides the component types defined in [RFC5575bis] and
[I-D.ietf-idr-flow-spec-v6], [FlowSpecV6],
this document specifies the following additional component types for
L2 VPN Ethernet traffic filtering:
Type 14 tbdA - Ethernet Type (EtherType)
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match two-octet
field. op is encoded as specified in Section 4.2.3 of
[RFC5575bis]. Values are encoded as 2-byte 2-octet quantities. Ethernet
II framing defines the two-octet Ethernet Type (EtherType) field
in an Ethernet frame, preceded by destination and source MAC
addresses, that identifies an upper layer protocol encapsulating
the frame data.
Type 15 tbdB - Source MAC
Encoding: <type (1 octet), MAC Address length (1 octet), MAC Address>
Defines the source MAC Address to match.
Type 16 tbdC - Destination MAC
Encoding: <type (1 octet), MAC Address length (1 octet), MAC Address>
Defines the destination MAC Address to match.
Type 17 tbdD - DSAP(Destination DSAP (Destination Service Access Point) in LLC
Encoding: <type (1 octet), length (1 octet), [op, value]+>
INTERNET-DRAFT L2VPN Flow Spec
Defines a list of {operation, value} pairs used to match the
1-octet DSAP in the 802.2 LLC (Logical Link Control Header).
Values are encoded as 1-byte 1-octet quantities. The operation field op is encoded as a
specified in Section 4.2.3 of [RFC5575bis].
Type 18 tbdE - SSAP(Source SSAP (Source Service Access Point) in LLC
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match the
1-octet SSAP in the 802.2 LLC. Values are encoded as 1-byte 1-octet
quantities.
INTERNET-DRAFT L2VPN Flow Spec op is encoded as specified in Section 4.2.3 of
[RFC5575bis].
Type 19 tbdF - Control field in LLC
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 1-octet
control field in the 802.2 LLC. Values are encoded as 1-byte 1-octet
quantities. op is encoded as specified in Section 4.2.3 of
[RFC5575bis].
Type 20 tbdG - SNAP
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 5-octet
SNAP (Sub-Network Access Protocol) field. Values are encoded as
5-byte
5-octet quantities. op is encoded as specified in Section 4.2.3 of
[RFC5575bis].
Type 21 tbdH - VLAN ID
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match VLAN ID.
Values are encoded as 2-byte 2-octet quantities, where the four most
significant bits are zero and the 12 least significant bits
contain the VLAN value. op is encoded as specified in Section
4.2.3 of [RFC5575bis].
In the virtual local-area network (VLAN) stacking case, the VLAN
ID is the outer VLAN ID.
Type 22 tbdI - VLAN COS PCP
Encoding: <type (1 octet), length (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 3-bit
VLAN COS PCP fields [802.1Q]. Values are encoded using a single byte,
octet, where the five most significant bits are zero and the three
least significant bits contain the VLAN COS PCP value. op is encoded
as specified in Section 4.2.3 of [RFC5575bis].
INTERNET-DRAFT L2VPN Flow Spec
In the virtual local-area network (VLAN) stacking case, the VLAN
COS
PCP is outer VLAN COS. PCP.
Type 23 tbdJ - Inner VLAN ID
Encoding: <type (1 octet), length (1 octet), [op, value]+>
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 Q use. Values are encoded as 2-byte 2-octet quantities, where the
four most significant bits are zero and the 12 least significant
bits contain the VLAN value. op is encoded as specified in Section
4.2.3 of [RFC5575bis].
In single VLAN case, this component type MUST NOT be used. If it
appears the match will fail.
Type 24 tbdK - Inner VLAN COS PCP
Encoding: <type (1 octet), length (1 octet), [op, value]+>
INTERNET-DRAFT L2VPN Flow Spec
Defines a list of {operation, value} pairs used to match 3-bit
inner VLAN COS PCP fields [802.1Q] using for virtual local-area
network (VLAN) stacking or Q in Q use. Values are encoded using a
single byte, octet, where the five most significant bits are zero and
the three least significant bits contain the VLAN COS PCP value. op is
encoded as specified in Section 4.2.3 of [RFC5575bis].
In single VLAN case, the component type MUST NOT be used. If it
appears the match will fail.
Type tbdL - VLAN DEI
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
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.
Type tbdM - Inner VLAN DEI
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 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.
3.1 Order of Traffic Filtering Rules
The original definition for the order of traffic filtering rules can
be reused with new consideration for the MAC Address offset. As long
as the offsets are equal, the comparison is the same, retaining
INTERNET-DRAFT L2VPN Flow Spec
longest-prefix-match semantics. If the offsets are not equal, the
lowest offset has precedence, as this flow matches the most
significant bit.
Pseudocode:
flow_rule_L2_cmp (a, b)
{
comp1 = next_component(a);
comp2 = next_component(b);
while (comp1 || comp2) {
// component_type returns infinity on end-of-list
if (component_type(comp1) < component_type(comp2)) {
return A_HAS_PRECEDENCE;
}
if (component_type(comp1) > component_type(comp2)) {
return B_HAS_PRECEDENCE;
}
if (component_type(comp1) == MAC_DESTINATION || MAC_SOURCE) {
common = MIN(MAC Address length (comp1),
MAC Address length (comp2));
cmp = MAC Address compare(comp1, comp2, common);
// not equal, lowest value has precedence
// equal, longest match has precedence
} else {
common =
MIN(component_length(comp1), component_length(comp2));
cmp = memcmp(data(comp1), data(comp2), common);
// not equal, lowest value has precedence
// equal, longest string has precedence
}
}
return EQUAL;
}
INTERNET-DRAFT L2VPN Flow Spec
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 [RFC5575bis] can be used to
specify particular actions in an L2 VPN network:
+--------+--------------------+--------------------------+
+--------+--------------------+----------------------------+
| type | extended community | encoding |
+--------+--------------------+--------------------------+
+--------+--------------------+----------------------------+
| 0x8006 | traffic-rate | 2-byte 2-octet as#, 4-byte 4-octet float |
| 0x8007 | traffic-action | bitmask |
| 0x8008 | redirect | 6-byte 6-octet Route Target |
| 0x8009 | traffic-marking | DSCP value |
+--------+--------------------+--------------------------+
+--------+--------------------+----------------------------+
Redirect: The action should be redefined to allow the traffic to be
redirected to a MAC or IP VRF routing instance that lists the
specified route-target in its import policy.
Besides the above extended communities, this document also specifies
the following BGP extended communities for Ethernet flows to extend
[RFC5575bis]:
+--------+------------------------+--------------------------+
| type | extended community | encoding |
+--------+------------------------+--------------------------+
| TBD1 | VLAN-action | bitmask |
| TBD2 | TPID-action | bitmask |
+--------+------------------------+--------------------------+
4.1 VLAN-action
The VLAN-action extended community, as shown in the diagram below,
consists of 6 bytes octets that include t action Flags, two VLAN IDs, and
the associating COS value. associated PCP and DEI values. The action Flags fields are
further divided into two parts which correspond to the first action
and the second action respectively. Bit 0 to bit 7 give the first
action while bit 8 to bit 15 give the second action. The bits of PO,
PU, SW, RI and RO in each part represent the action of Pop, Push,
Swap, Rewrite inner VLAN and Rewrite outer VLAN respectively.
Through this method, more complicated actions also can be represented
in a single VLAN-action extended community, such as SwapPop,
PushSwap, etc. For example, SwapPop action is the sequence of two
actions, the first action is Swap and the second action is Pop.
INTERNET-DRAFT L2VPN Flow Spec
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 |
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| VLAN ID1 |COS1 |R1 | |PCP1 |DE1|
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| VLAN ID2 |COS2 |R2 | |PCP2 |DE2|
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
PO1: Pop action. If the PO1 flag is one, it indicates the outmost
VLAN should be removed.
PU1: Push action. If PU1 is one, it indicates VLAN ID1 will be
added, the associated COS is COS1. PCP and DEI are PCP1 and DE1.
SW1: Swap action. If the SW1 flag is one, it indicates the outer
VLAN and inner VLAN should be swapped.
PO2: Pop action. If the PO2 flag is one, it indicates the outmost
VLAN should be removed.
PU2: Push action. If PU2 is one, it indicates VLAN ID2 will be
added, the associated COS is COS2. PCP and DEI are PCP2 and DE2.
SW2: Swap action. If the SW2 flag is one, it indicates the outer
VLAN and inner VLAN should be swapped.
RI1 and RI2: Rewrite inner VLAN action. If the RI flag is one, it
indicates the inner VLAN should be replaced by a new VLAN where the
new VLAN is VLAN ID1 and the associated COS is COS1. PCP and DEO are PCP1 and DE1.
If the VLAN ID1 is 0, the action is to only modify the COS PCP and DEI
value of the inner VLAN.
RO1 and RO2: Rewrite outer VLAN action. If the RO flag is one, it
indicates the outer VLAN should be replaced by a new VLAN where the
new VLAN is VLAN ID and the associated COS is COS2. PCP and DEI are PCP2 and DE2.
If the VLAN ID2 is 0, the action is to only modify the COS PCP and DEI
value of the outer VLAN.
Resv, R1, and R2: Reserved for future use. MUST be sent as zero and
ignored on receipt.
Giving an example below: if the action of PUSH Inner VLAN 10 with COS PCP
value 5 DEI value 0 and Outer VLAN 20 with COS PCP value 6 DEI value 0 is
needed, the format of the VLAN-action extended community is as
follows:
INTERNET-DRAFT L2VPN Flow Spec
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 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 10 |1 |0 |1 |0 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 20 |1 |1 |0 |0 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
4.2 TPID-action
The TPID-action extended community consists of 6 bytes octets which
includes the fields of action Flags, TPID1 and TPID2.
0 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|TI|TO| Resv |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TP ID1 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TP ID2 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
TI: Mapping inner TP ID action. If the TI flag is one, it indicates
the inner TP ID should be replaced by a new TP ID, the new TP ID is
TP ID1.
TO: Mapping outer TP ID action. If the TO flag is one, it indicates
the outer TP ID should be replaced by a new TP ID, the new TP ID is
TP ID2.
Resv: Reserved for future use. MUST be sent as zero and ignored on
receipt.
INTERNET-DRAFT L2VPN Flow Spec
5. Flow Spec Validation
Flow-specs received over AFI=25/SAFI=134 are validated against
routing reachability received over AFI=25/SAFI=128 as modified to
conform to [FlowSpecOID].
INTERNET-DRAFT L2VPN Flow Spec
6. IANA Considerations
IANA is requested to change the description for SAFI 134 [RFC5575bis]
to read as follows more general description and to change the reference for it to [this
document]:
134 VPN dissemination of flow specification rules
IANA is requested to allocate 11 new values in the Flow-Spec
Component Type registry as follows:
+--------+-------------------------------+--------------------------+
+--------+--------------------------+--------------------------+
| type | RFC or Draft Reference | description | discription
+--------+--------------------------+--------------------------+
|
+--------+-------------------------------+--------------------------+ tbdA | 14 |This draft [this document] | Ethernet Type |
| 15 |This draft tbdB | [this document] | Source MAC |
| 16 |This draft tbdC | [this document] | Destination MAC |
| 17 |This draft tbdD | [this document] | DSAP in LLC |
| 18 |This draft tbdE | [this document] | SSAP in LLC |
| 19 |This draft tbdF | [this document] | Control field in LLC |
| 20 |This draft tbdG | [this document] | SNAP |
| 21 |This draft tbdH | [this document] | VLAN ID |
| 22 |This draft tbdI | [this document] | VLAN COS PCP |
| 23 |This draft tbdJ | [this document] | Inner VLAN ID |
| 24 |This draft tbdK | [this document] | Inner VLAN PCP |
| tbdL | [this document] | VLAN DEI |
| tbdM | [this document] | Inner VLAN COS DEI |
+--------+-------------------------------+--------------------------+
+--------+--------------------------+--------------------------+
IANA is requested to update the reference for the following
assignment in assign two values from the "BGP Extended
Communities Type - extended, transitive" registry: registry [suggested value
provided in square brackets]:
Type value Name Reference
---------- ---------------------------
------------ ------------------------ ---------------
0x080A
TBD1[0x080A] Flow spec VLAN action [this document]
0x080B
TBD2[0x080B] Flow spec TPID action [this document]
INTERNET-DRAFT L2VPN Flow Spec
6.
7. Security Considerations
No new security issues
For General BGP Flow-spec Security Considerations, see [RFC5575bis].
VLAN tagging identifies Layer 2 communities which are introduced commonly
expected to be isolated except when higher layer connection is
provided, such as Layer 3 routing. The ability of the Flow-spec VLAN
action to change the BGP protocol by this
specification.
7. VLAN ID in a frame thus may compromise security.
8. Acknowledgements
The authors wish to acknowledge the important contributions of the
following:
Hannes Gredler, Xiaohu Xu, Zhenbin Li, Lucy Yong, and Feng Dong.
8.
9. Contributors
Qiandeng Liang
Huawei Technologies
101 Software Avenue, Yuhuatai District
Nanjing 210012
China
Email: liangqiandeng@huawei.com
INTERNET-DRAFT L2VPN Flow Spec
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.
[RFC5575bis] Hares, S., Loibl, C., Raszuk, R., McPherson, D., Bacher,
M., "Dissemination of Flow Specification Rules", draft-
ietf-idr-rfc5575bis-17, Work in progress, June 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>.
[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,
<https://www.rfc-editor.org/info/rfc4761>.
[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,
<https://www.rfc-editor.org/info/rfc4762>.
[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, <https://www.rfc-
editor.org/info/rfc6074>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119
Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May
2017, <https://www.rfc-editor.org/info/rfc8174>.
[FlowSpecOID] Uttaro, J., Alcaide, J., Filsfils, C.. Smith, D.,
Mohapatra, P., draft-ietf-idr-bgp-flowspec-oid, work in
progress.
[FlowSpecV6] 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.
[RFC5575bis] Hares, S., Loibl, C., Raszuk, R., McPherson, D., Bacher,
M., "Dissemination of Flow Specification Rules", draft-
ietf-idr-rfc5575bis-17, Work in progress, June 2019.
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, <https://www.rfc-editor.org/info/rfc7432>.
INTERNET-DRAFT L2VPN Flow Spec
Authors' Addresses
Weiguo Hao
Huawei Technologies
101 Software Avenue,
Nanjing 210012
China
Email: haoweiguo@huawei.com
Donald E. Eastlake, 3rd
Futurewei Technologies
1424 Pro Shop Court
Davenport,
2386 Panoramic Circle
Apopka, FL 33896 32703
USA
Tel: +1-508-333-2270
Email: d3e3e3@gmail.com
James Uttaro
AT&T
Email: uttaro@att.com
Stephane Litkowski
Orange Business Service
Cisco Systems, Inc.
Email: stephane.litkowski@orange.com slitkows.ietf@gmail.com
Shunwan Zhuang
Huawei Technologies
Huawei Bld., No.156 Beiqing Rd.
Beijing 100095
China
Email: zhuangshunwan@huawei.com
INTERNET-DRAFT L2VPN Flow Spec
Copyright, Disclaimer, and Additional IPR Provisions
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
(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.