draft-ietf-bess-mvpn-evpn-sr-p2mp-00.txt		draft-ietf-bess-mvpn-evpn-sr-p2mp-01.txt
	Network Working Group R. Parekh		Network Working Group R. Parekh
	Internet-Draft C. Filsfils		Internet-Draft C. Filsfils
	Intended status: Standards Track A. Venkateswaran		Intended status: Standards Track A. Venkateswaran
	Expires: May 22, 2021 Cisco Systems, Inc.		Expires: June 5, 2021 Cisco Systems, Inc.
	H. Bidgoli		H. Bidgoli
	Nokia		Nokia
	D. Voyer		D. Voyer
	Bell Canada		Bell Canada
	Z. Zhang		Z. Zhang
	Juniper Networks		Juniper Networks
	November 18, 2020		December 2, 2020
	Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint		Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint
	Trees		Trees
	draft-ietf-bess-mvpn-evpn-sr-p2mp-00		draft-ietf-bess-mvpn-evpn-sr-p2mp-01
	Abstract		Abstract
	A Point-to-Multipoint (P2MP) Tree in a Segment Routing domain		A Point-to-Multipoint (P2MP) Tree in a Segment Routing domain
	efficiently carries traffic from a Root to a set of Leaves. This		efficiently carries traffic from a Root to a set of Leaves. This
	document describes extensions to BGP encodings and procedures for		document describes extensions to BGP encodings and procedures for
	P2MP trees used in BGP/MPLS IP VPNs and Ethernet VPNs.		P2MP trees used in BGP/MPLS IP VPNs and Ethernet VPNs.
	Requirements Language		Requirements Language
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 22, 2021.		This Internet-Draft will expire on June 5, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 2, line 49 ¶		skipping to change at page 2, line 49 ¶
	4.4.2. Receiving Leaf A-D routes . . . . . . . . . . . . . . 9		4.4.2. Receiving Leaf A-D routes . . . . . . . . . . . . . . 9
	5. Dampening of MVPN routes . . . . . . . . . . . . . . . . . . 9		5. Dampening of MVPN routes . . . . . . . . . . . . . . . . . . 9
	6. SR P2MP Trees for EVPN . . . . . . . . . . . . . . . . . . . 10		6. SR P2MP Trees for EVPN . . . . . . . . . . . . . . . . . . . 10
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 11		8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11		10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	11.1. Normative References . . . . . . . . . . . . . . . . . . 12		11.1. Normative References . . . . . . . . . . . . . . . . . . 12
	11.2. Informative References . . . . . . . . . . . . . . . . . 12		11.2. Informative References . . . . . . . . . . . . . . . . . 12
	11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13		11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	Multicast in MPLS/BGP IP VPNs [RFC6513] and BGP Encodings and		Multicast in MPLS/BGP IP VPNs [RFC6513] and BGP Encodings and
	Procedures for Multicast in MPLS/BGP IP VPNs [RFC6514] specify		Procedures for Multicast in MPLS/BGP IP VPNs [RFC6514] specify
	procedures that allow a Service Provider to provide Multicast VPN		procedures that allow a Service Provider to provide Multicast VPN
	(MVPN) service to its customers. Multicast traffic from a customer		(MVPN) service to its customers. Multicast traffic from a customer
	is tunneled across the service provider network over Provider Tunnels		is tunneled across the service provider network over Provider Tunnels
	(P-Tunnels). P-tunnels can be instantiated via different		(P-Tunnels). P-tunnels can be instantiated via different
	skipping to change at page 11, line 7 ¶		skipping to change at page 11, line 7 ¶
	SRv6 header and deliver it over SRv6 P2MP trees to other NVEs.		SRv6 header and deliver it over SRv6 P2MP trees to other NVEs.
	The same procedures specified for MVPN are used to collect the leaf		The same procedures specified for MVPN are used to collect the leaf
	information of corresponding SR P2MP tree (either based on IMET route		information of corresponding SR P2MP tree (either based on IMET route
	or Leaf A-D routes in response to x-PMSI routes), to pass the tree		or Leaf A-D routes in response to x-PMSI routes), to pass the tree
	information to the PCE controller, and to get back tree forwarding		information to the PCE controller, and to get back tree forwarding
	state used for customer multicast traffic forwarding.		state used for customer multicast traffic forwarding.
	7. IANA Considerations		7. IANA Considerations
	IANA to assign a codepoint [[CREF2: TBD]] for "P2MP tree" in the		IANA is requested assign codepoint for "SR-MPLS P2MP Tree" in the
	"P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types"		"P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types"
	registry.		registry <https://www.iana.org/assignments/bgp-parameters/bgp-
			parameters.xhtml#pmsi-tunnel-types> [RFC 7538] in the "Border Gateway
			Protocol (BGP) Parameters" registry. A proposed value is 0x0C.
	8. Security Considerations		8. Security Considerations
	The procedures in this document do not introduce any additional		The procedures in this document do not introduce any additional
	security considerations beyond those mentioned in [RFC6513] and		security considerations beyond those mentioned in [RFC6513] and
	[RFC6514]. For general security considerations applicable to P2MP		[RFC6514]. For general security considerations applicable to P2MP
	trees, please refer to [I-D.ietf-pim-sr-p2mp-policy] .		trees, please refer to [I-D.ietf-pim-sr-p2mp-policy] .
	9. Acknowledgements		9. Acknowledgements
	skipping to change at page 13, line 8 ¶		skipping to change at page 13, line 14 ¶
	[I-D.ietf-bess-evpn-mvpn-seamless-interop]		[I-D.ietf-bess-evpn-mvpn-seamless-interop]
	Sajassi, A., Thiruvenkatasamy, K., Thoria, S., Gupta, A.,		Sajassi, A., Thiruvenkatasamy, K., Thoria, S., Gupta, A.,
	and L. Jalil, "Seamless Multicast Interoperability between		and L. Jalil, "Seamless Multicast Interoperability between
	EVPN and MVPN PEs", draft-ietf-bess-evpn-mvpn-seamless-		EVPN and MVPN PEs", draft-ietf-bess-evpn-mvpn-seamless-
	interop-01 (work in progress), July 2020.		interop-01 (work in progress), July 2020.
	[I-D.ietf-bess-mvpn-evpn-aggregation-label]		[I-D.ietf-bess-mvpn-evpn-aggregation-label]
	Zhang, Z., Rosen, E., Lin, W., Li, Z., and I. Wijnands,		Zhang, Z., Rosen, E., Lin, W., Li, Z., and I. Wijnands,
	"MVPN/EVPN Tunnel Aggregation with Common Labels", draft-		"MVPN/EVPN Tunnel Aggregation with Common Labels", draft-
	ietf-bess-mvpn-evpn-aggregation-label-03 (work in		ietf-bess-mvpn-evpn-aggregation-label-04 (work in
	progress), October 2019.		progress), November 2020.
	[I-D.ietf-spring-sr-replication-segment]		[I-D.ietf-spring-sr-replication-segment]
	Voyer, D., Filsfils, C., Parekh, R., Bidgoli, H., and Z.		Voyer, D., Filsfils, C., Parekh, R., Bidgoli, H., and Z.
	Zhang, "SR Replication Segment for Multi-point Service		Zhang, "SR Replication Segment for Multi-point Service
	Delivery", draft-ietf-spring-sr-replication-segment-03		Delivery", draft-ietf-spring-sr-replication-segment-03
	(work in progress), October 2020.		(work in progress), October 2020.
	[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.		[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
	Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",		Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
	RFC 6625, DOI 10.17487/RFC6625, May 2012,		RFC 6625, DOI 10.17487/RFC6625, May 2012,
End of changes. 8 change blocks.
	9 lines changed or deleted		11 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/