rfc9541v2.txt		rfc9541.txt
	Internet Engineering Task Force (IETF) J. Rabadan, Ed.		Internet Engineering Task Force (IETF) J. Rabadan, Ed.
	Request for Comments: 9541 S. Sathappan		Request for Comments: 9541 S. Sathappan
	Category: Standards Track K. Nagaraj		Category: Standards Track K. Nagaraj
	ISSN: 2070-1721 Nokia		ISSN: 2070-1721 Nokia
	M. Miyake		M. Miyake
	T. Matsuda		T. Matsuda
	Softbank		Softbank
	January 2024		February 2024
	Flush Mechanism for Customer MAC Addresses Based on Service Instance		Flush Mechanism for Customer MAC Addresses Based on Service Instance
	Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN)		Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN)
	Abstract		Abstract
	Provider Backbone Bridging (PBB) can be combined with Ethernet		Provider Backbone Bridging (PBB) can be combined with Ethernet
	Virtual Private Networks (EVPNs) to deploy Ethernet Local Area		Virtual Private Networks (EVPNs) to deploy Ethernet Local Area
	Network (E-LAN) services in large Multiprotocol Label Switching		Network (E-LAN) services in large Multiprotocol Label Switching
	(MPLS) networks. That combination is what we refer to as "PBB-EVPN."		(MPLS) networks. That combination is what we refer to as "PBB-EVPN."
	skipping to change at line 108 ¶		skipping to change at line 108 ¶
	devices or aggregation networks do not demand multihomed ESs from the		devices or aggregation networks do not demand multihomed ESs from the
	PBB-EVPN provider, but simply demand multiple single-homed ESs.		PBB-EVPN provider, but simply demand multiple single-homed ESs.
	Single-homed ESs use null ESIs, whereas multihomed ESs use non-null		Single-homed ESs use null ESIs, whereas multihomed ESs use non-null
	ESIs. If using single-homed ESs, the PBB-EVPN network is no longer		ESIs. If using single-homed ESs, the PBB-EVPN network is no longer
	aware of the redundancy offered by the access administrative entity.		aware of the redundancy offered by the access administrative entity.
	Figure 1 shows an example where the PBB-EVPN network provides four		Figure 1 shows an example where the PBB-EVPN network provides four
	different Attachment Circuits (ACs) for I-SID1, with those ACs not		different Attachment Circuits (ACs) for I-SID1, with those ACs not
	being part of any ES or virtual ES. (Therefore, they are referred to		being part of any ES or virtual ES. (Therefore, they are referred to
	as null virtual Ethernet Segments.)		as null virtual Ethernet Segments.)
	<----G.8032--><--PBB-EVPN Network---><----MPLS---->		<----G.8032----><--PBB-EVPN Network-----><----MPLS---->
	Access MPLS Access		Access MPLS Access
	Ring Network		Ring Network
	I-SID1 ESI +------+ +------+		I-SID1 ESI +------+ +------+
	+----+ null| PE1 |---------| PE3 |		+----+ null| PE1 |---------| PE3 |
	|CE1 |--------|B-MAC1| |B-MAC3| ESI null		|CE1 |----------|B-MAC1| |B-MAC3| ESI null
	+----+ active| | | |----+ PW		+----+ active| | | |----+ PW
	| +------+ +------+ \active		| +------+ +------+ \active
	| | | \ +----+		| | | \ +----+
	| | | ==|CE3 |I-SID1		| | | ==|CE3 |I-SID1
	| | | / +----+		| | | / +----+
	|stb ESI +------+ +------+ / PW		|standby ESI +------+ +------+ / PW
	+----+ null| PE2 | | PE4 |----+ standby		+----+ null| PE2 | | PE4 |----+ standby
	|CE2 |--------|B-MAC2| |B-MAC4| ESI null		|CE2 |----------|B-MAC2| |B-MAC4| ESI null
	+----+ active| |---------| |		+----+ active| |---------| |
	I-SID1 +------+ +------+		I-SID1 +------+ +------+
	Figure 1: PBB-EVPN and Non-ES-Based Redundancy		Figure 1: PBB-EVPN and Non-ES-Based Redundancy
	In the example in Figure 1, CE1, CE2, and CE3 are attached to the		In the example in Figure 1, CE1, CE2, and CE3 are attached to the
	same service, identified by I-SID1, in the PBB-EVPN PEs. CE1 and CE2		same service, identified by I-SID1, in the PBB-EVPN PEs. CE1 and CE2
	are connected to the PEs via "Ethernet ring protection switching" as		are connected to the PEs via "Ethernet ring protection switching" as
	specified in [G.8032], and their ACs to PE1 and PE2 are represented		specified in [G.8032], and their ACs to PE1 and PE2 are represented
	by a port and VLAN identifier. CE3 is dual-homed to PE3 and PE4		by a port and VLAN identifier. CE3 is dual-homed to PE3 and PE4
	through an active/standby PW, and its AC to the PEs is represented by		through an active/standby PW, and its AC to the PEs is represented by
	a PW. Each of the four PEs uses a dedicated Backbone MAC address as		a PW. Each of the four PEs uses a dedicated Backbone MAC address as
End of changes. 2 change blocks.
	17 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.48.