draft-ietf-idr-flowspec-nvo3-03.txt   draft-ietf-idr-flowspec-nvo3-04.txt 
INTERNET-DRAFT Donald Eastlake INTERNET-DRAFT D. Eastlake
Intended Status: Proposed Standard Weiguo Hao Intended Status: Proposed Standard W. Hao
Shunwan Zhuang S. Zhuang
Zhenbin Li Z. Li
Huawei Technologies Huawei Technologies
Rong Gu R. Gu
China Mobil China Mobil
Expires: March 10, 2019 September 11, 2018 Expires: September 3, 2019 March 4, 2019
BGP Dissemination of BGP Dissemination of
Network Virtualization Overlays (NVO3) Flow Specification Rules Network Virtualization Overlays (NVO3) Flow Specification Rules
<draft-ietf-idr-flowspec-nvo3-03.txt> <draft-ietf-idr-flowspec-nvo3-04.txt>
Abstract Abstract
This draft specifies a new subset of component types to support the This draft specifies a new subset of component types to support the
(Network Virtualization Overlays (NVO3)) flow-spec application. (Network Virtualization Overlays (NVO3)) flow-spec application.
Status of This Document Status of This Document
This Internet-Draft is submitted to IETF 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 TRILL Working Group mailing list to the authors or the TRILL Working Group mailing list
<dnsext@ietf.org>. <dnsext@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 4, line 36 skipping to change at page 4, line 36
Figure 1. NVO3 Data Center Interconnection Figure 1. NVO3 Data Center Interconnection
The MPLS L2/L3 VPN in the WAN network can be used for NVO3 based data The MPLS L2/L3 VPN in the WAN network can be used for NVO3 based data
center network interconnection. When the Data Center (DC) and the WAN center network interconnection. When the Data Center (DC) and the WAN
are operated by the same administrative entity, the Service Provider are operated by the same administrative entity, the Service Provider
can decide to integrate the gateway (GW) and WAN Edge PE functions in can decide to integrate the gateway (GW) and WAN Edge PE functions in
the same router for capital and operational cost saving reasons. This the same router for capital and operational cost saving reasons. This
is illustrated in Figure 1. There are two interconnection solutions is illustrated in Figure 1. There are two interconnection solutions
as follows: as follows:
1. End-to-end NVO3 tunnel across different data centers: NVE1 perform 1. End-to-end NVO3 tunnel across different data centers: NVE1
NVO3 encapsulation for DC interconnection with NVE3, the performs NVO3 encapsulation for DC interconnection with NVE3. The
destination VTEP IP is NVE3's IP. The GW doesn't perform NVO3 destination VTEP IP is NVE3's IP. The GW doesn't perform NVO3
tunnel termination. The DC interconnect WAN is pure an underlay tunnel termination. The DC interconnect WAN is pure an underlay
network. network.
2. Segmented NVO3 tunnels across different data centers: NVE1 doesn't 2. Segmented NVO3 tunnels across different data centers: NVE1 doesn't
perform end-to-end NVO3 encapsulation to NVE3 for DC perform end-to-end NVO3 encapsulation to NVE3 for DC
interconnection. The GW performs NVO3 tunnel encapsulation interconnection. The GW performs NVO3 tunnel encapsulation
termination, and then transmits the inner original traffic through termination, and then transmits the inner original traffic through
MPLS network to the peer data center GW. The peer data center GW an MPLS network to the peer data center GW. The peer data center
again terminates MPLS encapsulation, and then performs NVO3 GW again terminates MPLS encapsulation, and then performs NVO3
encapsulation to transmit the traffic to the local NVE3. encapsulation to transmit the traffic to the local NVE3.
In the first solution, to differentiate bandwidth and Quality of In the first solution, to differentiate bandwidth and Quality of
Service (QoS) among different tenants or applications, different TE Service (QoS) among different tenants or applications, different TE
tunnels in the WAN network will be used to carry the end-to-end NVO3 tunnels in the WAN network will be used to carry the end-to-end NVO3
encapsulation traffic using VN ID, NVO3 outer header DSCP, and other encapsulation traffic using VN ID, NVO3 outer header DSCP, and other
fields as the traffic classification match part. The BGP Flow-spec fields as the traffic classification match part. The BGP Flow-spec
protocol can be used to set the traffic classification on all GWs protocol can be used to set the traffic classification on all GWs
simultaneously. simultaneously.
INTERNET-DRAFT NVO3 BGP Flow-Spec INTERNET-DRAFT NVO3 BGP Flow-Spec
In the second solution, a centralized BGP speaker can be deployed for In the second solution, a centralized BGP speaker can be deployed for
DDOS mitigation in the WAN network. When the analyzer detects DDOS mitigation in the WAN network. When the analyzer detects
abnormal traffic, it will automatically generate Flow-spec rules and abnormal traffic, it will automatically generate Flow-spec rules and
distribute them to each GW through BGP Flow-spec protocol, the match distribute them to each GW through the BGP Flow-spec protocol, the
part should include matching on inner or outer L2/L3 layer or NVO3 match part should include matching on inner or outer L2/L3 layer or
headers. NVO3 headers.
In summary, the Flow specification match part on the GW/PE should be In summary, the Flow specification match part on the GW/PE should be
able to include inner layer 2 Ethernet header, inner layer 3 IP able to include inner layer 2 Ethernet header, inner layer 3 IP
header, outer layer 2 Ethernet header, outer layer 3 IP header, header, outer layer 2 Ethernet header, outer layer 3 IP header,
and/or NVO3 header information. Because the current flow-spec and/or NVO3 header information. Because the current flow-spec
matching facilities lack a layer indicator and NVO3 header matching facilities lack a layer indicator and NVO3 header
information, those facilities can't be used directly for traffic information, those facilities can't be used directly for traffic
filtering based on NVO3 headers or on a specified layer header filtering based on NVO3 headers or on a specified layer header
directly. This draft specifies a new subset of component types to directly. This draft specifies a new subset of component types to
support the NVO3 flow-spec application. support the NVO3 flow-spec application.
skipping to change at page 5, line 40 skipping to change at page 5, line 40
capitals, as shown here. capitals, as shown here.
The reader is assumed to be familiar with BGP and NVO3 terminology. The reader is assumed to be familiar with BGP and NVO3 terminology.
The following terms and acronyms are used in this document with the The following terms and acronyms are used in this document with the
meaning indicated: meaning indicated:
ACL - Access Control List ACL - Access Control List
DC - Data Center DC - Data Center
DDOS - Distributed Denial of Service (Attack). DDOS - Distributed Denial of Service (Attack)
GW - gateway GW - gateway
VN - virtual network VN - virtual network
VTEP - Virtual Tunnel End Point VTEP - Virtual Tunnel End Point
WAN - wide area network WAN - wide area network
INTERNET-DRAFT NVO3 BGP Flow-Spec INTERNET-DRAFT NVO3 BGP Flow-Spec
skipping to change at page 6, line 29 skipping to change at page 6, line 29
Because the NVO3 outer layer address normally belongs to a public Because the NVO3 outer layer address normally belongs to a public
network, the "Flow Specification" NLRI for the outer layer header network, the "Flow Specification" NLRI for the outer layer header
doesn't need to include a Route Distinguisher field (8 bytes). If the doesn't need to include a Route Distinguisher field (8 bytes). If the
outer layer address belongs to a VPN, the NLRI format for the outer outer layer address belongs to a VPN, the NLRI format for the outer
header should consist of a fixed-length Route Distinguisher field (8 header should consist of a fixed-length Route Distinguisher field (8
bytes) corresponding to the VPN. This Route Distinguisher is followed bytes) corresponding to the VPN. This Route Distinguisher is followed
by the detail flow specifications for the outer layer. by the detail flow specifications for the outer layer.
The VN ID is the identification for each tenant network. The "Flow The VN ID is the identification for each tenant network. The "Flow
Specification" NLRI for an NVO3 header part should always include the Specification" NLRI for an NVO3 header part should always include the
VN ID field but a Route Distinguisher field doesn't need to be VN ID field but a Route Distinguisher field does not need to be
included. included.
The inner layer MAC/IP address is always associated with a VN ID. The inner layer MAC/IP address is always associated with a VN ID.
Thus the NLRI format for the inner header should consist of a fixed- Thus the NLRI format for the inner header should consist of a fixed-
length VN ID field (4 bytes). The VN ID is followed by the detailed length VN ID field (4 bytes). The VN ID is followed by the detailed
flow specifications for the inner layer. The NLRI length field shall flow specifications for the inner layer. The NLRI length field shall
include both the 4 bytes of the VN ID as well as the subsequent flow include both the 4 bytes of the VN ID as well as the subsequent flow
specification. In the NVO3 terminating into a VPN scenario, if specification. In the NVO3 terminating into a VPN scenario, if
multiple access VN IDs map to one VPN instance, one shared VN ID can multiple access VN IDs map to one VPN instance, one shared VN ID can
be carried in the Flow-Spec rule to enforce the rule on the entire be carried in the Flow-Spec rule to enforce the rule on the entire
skipping to change at page 7, line 26 skipping to change at page 7, line 26
- VXLAN: Tunnel Type = 0 - VXLAN: Tunnel Type = 0
- NVGRE: Tunnel Type = 1 - NVGRE: Tunnel Type = 1
I: If I is set to one, it indicates the component types for the I: If I is set to one, it indicates the component types for the
inner layer of NVO3 headers immediately follow. inner layer of NVO3 headers immediately follow.
O: If O is set to one, it indicates the component types for the O: If O is set to one, it indicates the component types for the
outer layer of NVO3 headers immediately follow. outer layer of NVO3 headers immediately follow.
For NVO3 header part, the following additional component types are For the NVO3 header part, the following additional component types are
introduced. introduced.
Type TBD2 - VN ID Type TBD2 - VN ID
Encoding: <type (1 octet), [op, value]+>. Encoding: <type (1 octet), [op, value]+>.
Defines a list of {operation, value} pairs used to match the Defines a list of {operation, value} pairs used to match the
24-bit VN ID that is used as the tenant identification in NVO3 24-bit VN ID that is used as the tenant identification in NVO3
networks. For NVGRE encapsulation, the VN ID is equivalent to networks. For NVGRE encapsulation, the VN ID is equivalent to
VSID. Values are encoded as 1- to 3-byte quantities. VSID. Values are encoded as 1- to 3-byte quantities.
skipping to change at page 11, line 9 skipping to change at page 11, line 9
Rong Gu Rong Gu
China Mobile China Mobile
Email: gurong_cmcc@outlook.com Email: gurong_cmcc@outlook.com
INTERNET-DRAFT NVO3 BGP Flow-Spec INTERNET-DRAFT NVO3 BGP Flow-Spec
Copyright, Disclaimer, and Additional IPR Provisions Copyright, Disclaimer, and Additional IPR Provisions
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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. 12 change blocks. 
19 lines changed or deleted 19 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/