< draft-geng-bier-ipv6-inter-domain-00.txt		draft-geng-bier-ipv6-inter-domain-01.txt >
	Network Working Group L. Geng		Network Working Group L. Geng
	Internet-Draft China Mobile		Internet-Draft China Mobile
	Intended status: Standards Track J. Xie		Intended status: Standards Track J. Xie
	Expires: January 5, 2020 Huawei Technologies		Expires: July 17, 2020 Huawei Technologies
	M. McBride		M. McBride
	Futurewei		Futurewei
	G. Yan		G. Yan
	Huawei Technologies		Huawei Technologies
	July 4, 2019		January 14, 2020
	Inter-Domain Multicast Deployment using BIERv6		Inter-Domain Multicast Deployment using BIERv6
	draft-geng-bier-ipv6-inter-domain-00		draft-geng-bier-ipv6-inter-domain-01
	Abstract		Abstract
	Bit Index Explicit Replication IPv6 encapsulation (BIERv6) introduces		Bit Index Explicit Replication IPv6 encapsulation (BIERv6) introduces
	an approach to use IPv6 extension header to carry BIER header with		an approach to use IPv6 extension header to carry BIER header with
	IPv6 unicast address as destination address. It provides the ability		IPv6 unicast address as destination address. It provides the ability
	to replicate a packet from one router to another router in a		to replicate a packet from one router to another router in a
	different domain as well as in the same domain. This document		different domain as well as in the same domain. This document
	introduces the techniques for multicast deployment across multiple		introduces the techniques for multicast deployment across multiple
	domains using BIERv6, and demonstrate how BIERv6 is beneficial for		domains using BIERv6, and demonstrate how BIERv6 is beneficial for
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 49 ¶
	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 January 5, 2020.		This Internet-Draft will expire on July 17, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 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
	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 2, line 32 ¶		skipping to change at page 2, line 32 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. Inter-domain Multicast Overview . . . . . . . . . . . . . . . 3		3. Inter-domain Multicast Overview . . . . . . . . . . . . . . . 3
	4. Inter-domain Multicast Deployment using BIERv6 . . . . . . . 3		4. Inter-domain Multicast Deployment using BIERv6 . . . . . . . 3
	4.1. Hierarchical Multicast . . . . . . . . . . . . . . . . . 3		4.1. Hierarchical Multicast . . . . . . . . . . . . . . . . . 3
	4.2. Peering Multicast . . . . . . . . . . . . . . . . . . . . 6		4.2. Peering Multicast . . . . . . . . . . . . . . . . . . . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 8		5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	8.1. Normative References . . . . . . . . . . . . . . . . . . 8		8.1. Normative References . . . . . . . . . . . . . . . . . . 9
	8.2. Informative References . . . . . . . . . . . . . . . . . 9		8.2. Informative References . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	Bit Index Explicit Replication [RFC8296] IPv6 encapsulation (BIERv6)		Bit Index Explicit Replication [RFC8296] IPv6 encapsulation (BIERv6)
	described in [I-D.xie-bier-ipv6-encapsulation] introduces an approach		described in [I-D.xie-bier-ipv6-encapsulation] introduces an approach
	to use IPv6 extension header to carry BIER header. One BIERv6		to use IPv6 extension header to carry BIER header. One BIERv6
	option, using IPv6 unicast address as destination address provides		option, using IPv6 unicast address as destination address provides
	the ability to replicate a packet from one router to another router		the ability to replicate a packet from one router to another router
	in a different domain as well as in the same domain. This document		in a different domain as well as in the same domain. This document
	skipping to change at page 4, line 6 ¶		skipping to change at page 4, line 6 ¶
	It is described as peering multicast in this document.		It is described as peering multicast in this document.
	4. Inter-domain Multicast Deployment using BIERv6		4. Inter-domain Multicast Deployment using BIERv6
	4.1. Hierarchical Multicast		4.1. Hierarchical Multicast
	Following is an example of hierarchical deployment of multicast.		Following is an example of hierarchical deployment of multicast.
	+---------------------+		+---------------------+
	| Metro 2 (AS 64002) |		| Metro 2 (AS 65002) |
	| +-----+ +------+ |		| +-----+ +------+ |
	+-------| BR2 | | PE2x |---RCV		+-------| BR2 | | PE2x |---RCV
	/ | +-----+ +------+ |		/ | +-----+ +------+ |
	/ +---------------------+		/ +---------------------+
	+---------------------+ / Bfr-id 1 to 256		+---------------------+ / Bfr-id 1 to 256
	| Backbone (AS 64001) | /		| Backbone (AS 65001) | /
	| +------+ +-----+ /		| +------+ +-----+ /
	SRC---| PE1x | | BR1 | |		SRC---| PE1x | | BR1 | |
	| +------+ +-----+ \		| +------+ +-----+ \
	+---------------------+ \ Bfr-id 257 to 512		+---------------------+ \ Bfr-id 257 to 512
	| \ +---------------------+		| \ +---------------------+
	| \ | Metro 3 (AS 64003) |		| \ | Metro 3 (AS 65003) |
	| \ | +-----+ +------+ |		| \ | +-----+ +------+ |
	| +-------| BR3 | | PE3x |---RCV		| +-------| BR3 | | PE3x |---RCV
	| | +-----+ +------+ |		| | +-----+ +------+ |
	| +---------------------+		| +---------------------+
	| |		| |
	|<----------------- BIERv6 Domain --------------->|		|<----------------- BIERv6 Domain --------------->|
	BR = Border Router		BR = Border Router
	SRC = Multicast Source		SRC = Multicast Source
	RCV = Multicast Receiver		RCV = Multicast Receiver
	Figure 1: Inter-Domain Hierarchical Multicast		Figure 1: Inter-Domain Hierarchical Multicast
	Multicast source is connected to PE1x, and multicast receivers are		Multicast source is connected to PE1x, and multicast receivers are
	connected to PE2x and PE3x.		connected to PE2x and PE3x.
	PE1x, PE2x, PE3x is located in Backbone (AS 64001), Metro 2 (AS		PE1x, PE2x, PE3x is located in Backbone (AS 65001), Metro 2 (AS
	64002), and Metro 3 (AS 64003) respectively, and BR1, BR2, BR3 is		65002), and Metro 3 (AS 65003) respectively, and BR1, BR2, BR3 is
	boarder of these three domains. They belong to a single		boarder of these three domains. They belong to a single
	administrative domain.		administrative domain.
	IGP underlay for BIERv6 is deployed in Metro2, Metro3 respectively.		IGP underlay for BIERv6 is deployed in Metro2, Metro3 respectively.
	The bfr-ids in Metro2 and Metro 3 should be divided rationally.		The bfr-ids in Metro2 and Metro 3 should be divided rationally.
	PE1x, PE2x, PE3x uses 2001::E1, 2001::E2, 2001::E3 as IPv6 BFR-prefix		PE1x, PE2x, PE3x uses 2001:DB8::E1, 2001:DB8::E2, 2001:DB8::E3 as
	(and End.BIER function) respectively.		End.BIER IPv6 address respectively.
	BR1, BR2, BR3 uses 2001::B1, 2001::B2, 2001::B3 as IPv6 BFR-prefix		BR1, BR2, BR3 uses 2001:DB8::B1, 2001:DB8::B2, 2001:DB8::B3 as
	(and End.BIER function) respectively.		End.BIER IPv6 address respectively.
	All of them use the Non-MPLS static BSL-SD-SI BIFT encoding method		All of them use the Non-MPLS static BSL-SD-SI BIFT encoding method
	described in [I-D.ietf-bier-non-mpls-bift-encoding] as the auto-		described in [I-D.ietf-bier-non-mpls-bift-encoding] as the auto-
	generation method.		generation method.
	On BR1, static configuration can be used to construct inter-domain		On BR1, static configuration can be used to construct inter-domain
	BIERv6 forwarding table.		BIERv6 forwarding table.
	bier sub-domain 6 ipv6-underlay		bier sub-domain 6 ipv6-underlay
	bfr-prefix 2001::B1		bfr-prefix interface loopback0
	bfr-id 0		end-bier 2001:DB8::B1
	encapsulation ipv6 bsl 256 max-si 2		encapsulation ipv6 bsl 256 max-si 2
	static-bift		static-bift
	nexthop 2001::B2 bfr-id 1 to 256		nexthop end-bier 2001:DB8::B2 bfr-id 1 to 256
	nexthop 2001::B3 bfr-id 257 to 512		nexthop end-bier 2001:DB8::B3 bfr-id 257 to 512
	Accordingly, the following BIFTs will be constructed:		Accordingly, the following BIFTs will be constructed:
	BIFT correspond to SD<6>/BSL<256>/SI<0>		BIFT correspond to SD<6>/BSL<256>/SI<0>
	(neighbor = 2001::B2, F-BM = ffff....ffff)		(neighbor = 2001:DB8::B2, F-BM = ffff....ffff)
	BIFT correspond to SD<6>/BSL<256>/SI<1>		BIFT correspond to SD<6>/BSL<256>/SI<1>
	(neighbor = 2001::B3, F-BM = ffff....ffff)		(neighbor = 2001:DB8::B3, F-BM = ffff....ffff)
	On PE1x, static configuration can be used to construct inter-domain		On PE1x, static configuration can be used to construct inter-domain
	BIERv6 forwarding table.		BIERv6 forwarding table. Note that PE1x doesn't need to assign a
			valid BFR-id uniquely among many.
	bier sub-domain 6 ipv6-underlay		bier sub-domain 6 ipv6-underlay
	bfr-prefix 2001::E1		bfr-prefix interface loopback0
	bfr-id 0		end-bier 2001:DB8::E1
	encapsulation ipv6 bsl 256 max-si 2		encapsulation ipv6 bsl 256 max-si 2
	static-bift		static-bift
	nexthop 2001::B1 bfr-id 1 to 512		nexthop end-bier 2001:DB8::B1 bfr-id 1 to 512
	Accordingly, the following BIFTs will be constructed:		Accordingly, the following BIFTs will be constructed:
	BIFT correspond to SD<6>/BSL<256>/SI<0>		BIFT correspond to SD<6>/BSL<256>/SI<0>
	(neighbor = 2001::B1, F-BM = ffff....ffff)		(neighbor = 2001:DB8::B1, F-BM = ffff....ffff)
	BIFT correspond to SD<6>/BSL<256>/SI<1>		BIFT correspond to SD<6>/BSL<256>/SI<1>
	(neighbor = 2001::B1, F-BM = ffff....ffff)		(neighbor = 2001:DB8::B1, F-BM = ffff....ffff)
	Use of BGP as inter-domain underlay protocol to advertise the BIER		Use of BGP as inter-domain underlay protocol to advertise the BIER
	information from BR2 or BR2 to BR1, or from BR1 to PE1x is outside		information from BR2 or BR2 to BR1, or from BR1 to PE1x is outside
	the scope of this document.		the scope of this document.
	On each domain, two redundant border routers may be deployed, and		On each domain, two redundant border routers may be deployed, and
	anycase IPv6 address can be used on each pair of BRs as BFR-prefix.		anycase IPv6 address can be used on each pair of BRs as End.BIER IPv6
			address.
	Inter-Domain BIER will converge normally when unicast converge and		Inter-Domain BIER will converge normally when unicast converge and
	the BIFT will be reconstructed accordingly.		the BIFT will be reconstructed accordingly.
	For multicast overlay layer, there are no extensions needed. MVPN is		For multicast overlay layer, there are no extensions needed. MVPN is
	deployed on PE1x, PE2x and PE3x using sub-domain 6 and bsl 256		deployed on PE1x, PE2x and PE3x using sub-domain 6 and bsl 256
	without segmentation on border router(s).		without segmentation on border router(s).
	Note: Use of the IPv6 address configured on PE1 to identify an MVPN		Note: Use of the IPv6 address configured on PE1 to identify an MVPN
	instance can eliminate the need for BFR-id configuration on PE1x,		instance can eliminate the need for BFR-id configuration on PE1x,
	skipping to change at page 6, line 48 ¶		skipping to change at page 7, line 5 ¶
	Figure 2: Inter-Domain Peering Multicast		Figure 2: Inter-Domain Peering Multicast
	Each Administrative Domain AD-1, AD-2 or AD-3 is configured a unique		Each Administrative Domain AD-1, AD-2 or AD-3 is configured a unique
	color. Color 1, 2, 3 are used in this example.		color. Color 1, 2, 3 are used in this example.
	For routing underlay layer, the ingress router uses IGP protocol (IS-		For routing underlay layer, the ingress router uses IGP protocol (IS-
	IS as example in this document) for the domain it belongs to, and		IS as example in this document) for the domain it belongs to, and
	uses static configuration for the domain it doesn't belong to.		uses static configuration for the domain it doesn't belong to.
	Below is an example of routing underlay configuration on PE1x:		Below is an example of routing underlay configuration on PE1x. Note
			that PE1x doesn't need to assign a valid BFR-id per color.
	# PE1x routing underlay layer configuration		# PE1x routing underlay layer configuration
	bier sub-domain 6 ipv6-underlay		bier sub-domain 6 ipv6-underlay
	bfr-prefix 2001::E1		bfr-prefix interface loopback0
	bfr-id 1		end-bier 2001:DB8::E1
	encapsulation ipv6 bsl 256 max-si 1		encapsulation ipv6 bsl 256 max-si 1
	color 1 protocol isis		color 1 protocol isis
	color 2 static-bift		color 2 static-bift
	next-hop 2001::B2 bfr-id 1 to 512		nexthop end-bier 2001:DB8::B2 bfr-id 1 to 512
	color 3 static-bift		color 3 static-bift
	next-hop 2001::B3 bfr-id 1 to 256		nexthop end-bier 2001:DB8::B3 bfr-id 1 to 256
	The following lists the BIFT that will be constructed on PE1x:		The following lists the BIFT that will be constructed on PE1x:
	BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 1 ;;Ref1		BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 1 ;;Ref1
	BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 2 ;;Ref2		BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 2 ;;Ref2
	BIFT corresponding to SD<6>/BSL<256>/SI<1> for color 2 ;;Ref3		BIFT corresponding to SD<6>/BSL<256>/SI<1> for color 2 ;;Ref3
	BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 3 ;;Ref4		BIFT corresponding to SD<6>/BSL<256>/SI<0> for color 3 ;;Ref4
	Ref1: BIFT constructed using IGP.		Ref1: BIFT constructed using IGP.
	skipping to change at page 8, line 46 ¶		skipping to change at page 9, line 4 ¶
	6. IANA Considerations		6. IANA Considerations
	No IANA Allocation is required in this document.		No IANA Allocation is required in this document.
	7. Acknowledgements		7. Acknowledgements
	TBD.		TBD.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-bier-ipv6-requirements]		[I-D.ietf-bier-ipv6-requirements]
	McBride, M., Xie, J., Dhanaraj, S., and R. Asati, "BIER		McBride, M., Xie, J., Dhanaraj, S., and R. Asati, "BIER
	IPv6 Requirements", draft-ietf-bier-ipv6-requirements-00		IPv6 Requirements", draft-ietf-bier-ipv6-requirements-03
	(work in progress), May 2019.		(work in progress), November 2019.
	[I-D.ietf-bier-non-mpls-bift-encoding]		[I-D.ietf-bier-non-mpls-bift-encoding]
	Wijnands, I., Xu, X., and H. Bidgoli, "An Optional		Wijnands, I., Xu, X., and H. Bidgoli, "An Optional
	Encoding of the BIFT-id Field in the non-MPLS BIER		Encoding of the BIFT-id Field in the non-MPLS BIER
	Encapsulation", draft-ietf-bier-non-mpls-bift-encoding-01		Encapsulation", draft-ietf-bier-non-mpls-bift-encoding-02
	(work in progress), October 2018.		(work in progress), August 2019.
	[I-D.xie-bier-ipv6-encapsulation]		[I-D.xie-bier-ipv6-encapsulation]
	Xie, J., Geng, L., McBride, M., Dhanaraj, S., Yan, G., and		Xie, J., Geng, L., McBride, M., Asati, R., and S.
	Y. Xia, "Encapsulation for BIER in Non-MPLS IPv6		Dhanaraj, "Encapsulation for BIER in Non-MPLS IPv6
	Networks", draft-xie-bier-ipv6-encapsulation-01 (work in		Networks", draft-xie-bier-ipv6-encapsulation-04 (work in
	progress), June 2019.		progress), December 2019.
	[I-D.xie-bier-ipv6-mvpn]		[I-D.xie-bier-ipv6-mvpn]
	Xie, J., McBride, M., Dhanaraj, S., and L. Geng, "Use of		Xie, J., McBride, M., Dhanaraj, S., and L. Geng, "Use of
	BIER IPv6 Encapsulation (BIERv6) for Multicast VPN in IPv6		BIER IPv6 Encapsulation (BIERv6) for Multicast VPN in IPv6
	networks", draft-xie-bier-ipv6-mvpn-01 (work in progress),		networks", draft-xie-bier-ipv6-mvpn-01 (work in progress),
	July 2019.		July 2019.
	[RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation		[RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
	Subsequent Address Family Identifier (SAFI) and the BGP		Subsequent Address Family Identifier (SAFI) and the BGP
	Tunnel Encapsulation Attribute", RFC 5512,		Tunnel Encapsulation Attribute", RFC 5512,
End of changes. 30 change blocks.
	43 lines changed or deleted		45 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/