draft-ietf-bess-evpn-ac-df-02.txt   draft-ietf-bess-evpn-ac-df-03.txt 
BESS Workgroup J. Rabadan BESS Workgroup J. Rabadan, Ed.
Internet Draft K. Nagaraj Internet Draft K. Nagaraj
S. Sathappan S. Sathappan
Intended status: Informational V. Prabhu Intended status: Informational V. Prabhu
W. Henderickx
Nokia Nokia
A. Liu A. Liu
Ericsson Ciena
W. Lin W. Lin
Juniper Networks Juniper Networks
Expires: April 14, 2018 October 11, 2017 Expires: July 22, 2018 January 18, 2018
AC-Influenced Designated Forwarder Election for EVPN AC-Influenced Designated Forwarder Election for EVPN
draft-ietf-bess-evpn-ac-df-02 draft-ietf-bess-evpn-ac-df-03
Abstract Abstract
The Designated Forwarder (DF) in EVPN networks is the PE responsible The Designated Forwarder (DF) in EVPN networks is the PE responsible
for sending multicast, broadcast and unknown unicast traffic to a for sending multicast, broadcast and unknown unicast traffic to a
multi-homed CE, on a given Ethernet Tag on a particular Ethernet multi-homed CE, on a given Ethernet Tag on a particular Ethernet
Segment (ES). The DF is selected based on the list of PEs that Segment (ES). The DF is selected based on the list of PEs that
advertise the Ethernet Segment Identifier (ESI) to the EVPN network. advertise the Ethernet Segment Identifier (ESI) to the EVPN network.
While PE node or link failures trigger the DF re-election for a given While PE node or link failures trigger the DF re-election for a given
<ESI, EVI>, individual Attachment Circuit (AC) or MAC-VRF failures do <ESI, EVI>, individual Attachment Circuit (AC) or MAC-VRF failures do
skipping to change at page 2, line 14 skipping to change at page 2, line 13
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 14, 2018. This Internet-Draft will expire on July 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. 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
skipping to change at page 2, line 40 skipping to change at page 2, line 39
Table of Contents Table of Contents
1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3 1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3
2. Solution Description . . . . . . . . . . . . . . . . . . . . . 4 2. Solution Description . . . . . . . . . . . . . . . . . . . . . 4
2.1. Current DF Election Procedure And AC Failures . . . . . . . 5 2.1. Current DF Election Procedure And AC Failures . . . . . . . 5
2.2. The Attachment Circuit (AC) Influenced DF Election . . . . 6 2.2. The Attachment Circuit (AC) Influenced DF Election . . . . 6
2.3. AC-Influenced DF Election For VLAN-Aware Bundle Services . 7 2.3. AC-Influenced DF Election For VLAN-Aware Bundle Services . 7
3. Solution benefits . . . . . . . . . . . . . . . . . . . . . . . 8 3. Solution benefits . . . . . . . . . . . . . . . . . . . . . . . 8
4. Conventions used in this document . . . . . . . . . . . . . . . 8 4. Conventions used in this document . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Problem Statement 1. Problem Statement
[RFC7432] defines the Designated Forwarder (DF) as the EVPN PE [RFC7432] defines the Designated Forwarder (DF) as the EVPN PE
responsible for: responsible for:
o Flooding Broadcast, Unknown unicast and Multicast traffic (BUM), on o Flooding Broadcast, Unknown unicast and Multicast traffic (BUM), on
a given Ethernet Tag on a particular Ethernet Segment (ES), to the a given Ethernet Tag on a particular Ethernet Segment (ES), to the
CE. This is valid for single-active and all-active EVPN CE. This is valid for single-active and all-active EVPN
multi-homing. multi-homing.
skipping to change at page 5, line 40 skipping to change at page 5, line 40
Figure 1 EVPN network example Figure 1 EVPN network example
2.1. Current DF Election Procedure And AC Failures 2.1. Current DF Election Procedure And AC Failures
After running the service-carving DF election algorithm, PE-2 turns After running the service-carving DF election algorithm, PE-2 turns
out to be the DF for ESI12 and ESI23 in EVI-1. The following two out to be the DF for ESI12 and ESI23 in EVI-1. The following two
examples illustrate the issues with the existing defined procedure in examples illustrate the issues with the existing defined procedure in
[RFC7432]: [RFC7432]:
a) If AC2 is accidentally shutdown or even not configured, CE12 a) If AC2 is accidentally shutdown or even not configured, CE12
traffic will be impacted. In case of all-active multi-homing, only traffic will be impacted. In case of all-active multi-homing, the BUM
the BUM traffic to CE12 will be impacted, whereas for single-active traffic to CE12 will be "black-holed", whereas for single-active
multi-homing all the traffic to/from CE12 will be discarded. This is multi-homing all the traffic to/from CE12 will be discarded. This is
due to the fact that a logical failure in PE-2 AC2 may not trigger an due to the fact that a logical failure in PE-2 AC2 may not trigger an
ES route withdrawn for ESI12 (since there are still other ACs active ES route withdrawn for ESI12 (since there are still other ACs active
on ESI12) and therefore PE-1 will not re-run the DF election on ESI12) and therefore PE-1 will not re-run the DF election
procedures. procedures.
b) If EVI-1 is administratively shutdown or even not configured yet b) If EVI-1 is administratively shutdown or even not configured yet
on PE-2, CE12 and CE23 will both be impacted: BUM traffic to both CEs on PE-2, CE12 and CE23 will both be impacted: BUM traffic to both CEs
will be discarded in case of all-active multi-homing and all traffic will be discarded in case of all-active multi-homing and all traffic
will be discarded to/from the CEs in case of single-active will be discarded to/from the CEs in case of single-active
skipping to change at page 7, line 38 skipping to change at page 7, line 38
This procedure is backwards compatible with the DF election This procedure is backwards compatible with the DF election
procedures described in [RFC7432] since it does not add any new procedures described in [RFC7432] since it does not add any new
extension in the control plane, however, a PE not supporting the extension in the control plane, however, a PE not supporting the
procedures in this document SHOULD NOT share a multi-homed ES with a procedures in this document SHOULD NOT share a multi-homed ES with a
PE following this solution since both PEs may end up with an PE following this solution since both PEs may end up with an
inconsistent view on who the DF is. The AC influenced DF election inconsistent view on who the DF is. The AC influenced DF election
procedures SHOULD be enabled by an administrative option and only procedures SHOULD be enabled by an administrative option and only
used when all the PEs in the ES support it. used when all the PEs in the ES support it.
The procedure discussed in this section is applicable to the DF
Election in EVPN Services [RFC7432] and EVPN Virtual Private Wire
Services [RFC8214].
2.3. AC-Influenced DF Election For VLAN-Aware Bundle Services 2.3. AC-Influenced DF Election For VLAN-Aware Bundle Services
The procedure described section 2.2 works for VLAN-based and VLAN- The procedure described section 2.2 works for VLAN-based and VLAN-
bundle service interfaces since, for those service types, a PE bundle service interfaces since, for those service types, a PE
advertises only one Ethernet A-D per EVI route per <ESI,EVI>. The advertises only one Ethernet A-D per EVI route per <ESI,EVI>. The
withdrawal of such route means that the PE cannot forward traffic on withdrawal of such route means that the PE cannot forward traffic on
that particular <ESI,EVI>. that particular <ESI,EVI>.
In VLAN-aware bundle services, the PE advertises multiple Ethernet A- In VLAN-aware bundle services, the PE advertises multiple Ethernet A-
D per EVI routes per <ESI,EVI> (one route per Ethernet Tag). The D per EVI routes per <ESI,EVI> (one route per Ethernet Tag). The
skipping to change at page 9, line 4 skipping to change at page 9, line 11
indicates a compliance requirement statement using the key words indicates a compliance requirement statement using the key words
listed above. This convention aids reviewers in quickly identifying listed above. This convention aids reviewers in quickly identifying
or finding the explicit compliance requirements of this RFC. or finding the explicit compliance requirements of this RFC.
5. Security Considerations 5. Security Considerations
The same Security Considerations described in [RFC7432] are valid for The same Security Considerations described in [RFC7432] are valid for
this document. this document.
6. IANA Considerations 6. IANA Considerations
There are no new IANA considerations in this document. There are no new IANA considerations in this document.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
R., Patel, K., and J. Guichard, "Constrained Route Distribution for
Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
Internet Protocol (IP) Virtual Private Networks (VPNs)", RFC 4684,
DOI 10.17487/RFC4684, November 2006, <http://www.rfc-
editor.org/info/rfc4684>.
[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 Ethernet Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet
VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc- VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc-
editor.org/info/rfc7432>. editor.org/info/rfc7432>.
[RFC8214] Boutros, S., Sajassi, A., Salam, S., Drake, J., Rabadan,
J., "Virtual Private Wire Service Support in Ethernet VPN", RFC 8214,
DOI 10.17487/RFC8214, August 2017, <http://www.rfc-
editor.org/info/rfc8214>.
7.2. Informative References 7.2. Informative References
[VPLS-MH] Kothari, Henderickx et al., "BGP based Multi-homing in [VPLS-MH] Kothari, Henderickx et al., "BGP based Multi-homing in
Virtual Private LAN Service", draft-ietf-bess-vpls-multihoming- Virtual Private LAN Service", draft-ietf-bess-vpls-multihoming-
01.txt, work in progress, January, 2016. 01.txt, work in progress, January, 2016.
8. Acknowledgments 8. Acknowledgments
Will be added. The authors want to thank Sriram Venkateswaran, Laxmi Padakanti,
Ranganathan Boovaraghavan and Ali Sajassi for their review and
contributions.
9. Contributors
In addition to the authors listed on the front page, the following
coauthors have also contributed to this document:
Wim Henderickx
Nokia
Email: wim.henderickx@nokia.com
Patrice Brissette
Cisco Systems
Email: pbrisset@cisco.com
Authors' Addresses Authors' Addresses
Jorge Rabadan Jorge Rabadan
Nokia Nokia
777 E. Middlefield Road 777 E. Middlefield Road
Mountain View, CA 94043 USA Mountain View, CA 94043 USA
Email: jorge.rabadan@nokia.com Email: jorge.rabadan@nokia.com
Kiran Nagaraj Kiran Nagaraj
skipping to change at page 10, line 4 skipping to change at page 10, line 23
Mountain View, CA 94043 USA Mountain View, CA 94043 USA
Email: jorge.rabadan@nokia.com Email: jorge.rabadan@nokia.com
Kiran Nagaraj Kiran Nagaraj
Nokia Nokia
Email: kiran.nagaraj@nokia.com Email: kiran.nagaraj@nokia.com
Senthil Sathappan Senthil Sathappan
Nokia Nokia
Email: senthil.sathappan@nokia.com Email: senthil.sathappan@nokia.com
Vinod Prabhu Vinod Prabhu
Nokia Nokia
Email: vinod.prabhu@nokia.com Email: vinod.prabhu@nokia.com
Wim Henderickx
Nokia
Email: wim.henderickx@nokia.com
Autumn Liu Autumn Liu
Ericsson Ciena
Email: autumn.liu@ericsson.com Email: hliu@ciena.com
Wen Lin Wen Lin
Juniper Networks, Inc. Juniper Networks, Inc.
Email: wlin@juniper.net Email: wlin@juniper.net
 End of changes. 18 change blocks. 
26 lines changed or deleted 40 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/