< draft-ietf-bess-evpn-igmp-mld-proxy-20.txt		draft-ietf-bess-evpn-igmp-mld-proxy-21.txt >
	BESS WorkGroup A. Sajassi		BESS WorkGroup A. Sajassi
	Internet-Draft S. Thoria		Internet-Draft S. Thoria
	Intended status: Standards Track M. Mishra		Intended status: Standards Track M. Mishra
	Expires: September 22, 2022 Cisco Systems		Expires: September 23, 2022 Cisco Systems
	K. Patel		K. Patel
	Arrcus		Arrcus
	J. Drake		J. Drake
	W. Lin		W. Lin
	Juniper Networks		Juniper Networks
	March 21, 2022		March 22, 2022
	IGMP and MLD Proxy for EVPN		IGMP and MLD Proxy for EVPN
	draft-ietf-bess-evpn-igmp-mld-proxy-20		draft-ietf-bess-evpn-igmp-mld-proxy-21
	Abstract		Abstract
	This document describes how to support efficiently endpoints running		This document describes how to support efficiently endpoints running
	IGMP(Internet Group Management Protocol) or MLD (Multicast Listener		IGMP(Internet Group Management Protocol) or MLD (Multicast Listener
	Discovery) for the multicast services over an EVPN network by		Discovery) for the multicast services over an EVPN network by
	incorporating IGMP/MLD proxy procedures on EVPN (Ethernet VPN) PEs.		incorporating IGMP/MLD proxy procedures on EVPN (Ethernet VPN) PEs.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	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."
	This Internet-Draft will expire on September 22, 2022.		This Internet-Draft will expire on September 23, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2022 IETF Trust and the persons identified as the		Copyright (c) 2022 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 3, line 9 ¶		skipping to change at page 3, line 9 ¶
	9.3.1. Constructing the Multicast Leave Synch Route . . . . 26		9.3.1. Constructing the Multicast Leave Synch Route . . . . 26
	9.3.2. Reconstructing IGMP / MLD Leave from Multicast Leave		9.3.2. Reconstructing IGMP / MLD Leave from Multicast Leave
	Sync Route . . . . . . . . . . . . . . . . . . . . . 27		Sync Route . . . . . . . . . . . . . . . . . . . . . 27
	9.4. Multicast Flags Extended Community . . . . . . . . . . . 28		9.4. Multicast Flags Extended Community . . . . . . . . . . . 28
	9.5. EVI-RT Extended Community . . . . . . . . . . . . . . . . 29		9.5. EVI-RT Extended Community . . . . . . . . . . . . . . . . 29
	9.6. Rewriting of RT ECs and EVI-RT ECs by ASBRs . . . . . . . 31		9.6. Rewriting of RT ECs and EVI-RT ECs by ASBRs . . . . . . . 31
	9.7. BGP Error Handling . . . . . . . . . . . . . . . . . . . 32		9.7. BGP Error Handling . . . . . . . . . . . . . . . . . . . 32
	10. IGMP Version 1 Membership Report . . . . . . . . . . . . . . 32		10. IGMP Version 1 Membership Report . . . . . . . . . . . . . . 32
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 32		11. Security Considerations . . . . . . . . . . . . . . . . . . . 32
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
			12.1. EVPN Extended Community Sub-Types Registrations . . . . 32
			12.2. EVPN Route Type Registration . . . . . . . . . . . . . . 33
			12.3. Multicast Flags Extended Community Registry . . . . . . 33
	13. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 33		13. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 33
	14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 33		14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 34
	15. References . . . . . . . . . . . . . . . . . . . . . . . . . 34		15. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
	15.1. Normative References . . . . . . . . . . . . . . . . . . 34		15.1. Normative References . . . . . . . . . . . . . . . . . . 34
	15.2. Informative References . . . . . . . . . . . . . . . . . 35		15.2. Informative References . . . . . . . . . . . . . . . . . 35
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
	1. Introduction		1. Introduction
	In DC applications, a point of delivery (POD) can consist of a		In DC applications, a point of delivery (POD) can consist of a
	collection of servers supported by several top of rack (ToR) and		collection of servers supported by several top of rack (ToR) and
	spine switches. This collection of servers and switches are self		spine switches. This collection of servers and switches are self
	skipping to change at page 4, line 38 ¶		skipping to change at page 4, line 42 ¶
	o All-Active Redundancy Mode: When all PEs attached to an Ethernet		o All-Active Redundancy Mode: When all PEs attached to an Ethernet
	segment are allowed to forward known unicast traffic to/from that		segment are allowed to forward known unicast traffic to/from that
	Ethernet segment for a given VLAN, then the Ethernet segment is		Ethernet segment for a given VLAN, then the Ethernet segment is
	defined to be operating in All-Active redundancy mode.		defined to be operating in All-Active redundancy mode.
	o BD: Broadcast Domain. As per [RFC7432], an EVI consists of a		o BD: Broadcast Domain. As per [RFC7432], an EVI consists of a
	single or multiple BDs. In case of VLAN-bundle and VLAN-aware		single or multiple BDs. In case of VLAN-bundle and VLAN-aware
	bundle service model, an EVI contains multiple BDs. Also, in this		bundle service model, an EVI contains multiple BDs. Also, in this
	document, BD and subnet are equivalent terms.		document, BD and subnet are equivalent terms.
			o DC: Data Center
	o Ethernet Segment (ES): When a customer site (device or network) is		o Ethernet Segment (ES): When a customer site (device or network) is
	connected to one or more PEs via a set of Ethernet links.		connected to one or more PEs via a set of Ethernet links.
	o Ethernet Segment Identifier (ESI): A unique non-zero identifier		o Ethernet Segment Identifier (ESI): A unique non-zero identifier
	that identifies an Ethernet Segment.		that identifies an Ethernet Segment.
	o Ethernet Tag: It identifies a particular broadcast domain, e.g., a		o Ethernet Tag: It identifies a particular broadcast domain, e.g., a
	VLAN. An EVPN instance consists of one or more broadcast domains.		VLAN. An EVPN instance consists of one or more broadcast domains.
	o EVI: An EVPN instance spanning the Provider Edge (PE) devices		o EVI: An EVPN instance spanning the Provider Edge (PE) devices
	skipping to change at page 5, line 4 ¶		skipping to change at page 5, line 9 ¶
	o Ethernet Segment Identifier (ESI): A unique non-zero identifier		o Ethernet Segment Identifier (ESI): A unique non-zero identifier
	that identifies an Ethernet Segment.		that identifies an Ethernet Segment.
	o Ethernet Tag: It identifies a particular broadcast domain, e.g., a		o Ethernet Tag: It identifies a particular broadcast domain, e.g., a
	VLAN. An EVPN instance consists of one or more broadcast domains.		VLAN. An EVPN instance consists of one or more broadcast domains.
	o EVI: An EVPN instance spanning the Provider Edge (PE) devices		o EVI: An EVPN instance spanning the Provider Edge (PE) devices
	participating in that EVPN		participating in that EVPN
	o EVPN: Ethernet Virtual Private Network		o EVPN: Ethernet Virtual Private Network
	o IGMP: Internet Group Management Protocol		o IGMP: Internet Group Management Protocol
	o IR: Ingress Replication		o IR: Ingress Replication
	o MAC-VRF: A Virtual Routing and Forwarding table for Media Access
	Control (MAC) addresses on a PE
	o MLD: Multicast Listener Discovery		o MLD: Multicast Listener Discovery
	o OIF: Outgoing Interface for multicast. It can be physical		o OIF: Outgoing Interface for multicast. It can be physical
	interface, virtual interface or tunnel.		interface, virtual interface or tunnel.
	o PE: Provider Edge.		o PE: Provider Edge.
	o PMSI: P-Multicast Service Interface - a conceptual interface for a
	PE to send customer multicast traffic to all or some PEs in the
	same VPN.
	o POD: Point of Delivery		o POD: Point of Delivery
	o S-PMSI: Selective PMSI - to some of the PEs in the same VPN.		o S-PMSI: Selective P-Multicast Service Interface - a conceptual
			interface for a PE to send customer multicast traffic to some of
			the PEs in the same VPN.
	o Single-Active Redundancy Mode: When only a single PE, among all		o Single-Active Redundancy Mode: When only a single PE, among all
	the PEs attached to an Ethernet segment, is allowed to forward		the PEs attached to an Ethernet segment, is allowed to forward
	traffic to/from that Ethernet segment for a given VLAN, then the		traffic to/from that Ethernet segment for a given VLAN, then the
	Ethernet segment is defined to be operating in Single-Active		Ethernet segment is defined to be operating in Single-Active
	redundancy mode.		redundancy mode.
	o ToR: Top of Rack
	o DC: Data Center
	o SMET: Selective Multicast Ethernet Tag		o SMET: Selective Multicast Ethernet Tag
			o ToR: Top of Rack
	This document also assumes familiarity with the terminology of		This document also assumes familiarity with the terminology of
	[RFC7432], [RFC3376], [RFC2236] . Though most of the place this		[RFC7432], [RFC3376], [RFC2236] . Though most of the place this
	document uses term IGMP Membership Report, the text applies equally		document uses term IGMP Membership Report, the text applies equally
	for MLD Membership Report too. Similarly, text for IGMPv2 applies to		for MLD Membership Report too. Similarly, text for IGMPv2 applies to
	MLDv1 and text for IGMPv3 applies to MLDv2. IGMP / MLD version		MLDv1 and text for IGMPv3 applies to MLDv2. IGMP / MLD version
	encoding in BGP update is stated in Section 9		encoding in BGP update is stated in Section 9
	It is important to note when there is text considering whether a PE		It is important to note when there is text considering whether a PE
	indicates support for IGMP proxying, the corresponding behavior has a		indicates support for IGMP proxying, the corresponding behavior has a
	natural analogue for indication of support for MLD proxying, and the		natural analogue for indication of support for MLD proxying, and the
	skipping to change at page 32, line 44 ¶		skipping to change at page 32, line 44 ¶
	on a subnet constructed across multiple PODs or DCs via an EVPN		on a subnet constructed across multiple PODs or DCs via an EVPN
	solution. The security considerations for the operation of the		solution. The security considerations for the operation of the
	underlying EVPN and BGP substrate are described in [RFC7432], and		underlying EVPN and BGP substrate are described in [RFC7432], and
	specific multicast considerations are outlined in [RFC6513] and		specific multicast considerations are outlined in [RFC6513] and
	[RFC6514]. The EVPN and associated IGMP proxy provides a single		[RFC6514]. The EVPN and associated IGMP proxy provides a single
	broadcast domain so the same security considerations of IGMPv2		broadcast domain so the same security considerations of IGMPv2
	[RFC2236], [RFC3376], MLD [RFC2710], or MLDv2 [RFC3810] apply.		[RFC2236], [RFC3376], MLD [RFC2710], or MLDv2 [RFC3810] apply.
	12. IANA Considerations		12. IANA Considerations
			12.1. EVPN Extended Community Sub-Types Registrations
	IANA has allocated the following codepoints from the EVPN Extended		IANA has allocated the following codepoints from the EVPN Extended
	Community Sub-Types sub-registry of the BGP Extended Communities		Community Sub-Types sub-registry of the BGP Extended Communities
	registry.		registry.
	0x09 Multicast Flags Extended Community [this document]		0x09 Multicast Flags Extended Community [this document]
	0x0A EVI-RT Type 0 [this document]		0x0A EVI-RT Type 0 [this document]
	0x0B EVI-RT Type 1 [this document]		0x0B EVI-RT Type 1 [this document]
	0x0C EVI-RT Type 2 [this document]		0x0C EVI-RT Type 2 [this document]
	IANA is requested to allocate a new codepoint from the EVPN Extended		IANA is requested to allocate a new codepoint from the EVPN Extended
	Community sub-types registry for the following.		Community sub-types registry for the following.
	0x0D EVI-RT Type 3 [this document]		0x0D EVI-RT Type 3 [this document]
			12.2. EVPN Route Type Registration
	IANA has allocated the following EVPN route types from the EVPN Route		IANA has allocated the following EVPN route types from the EVPN Route
	Type registry.		Type registry.
	6 - Selective Multicast Ethernet Tag Route		6 - Selective Multicast Ethernet Tag Route
	7 - Multicast Membership Report Synch Route		7 - Multicast Membership Report Synch Route
	8 - Multicast Leave Synch Route		8 - Multicast Leave Synch Route
			12.3. Multicast Flags Extended Community Registry
	The Multicast Flags Extended Community contains a 16-bit Flags field.		The Multicast Flags Extended Community contains a 16-bit Flags field.
	The bits are numbered 0-15, from high-order to low-order.		The bits are numbered 0-15, from high-order to low-order.
	The registry should be initialized as follows:		The registry should be initialized as follows:
	Bit Name Reference Change Controller		Bit Name Reference Change Controller
	---- -------------- ------------- ------------------		---- -------------- ------------- ------------------
	0 - 13 Unassigned		0 - 13 Unassigned
	14 MLD Proxy Support This document. IETF		14 MLD Proxy Support This document. IETF
	15 IGMP Proxy Support This document IETF		15 IGMP Proxy Support This document IETF
	The registration policy should be "First Come First Served".		The registration policy should be "First Come First Served".
	13. Acknowledgement		13. Acknowledgement
End of changes. 17 change blocks.
	17 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/