draft-ietf-bess-mvpn-evpn-aggregation-label-04.txt		draft-ietf-bess-mvpn-evpn-aggregation-label-05.txt
	BESS Z. Zhang		BESS Z. Zhang
	Internet-Draft E. Rosen		Internet-Draft Juniper Networks
	Updates: 7432, 6514, 7582 (if approved) W. Lin		Updates: 7432, 6514, 7582 (if approved) E. Rosen
	Intended status: Standards Track Juniper Networks		Intended status: Standards Track Individual
	Expires: May 19, 2021 Z. Li		Expires: July 15, 2021 W. Lin
			Juniper Networks
			Z. Li
	Huawei Technologies		Huawei Technologies
	I. Wijnands		I. Wijnands
	Cisco Systems		Individual
	November 15, 2020		January 11, 2021
	MVPN/EVPN Tunnel Aggregation with Common Labels		MVPN/EVPN Tunnel Aggregation with Common Labels
	draft-ietf-bess-mvpn-evpn-aggregation-label-04		draft-ietf-bess-mvpn-evpn-aggregation-label-05
	Abstract		Abstract
	The MVPN specifications allow a single Point-to-Multipoint (P2MP)		The MVPN specifications allow a single Point-to-Multipoint (P2MP)
	tunnel to carry traffic of multiple VPNs. The EVPN specifications		tunnel to carry traffic of multiple VPNs. The EVPN specifications
	allow a single P2MP tunnel to carry traffic of multiple Broadcast		allow a single P2MP tunnel to carry traffic of multiple Broadcast
	Domains (BDs). These features require the ingress router of the P2MP		Domains (BDs). These features require the ingress router of the P2MP
	tunnel to allocate an upstream-assigned MPLS label for each VPN or		tunnel to allocate an upstream-assigned MPLS label for each VPN or
	for each BD. A packet sent on a P2MP tunnel then carries the label		for each BD. A packet sent on a P2MP tunnel then carries the label
	that is mapped to its VPN or BD. (In some cases, a distinct		that is mapped to its VPN or BD. (In some cases, a distinct
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	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 May 19, 2021.		This Internet-Draft will expire on July 15, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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
	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 13, line 24 ¶		skipping to change at page 13, line 24 ¶
	7.2. Informative References		7.2. Informative References
	[I-D.ietf-bess-evpn-bum-procedure-updates]		[I-D.ietf-bess-evpn-bum-procedure-updates]
	Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A.		Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A.
	Sajassi, "Updates on EVPN BUM Procedures", draft-ietf-		Sajassi, "Updates on EVPN BUM Procedures", draft-ietf-
	bess-evpn-bum-procedure-updates-08 (work in progress),		bess-evpn-bum-procedure-updates-08 (work in progress),
	November 2019.		November 2019.
	[I-D.ietf-bier-evpn]		[I-D.ietf-bier-evpn]
	Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,		Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,
	"EVPN BUM Using BIER", draft-ietf-bier-evpn-03 (work in		"EVPN BUM Using BIER", draft-ietf-bier-evpn-04 (work in
	progress), April 2020.		progress), December 2020.
	[I-D.ietf-bier-mvpn]		[I-D.ietf-bier-mvpn]
	Rosen, E., Sivakumar, M., Aldrin, S., Dolganow, A., and T.		Rosen, E., Sivakumar, M., Aldrin, S., Dolganow, A., and T.
	Przygienda, "Multicast VPN Using BIER", draft-ietf-bier-		Przygienda, "Multicast VPN Using BIER", draft-ietf-bier-
	mvpn-11 (work in progress), March 2018.		mvpn-11 (work in progress), March 2018.
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,		Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
	Litkowski, S., and R. Shakir, "Segment Routing		Litkowski, S., and R. Shakir, "Segment Routing
	Architecture", draft-ietf-spring-segment-routing-15 (work		Architecture", draft-ietf-spring-segment-routing-15 (work
	skipping to change at page 14, line 5 ¶		skipping to change at page 14, line 5 ¶
	RFC 5331, DOI 10.17487/RFC5331, August 2008,		RFC 5331, DOI 10.17487/RFC5331, August 2008,
	<https://www.rfc-editor.org/info/rfc5331>.		<https://www.rfc-editor.org/info/rfc5331>.
	Authors' Addresses		Authors' Addresses
	Zhaohui Zhang		Zhaohui Zhang
	Juniper Networks		Juniper Networks
	EMail: zzhang@juniper.net		EMail: zzhang@juniper.net
	Eric Rosen		Eric Rosen
	Juniper Networks		Individual
	EMail: erosen@juniper.net		EMail: erosen52@gmail.com
	Wen Lin		Wen Lin
	Juniper Networks		Juniper Networks
	EMail: wlin@juniper.net		EMail: wlin@juniper.net
	Zhenbin Li		Zhenbin Li
	Huawei Technologies		Huawei Technologies
	EMail: lizhenbin@huawei.com		EMail: lizhenbin@huawei.com
	IJsbrand Wijnands		IJsbrand Wijnands
	Cisco Systems		Individual
	EMail: ice@cisco.com		EMail: ice@braindump.be
End of changes. 10 change blocks.
	14 lines changed or deleted		16 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/