< draft-xie-bier-mvpn-segmented-05.txt		draft-xie-bier-mvpn-segmented-06.txt >
	skipping to change at page 1, line 14 ¶		skipping to change at page 1, line 14 ¶
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track L. Geng		Intended status: Standards Track L. Geng
	Expires: April 25, 2019 L. Wang		Expires: April 25, 2019 L. Wang
	China Mobile		China Mobile
	M. McBride		M. McBride
	G. Yan		G. Yan
	Huawei		Huawei
	October 22, 2018		October 22, 2018
	Segmented MVPN Using IP Lookup for BIER		Segmented MVPN Using IP Lookup for BIER
	draft-xie-bier-mvpn-segmented-05		draft-xie-bier-mvpn-segmented-06
	Abstract		Abstract
	This document specifies an alternative of the control plane and data		This document specifies an alternative of the control plane and data
	plane procedures that allow segmented MVPN using the more efficient		plane procedures that allow segmented MVPN using the more efficient
	LIR-pF explicit-tracking when BIER is used as the upstream or		LIR-pF explicit-tracking when BIER is used as the upstream or
	downstream or both segments. It requires a segmentation point BFR		downstream or both segments. It requires a segmentation point BFR
	doing an IP header lookup, which is common for the forwarding		doing an IP header lookup, which is common for the forwarding
	procedure on BFER, or the forwarding procedure on ABR with local VPN		procedure on BFER, or the forwarding procedure on ABR with local VPN
	CEs connected. This document updates [I-D.ietf-bier-mvpn].		CEs connected. This document updates [I-D.ietf-bier-mvpn].
	skipping to change at page 2, line 24 ¶		skipping to change at page 2, line 24 ¶
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Problem Statement and Considerations . . . . . . . . . . . . 5		3. Problem Statement and Considerations . . . . . . . . . . . . 4
	3.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 5		3.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 4
	3.2. Considerations . . . . . . . . . . . . . . . . . . . . . 5		3.2. Considerations . . . . . . . . . . . . . . . . . . . . . 5
	4. Upstream BIER and Downstream BIER (BIER-BIER) . . . . . . . . 6		4. Upstream BIER and Downstream BIER (BIER-BIER) . . . . . . . . 6
	4.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 6		4.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 6
	4.2. Forwarding using IP lookup on Segmentation Point . . . . 8		4.2. Forwarding using IP lookup on Segmentation Point . . . . 8
	5. Upstream P2MP and Downstream BIER (P2MP-BIER) . . . . . . . . 9		5. Upstream P2MP and Downstream BIER (P2MP-BIER) . . . . . . . . 9
	5.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 9		5.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 9
	5.2. Forwarding using IP lookup on Segmentation Point . . . . 10		5.2. Forwarding using IP lookup on Segmentation Point . . . . 10
	6. Upstream BIER and Downstream P2MP (BIER-P2MP) . . . . . . . . 11		6. Upstream BIER and Downstream P2MP (BIER-P2MP) . . . . . . . . 10
	6.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 11		6.1. Explicit Tracking using LIR-pF . . . . . . . . . . . . . 10
	6.2. Forwarding on Segmentation Point . . . . . . . . . . . . 12		6.2. Forwarding on Segmentation Point . . . . . . . . . . . . 11
	7. Summary and Recommendations . . . . . . . . . . . . . . . . . 12		7. Summary and Recommendations . . . . . . . . . . . . . . . . . 12
	8. Appendix A - Comparison of Solutions . . . . . . . . . . . . 13		8. Appendix A - Comparison of Solutions . . . . . . . . . . . . 13
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 15		9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
	12.1. Normative References . . . . . . . . . . . . . . . . . . 16		12.1. Normative References . . . . . . . . . . . . . . . . . . 16
	12.2. Informative References . . . . . . . . . . . . . . . . . 16		12.2. Informative References . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	skipping to change at page 4, line 30 ¶		skipping to change at page 4, line 30 ¶
	Another example of such forwarding state is to use the upstream BIER		Another example of such forwarding state is to use the upstream BIER
	tunnel bound to an SPMSI route, and the downstream P2MP tunnel(s)		tunnel bound to an SPMSI route, and the downstream P2MP tunnel(s)
	and/or BIER tunnel(s).		and/or BIER tunnel(s).
	VRF: Virtual Routing Forwarding. It is usually a number to indicate		VRF: Virtual Routing Forwarding. It is usually a number to indicate
	a VPN/MVPN instance locally when L3VPN is configured. It is also		a VPN/MVPN instance locally when L3VPN is configured. It is also
	called local VRF.		called local VRF.
	Pseudo VRF: a Pseudo VRF indicates a VPN/MVPN instance locally on the		Pseudo VRF: a Pseudo VRF indicates a VPN/MVPN instance locally on the
	segment point ABR when downstream BIER forwarding using IP lookup is		segment point ABR when downstream BIER forwarding using IP lookup is
	required. The segment point ABR can be PE of a VPN/MVPN instance at		required. The segment point ABR can be a PE of a VPN/MVPN instance
	the same time, and then there would have VRF and Pseudo VRF(s)		at the same time, and then there would have VRF and Pseudo VRF(s)
	simultaneously. Note that the Pseudo VRF(s) is per the tunnel (BIER		simultaneously. Note that the Pseudo VRF(s) is per the tunnel (BIER
	tunnel or P2MP tunnel). Numbers of RootIP per a VPN/MVPN, and		tunnel or P2MP tunnel). Numbers of RootIP per a VPN/MVPN, and
	numbers of tunnels per a VPN/MVPN and a RootIP, in the BGP-MVPN		numbers of tunnels per a VPN/MVPN and a RootIP, in the BGP-MVPN
	FEC(s), will cause numbers of the Pseudo VRF allocated.		FEC(s), will cause numbers of the Pseudo VRF allocated.
	Local VpnLabel: a Local VpnLabel indicates a upstream-assigned MPLS		Local VpnLabel: a Local VpnLabel indicates a upstream-assigned MPLS
	Label locally on the segment point ABR when downstream BIER		Label locally on the segment point ABR when downstream BIER
	forwarding using IP lookup is required. Local VpnLabel is 1:1 to		forwarding using IP lookup is required. Local VpnLabel is 1:1 to
	Pseudo VRF, and it is assumed that a Pseudo VRF always indicates a		Pseudo VRF, and it is assumed that a Pseudo VRF always indicates a
	Local VpnLabel within it.		Local VpnLabel within it.
	o Getting a much better multicast join latency by eliminating the
	round trip interaction of S-PMSI AD routes and Leaf AD routes.
	Especially, the S-PMSI A-D routes may need a data-driven procedure
	to trigger, and make the multicast join latency even worse.
	o Greatly reducing the number of S-PMSI A-D routes that BFIR and
	BFERs need to save.
	o Consolidated forwarding procedure of IP lookup for every BIER
	Overlay functioning routers, such as BFIR, BFER, segmentation
	point BFR, and segmentation point BFR with BFER function.
	3. Problem Statement and Considerations		3. Problem Statement and Considerations
	3.1. Problem Statement		3.1. Problem Statement
	BIER is a stateless multicast forwarding by introducing a multicast-		BIER is a stateless multicast forwarding by introducing a multicast-
	specific BIER header in the data plane. The maximal number of BFERs		specific BIER header in the data plane. The maximal number of BFERs
	a packet can reach is limited by the bit string length of a BIER		a packet can reach is limited by the bit string length of a BIER
	header. For a network with many routers in multiple IGP areas		header. For a network with many routers in multiple IGP areas
	(typically an Inter-Area network), it may be expected to use a		(typically an Inter-Area network), it may be expected to use a
	segmented MVPN when deploying BIER because operators don't want to		segmented MVPN when deploying BIER because operators don't want to
End of changes. 5 change blocks.
	20 lines changed or deleted		8 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/