Per multicast flow Designated Forwarder Election for EVPN
draft-ietf-bess-evpn-per-mcast-flow-df-election-00
BESS WorkGroup Ali. Sajassi
Internet-Draft Mankamana. Mishra
Intended status: Standards Track Samir. Thoria
Expires: March 8, 2019 Cisco Systems
Jorge. Rabadan
Nokia
John. Drake
Juniper Networks
September 4, 2018
Per multicast flow Designated Forwarder Election for EVPN
draft-ietf-bess-evpn-per-mcast-flow-df-election-00
Abstract
[RFC7432] describes mechanism to elect designated forwarder (DF) at
the granularity of (ESI, EVI) which is per VLAN (or per group of
VLANs in case of VLAN bundle or VLAN-aware bundle service). However,
the current level of granularity of per-VLAN is not adequate for some
applications.[I-D.ietf-bess-evpn-df-election-framework] improves base
line DF election by introducing HRW DF election.
[I-D.ietf-bess-evpn-igmp-mld-proxy] introduces applicability of EVPN
to Multicast flows, routes to sync them and a default DF election.
This document is an extension to HRW base draft
[I-D.ietf-bess-evpn-df-election-framework] and further enhances HRW
algorithm for the Multicast flows to do DF election at the
granularity of (ESI, VLAN, Mcast flow).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on March 8, 2019.
Sajassi, et al. Expires March 8, 2019 [Page 1]
Internet-DraftPer multicast flow Designated Forwarder ElecSeptember 2018
Copyright Notice
Copyright (c) 2018 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
(https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The DF Election Extended Community . . . . . . . . . . . . . 4
4. HRW base per multicast flow EVPN DF election . . . . . . . . 6
4.1. DF election for IGMP (S,G) membership request . . . . . . 6
4.2. DF election for IGMP (*,G) membership request . . . . . . 7
4.3. Default DF election procedure . . . . . . . . . . . . . . 7
5. Procedure to use per multicast flow DF election algorithm . . 8
6. Triggers for DF re-election . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10
10. Normative References . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
EVPN based All-Active multi-homing is becoming the basic building
block for providing redundancy in next generation data center
deployments as well as service provider access/aggregation networks.
[RFC7432] defines the role of a designated forwarder as the node in
the redundancy group that is responsible to forward Broadcast,
Unknown unicast, Multicast (BUM) traffic on that Ethernet Segment (CE
device or network) in All-Active multi-homing.
The default DF election mechanism allows selecting a DF at the
granularity of (ES, VLAN) or (ES, VLAN bundle) for BUM traffic.
While [I-D.ietf-bess-evpn-df-election-framework] improve on the
default DF election procedure, some service provider residential
applications require a finer granularity, where whole multicast flows
Show full document text