draft-ietf-bess-evpn-prefix-advertisement-06.txt   draft-ietf-bess-evpn-prefix-advertisement-07.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet Draft W. Henderickx Internet Draft W. Henderickx
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
J. Drake J. Drake
W. Lin W. Lin
Juniper Juniper
A. Sajassi A. Sajassi
Cisco Cisco
Expires: April 19, 2018 October 16, 2017 Expires: April 22, 2018 October 19, 2017
IP Prefix Advertisement in EVPN IP Prefix Advertisement in EVPN
draft-ietf-bess-evpn-prefix-advertisement-06 draft-ietf-bess-evpn-prefix-advertisement-07
Abstract Abstract
EVPN provides a flexible control plane that allows intra-subnet EVPN provides a flexible control plane that allows intra-subnet
connectivity in an MPLS and/or NVO-based network. In some networks, connectivity in an MPLS and/or NVO-based network. In some networks,
there is also a need for a dynamic and efficient inter-subnet there is also a need for a dynamic and efficient inter-subnet
connectivity across Tenant Systems and End Devices that can be connectivity across Tenant Systems and End Devices that can be
physical or virtual and do not necessarily participate in dynamic physical or virtual and do not necessarily participate in dynamic
routing protocols. This document defines a new EVPN route type for routing protocols. This document defines a new EVPN route type for
the advertisement of IP Prefixes and explains some use-case examples the advertisement of IP Prefixes and explains some use-case examples
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 16, 2018. This Internet-Draft will expire on April 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 12, line 21 skipping to change at page 12, line 21
actual next-hop is given by the RT-5's BGP next-hop. actual next-hop is given by the RT-5's BGP next-hop.
+----------+----------+----------+------------+----------------+ +----------+----------+----------+------------+----------------+
| ESI | GW-IP | MAC* | Label | Overlay Index | | ESI | GW-IP | MAC* | Label | Overlay Index |
|--------------------------------------------------------------| |--------------------------------------------------------------|
| Non-Zero | Zero | Zero | Don't Care | ESI | | Non-Zero | Zero | Zero | Don't Care | ESI |
| Non-Zero | Zero | Non-Zero | Don't Care | ESI | | Non-Zero | Zero | Non-Zero | Don't Care | ESI |
| Zero | Non-Zero | Zero | Don't Care | GW-IP | | Zero | Non-Zero | Zero | Don't Care | GW-IP |
| Zero | Zero | Non-Zero | Zero | MAC | | Zero | Zero | Non-Zero | Zero | MAC |
| Zero | Zero | Non-Zero | Non-Zero | MAC or None** | | Zero | Zero | Non-Zero | Non-Zero | MAC or None** |
| Zero | Zero | Zero | Non-Zero | None(IP NVO)***| | Zero | Zero | Zero | Non-Zero | None*** |
+----------+----------+----------+------------+----------------+ +----------+----------+----------+------------+----------------+
Table 1 - RT-5 fields and Indicated Overlay Index Table 1 - RT-5 fields and Indicated Overlay Index
Table NOTES: Table NOTES:
* MAC with Zero value means no Router's MAC extended community is * MAC with Zero value means no Router's MAC extended community is
present along with the RT-5. Non-Zero indicates that the extended present along with the RT-5. Non-Zero indicates that the extended
community is present and carries a valid MAC address. Examples of community is present and carries a valid MAC address. Examples of
invalid MAC addresses are broadcast or multicast MAC addresses. invalid MAC addresses are broadcast or multicast MAC addresses.
The presence of the Router's MAC extended community alone is not
enough to indicate the use of the MAC address as the overlay
index, since the extended community can be used for other
purposes.
** In this case, the Overlay Index may be the RT-5's MAC address or ** In this case, the Overlay Index may be the RT-5's MAC address or
None, depending on the local policy of the receiving NVE/PE. None, depending on the local policy of the receiving NVE/PE.
*** The Overlay Index is None. This is a special case used for IP- *** The Overlay Index is None. This is a special case used for IP-
VRF-to-IP-VRF where the NVE/PEs are connected by IP NVO tunnels VRF-to-IP-VRF where the NVE/PEs are connected by IP NVO tunnels
as opposed to Ethernet NVO tunnels. as opposed to Ethernet NVO tunnels.
Table 2 shows the different inter-subnet use-cases described in this Table 2 shows the different inter-subnet use-cases described in this
document and the corresponding coding of the Overlay Index in the document and the corresponding coding of the Overlay Index in the
skipping to change at page 13, line 32 skipping to change at page 13, line 32
This section describes some use-cases for the Overlay Index types This section describes some use-cases for the Overlay Index types
used with the IP Prefix route. used with the IP Prefix route.
4.1 TS IP Address Overlay Index Use-Case 4.1 TS IP Address Overlay Index Use-Case
The following figure illustrates an example of inter-subnet The following figure illustrates an example of inter-subnet
forwarding for subnets sitting behind Virtual Appliances (on TS2 and forwarding for subnets sitting behind Virtual Appliances (on TS2 and
TS3). TS3).
SN1---+ NVE2 DGW1 IP4---+ NVE2 DGW1
| +-----------+ +---------+ +-------------+ | +-----------+ +---------+ +-------------+
SN2---TS2(VA)--| (BD-10) |-| |----| (BD-10) | SN2---TS2(VA)--| (BD-10) |-| |----| (BD-10) |
| IP2/M2 +-----------+ | | | IRB1\ | | IP2/M2 +-----------+ | | | IRB1\ |
IP4---+ | | | (IP-VRF)|---+ -+---+ | | | (IP-VRF)|---+
| | +-------------+ _|_ | | | +-------------+ _|_
| VXLAN/ | ( ) SN1 | VXLAN/ | ( )
| nvGRE | DGW2 ( WAN ) | | nvGRE | DGW2 ( WAN )
SN1---+ NVE3 | | +-------------+ (___) -+---+ NVE3 | | +-------------+ (___)
| IP3/M3 +-----------+ | |----| (BD-10) | | | IP3/M3 +-----------+ | |----| (BD-10) | |
SN3---TS3(VA)--| (BD-10) |-| | | IRB2\ | | SN3---TS3(VA)--| (BD-10) |-| | | IRB2\ | |
| +-----------+ +---------+ | (IP-VRF)|---+ | +-----------+ +---------+ | (IP-VRF)|---+
IP5---+ +-------------+ IP5---+ +-------------+
Figure 2 TS IP address use-case Figure 2 TS IP address use-case
An example of inter-subnet forwarding between subnet SN1/24 and a An example of inter-subnet forwarding between subnet SN1/24 and a
subnet sitting in the WAN is described below. NVE2, NVE3, DGW1 and subnet sitting in the WAN is described below. NVE2, NVE3, DGW1 and
DGW2 are running BGP EVPN. TS2 and TS3 do not participate in dynamic DGW2 are running BGP EVPN. TS2 and TS3 do not participate in dynamic
 End of changes. 7 change blocks. 
10 lines changed or deleted 14 lines changed or added

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