< draft-wang-bier-rh-bier-03.txt		draft-wang-bier-rh-bier-04.txt >
	BIER Working Group W. Wang		BIER Working Group W. Wang
	Internet-Draft A. Wang		Internet-Draft A. Wang
	Intended status: Standards Track China Telecom		Intended status: Standards Track China Telecom
	Expires: July 2, 2022 December 29, 2021		Expires: September 8, 2022 H. Chen
			Futurewei
			G. Mishra
			Verizon Inc.
			March 7, 2022
	Routing Header Based BIER Information Encapsulation		Routing Header Based BIER Information Encapsulation
	draft-wang-bier-rh-bier-03		draft-wang-bier-rh-bier-04
	Abstract		Abstract
	This draft proposes one new encapsulation schema of Bit Index		This draft proposes one new encapsulation schema of Bit Index
	Explicit Replication (BIER) information to transfer the multicast		Explicit Replication (BIER) information to transfer the multicast
	packets within the IPv6 network. By using a new type of IPv6 Routing		packets within the IPv6 network. By using a new type of IPv6 Routing
	Header to forward the packet, the original source address and		Header to forward the packet, the original source address and
	destination address of the multicast packet is kept unchanged along		destination address of the multicast packet is kept unchanged along
	the forwarding path. Such encapsulation schema can make full use of		the forwarding path. Such encapsulation schema can make full use of
	the existing IPv6 quality assurance solutions to provide high-quality		the existing IPv6 quality assurance solutions to provide high-quality
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 41 ¶
	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 July 2, 2022.		This Internet-Draft will expire on September 8, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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
	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. Conventions used in this document . . . . . . . . . . . . . . 3		2. Conventions used in this document . . . . . . . . . . . . . . 3
	3. BIER Routing Header . . . . . . . . . . . . . . . . . . . . . 3		3. BIER Routing Header . . . . . . . . . . . . . . . . . . . . . 3
	4. Multicast Packet Forwarding Procedures . . . . . . . . . . . 5		4. Multicast Packet Forwarding Procedures . . . . . . . . . . . 5
	4.1. All nodes in BIER domain support BIER Routing Header . . 6		4.1. All nodes in BIER domain support BIER Routing Header . . 6
	4.2. Some nodes in BIER domain do not support BIER Routing		4.2. Some nodes in BIER domain do not support BIER Routing
	Header . . . . . . . . . . . . . . . . . . . . . . . . . 7		Header . . . . . . . . . . . . . . . . . . . . . . . . . 8
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 9		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	7.1. Normative References . . . . . . . . . . . . . . . . . . 9		7.1. Normative References . . . . . . . . . . . . . . . . . . 10
	7.2. Informative References . . . . . . . . . . . . . . . . . 10		7.2. Informative References . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	Bit Index Explicit Replication (BIER) is a new multicast technology		Bit Index Explicit Replication (BIER) is a new multicast technology
	based on IPv6 defined in [RFC8279]. In BIER domain, the set of		based on IPv6 defined in [RFC8279]. In BIER domain, the set of
	destination nodes of multicast message is mapped into a BitString and		destination nodes of multicast message is mapped into a BitString and
	encapsulated into the BIER header. The position of each bit in the		encapsulated into the BIER header. The position of each bit in the
	BitString represents an BFER. Compared with the traditional		BitString represents an BFER. Compared with the traditional
	multicast technologies, the nodes in BIER domain do not need to		multicast technologies, the nodes in BIER domain do not need to
	maintain a multicast tree and keep the multicast flow state for each		maintain a multicast tree and keep the multicast flow state for each
	skipping to change at page 3, line 8 ¶		skipping to change at page 3, line 13 ¶
	changed along the forwarding path.		changed along the forwarding path.
	The differences between the above two BIER encapsulation and		The differences between the above two BIER encapsulation and
	forwarding schemes are unfavorable for the development of BIER and		forwarding schemes are unfavorable for the development of BIER and
	its derivatives. In addition, when there is error in the forward		its derivatives. In addition, when there is error in the forward
	process of the multicast packet, the change of source address and		process of the multicast packet, the change of source address and
	destination address during transmission will increase the difficulty		destination address during transmission will increase the difficulty
	of fault location and traceability.		of fault location and traceability.
	This draft proposes a BIER information transmission scheme without		This draft proposes a BIER information transmission scheme without
	changing the multicast source and destination addresses. The		changing the multicast source and destination addresses in the outer
	relevant BIER information is encapsulated within the newly defined		IPv6 header. The relevant BIER information is encapsulated within
	IPv6 Routing Header type, each intermediate BIER router will route		the newly defined IPv6 Routing Header type, each intermediate BIER
	the multicast packet based on the BitString information and its		router will route the multicast packet based on the BitString
	associated BIFT. The multicast source and destination address are		information and its associated BIFT. The multicast source and
	not changed along the forwarding path.		destination address are not changed along the forwarding path.
	The characteristics of such schema are helpful to the rapid fault		The characteristics of such schema are helpful to the rapid fault
	location and traceability, and can make full use of the existing IPv6		location and traceability, and can make full use of the existing IPv6
	quality assurance technologies to provide high-quality multicast		quality assurance technologies to provide high-quality multicast
	service.		service.
	2. Conventions used in this document		2. Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	skipping to change at page 5, line 15 ¶		skipping to change at page 5, line 38 ¶
	o BitString(variable): the length must be reflected in the BSL		o BitString(variable): the length must be reflected in the BSL
	field. The string saved in this field is used to identify the		field. The string saved in this field is used to identify the
	destination BFER of the packet.		destination BFER of the packet.
	4. Multicast Packet Forwarding Procedures		4. Multicast Packet Forwarding Procedures
	Based on the newly defined BIER Routing Header, the nodes support		Based on the newly defined BIER Routing Header, the nodes support
	BIER Routing Header will perform the following steps to forward the		BIER Routing Header will perform the following steps to forward the
	multicast packets:		multicast packets:
	1) When a BFIR receive a multicast packet, it will encapsulate a IPv6		1) When a BFIR receive a multicast packet, it will find out the
	Header with BIER Routing Header. The payload is user data, the		destination address and RD that relate to the source interface of the
	source address is the IPv6 address of BFIR, and destination address		packet. BFIR looks up its End.MVPN mapping table to find the
	is the destination address of original multicast packet. BitString		associated End.MVPN, and encapsulate a IPv6 Header with BIER Routing
	in BIER Routing Header indicates the BFERs that want to receives such		Header. The payload is user data, the source address is the IPv6
			address of BFIR, and destination address is End.MVPN. BitString in
			BIER Routing Header indicates the BFERs that want to receives such
	multicast packet.		multicast packet.
	2) BFIR checks whether there is BIFT corresponding to the BIFT-id		2) BFIR checks whether there is BIFT corresponding to the BIFT-id
	locally. If not, it will discard the packet; otherwise, it will		locally. If not, it will discard the packet; otherwise, it will
	check whether the direct-connected node support BIER Routing Header.		check whether the direct-connected node support BIER Routing Header.
	If the direct-connected node supports BIER Routing Header, proceeding		If the direct-connected node supports BIER Routing Header, proceeding
	to step 3). If the direct-connected node doesn't support BIER		to step 3). If the direct-connected node doesn't support BIER
	Routing Header, proceeding to step 2.1) .		Routing Header, proceeding to step 2.1) .
	2.1) BFIR Calculates the IPv6 address of next hop that support BIER		2.1) BFIR Calculates the IPv6 address of next hop that support BIER
	skipping to change at page 5, line 44 ¶		skipping to change at page 6, line 20 ¶
	outer IPv6 Header, and its own IPv6 address is used as the source		outer IPv6 Header, and its own IPv6 address is used as the source
	address of the outer IPv6 Header. BitString will not be changed.		address of the outer IPv6 Header. BitString will not be changed.
	2.3) Sending the encapsulated packet to the direct-connected node,		2.3) Sending the encapsulated packet to the direct-connected node,
	the node will perform normal IPv6 forwarding according to the outer		the node will perform normal IPv6 forwarding according to the outer
	IPv6 Header.		IPv6 Header.
	3) Performing the normal BIER forwarding process as described in		3) Performing the normal BIER forwarding process as described in
	[RFC8279].		[RFC8279].
	For a BFR, it performs the above procedures except 1).		For a BFR, it performs as described in Section 4.2.
	The detail procedures for forwarding the multicast packets based on		The detail procedures for forwarding the multicast packets based on
	the newly defined Routing Header are described in the following		the newly defined Routing Header are described in the following
	sections.		sections.
	4.1. All nodes in BIER domain support BIER Routing Header		4.1. All nodes in BIER domain support BIER Routing Header
	+---+		+---+
	+-----------+ B +----------+		+-----------+ B +----------+
	| +---+ |		| +---+ |
	skipping to change at page 7, line 4 ¶		skipping to change at page 7, line 24 ¶
	Header +------------------------------------+		Header +------------------------------------+
	with | IPv6 Multicast Destination Address |		with | IPv6 Multicast Destination Address |
	BIER +------------------------------------+		BIER +------------------------------------+
	Routing| BIER RH(BitString = 00001100) |		Routing| BIER RH(BitString = 00001100) |
	Header +------------------------------------+		Header +------------------------------------+
	| Original multicast packet |		| Original multicast packet |
	+------------------------------------+		+------------------------------------+
	Packet 3		Packet 3
	+------------------------------------+		+------------------------------------+
	IPv6 | IPv6 Address of A |		IPv6 | IPv6 Address of A |
	Header +------------------------------------+		Header +------------------------------------+
	with | IPv6 Multicast Destination Address |		with | IPv6 Multicast Destination Address |
	BIER +------------------------------------+		BIER +------------------------------------+
	Routing| BIER RH(BitString = 00000100) |		Routing| BIER RH(BitString = 00000100) |
	Header +------------------------------------+		Header +------------------------------------+
	| Original multicast packet |		| Original multicast packet |
	+------------------------------------+		+------------------------------------+
	Figure 2: All nodes in BIER domain support BIER Routing Header		Figure 2: All nodes in BIER domain support BIER Routing Header
	The topology is shown in Figure 2, node A-F support BIER Routing		The topology is shown in Figure 2, node A-F support BIER Routing
	Header. The packet need to be transmitted from A to F. The changes		Header. The packet need to be transmitted from A to F. The changes
	of the Routing Header have been given in Figure 2.		of the Routing Header have been given in Figure 2.
	1). Node A is BFIR, when it receives a multicast packet, it will		1). Node A is BFIR, when it receives a multicast packet, it will
	encapsulate a IPv6 Header with BIER Routing Header to the packet.		encapsulate a IPv6 Header with BIER Routing Header to the packet.
	The source address is the IPv6 address of itself, and the destination
	address is the destination address of original multicast packet.
	2). Node A checks whether there is BIFT corresponding to the BIFT-id		2). Node A checks whether there is BIFT corresponding to the BIFT-id
	locally. If not, discarding the packet; otherwise, forwarding the		locally. If not, discarding the packet; otherwise, forwarding the
	packet according to the BIFT related to the BIFT-id.		packet according to the BIFT related to the BIFT-id.
			3). Node D-E repeat the step 2).
			4). Node F looks up the associated table and submits the packet to
			the new multicast downstreams.
	During the forwarding procedures, the source & destination address in		During the forwarding procedures, the source & destination address in
	IPv6 header are not changed, only the BitString in BIER Routing		IPv6 header are not changed, only the BitString in BIER Routing
	Header is updated.		Header is updated.
	4.2. Some nodes in BIER domain do not support BIER Routing Header		4.2. Some nodes in BIER domain do not support BIER Routing Header
	+---+		+---+
	+-----------+ B +-----------+		+-----------+ B +-----------+
	| +---+ |		| +---+ |
	| 0:01000000 |		| 0:01000000 |
	skipping to change at page 9, line 17 ¶		skipping to change at page 9, line 42 ¶
	to the packet. The source IPv6 address is the IPv6 address of		to the packet. The source IPv6 address is the IPv6 address of
	itself, and the destination IPv6 address is the IPv6 address of node		itself, and the destination IPv6 address is the IPv6 address of node
	E. Then, sending the packet to node C.		E. Then, sending the packet to node C.
	3). Node C performs normal IPv6 forwarding according to the outer		3). Node C performs normal IPv6 forwarding according to the outer
	IPv6 header and sends the packet to node E.		IPv6 header and sends the packet to node E.
	4). Node E decapsulates the outer IPv6 header and forwards the		4). Node E decapsulates the outer IPv6 header and forwards the
	packet according to the BIFT to node F.		packet according to the BIFT to node F.
			5). Node F looks up the associated table and submits the packet to
			the new multicast downstreams.
	In the forwarding procedures, the source address and destination		In the forwarding procedures, the source address and destination
	address in the Inner IPv6 Header are not changed, only the BitString		address in the Inner IPv6 Header are not changed, only the BitString
	in BIER Routing Header is updated.		in BIER Routing Header is updated.
	5. Security Considerations		5. Security Considerations
	TBD		TBD
	6. IANA Considerations		6. IANA Considerations
	skipping to change at page 10, line 16 ¶		skipping to change at page 10, line 47 ¶
	Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation		Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
	for Bit Index Explicit Replication (BIER) in MPLS and Non-		for Bit Index Explicit Replication (BIER) in MPLS and Non-
	MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January		MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
	2018, <https://www.rfc-editor.org/info/rfc8296>.		2018, <https://www.rfc-editor.org/info/rfc8296>.
	7.2. Informative References		7.2. Informative References
	[I-D.ietf-bier-bierin6]		[I-D.ietf-bier-bierin6]
	Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,		Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
	H., and G. Mishra, "Supporting BIER in IPv6 Networks		H., and G. Mishra, "Supporting BIER in IPv6 Networks
	(BIERin6)", draft-ietf-bier-bierin6-01 (work in progress),		(BIERin6)", draft-ietf-bier-bierin6-04 (work in progress),
	December 2021.		March 2022.
	[I-D.xie-bier-ipv6-encapsulation]		[I-D.xie-bier-ipv6-encapsulation]
	Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,		Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
	Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,		Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
	"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-		"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
	xie-bier-ipv6-encapsulation-10 (work in progress),		xie-bier-ipv6-encapsulation-10 (work in progress),
	February 2021.		February 2021.
	Authors' Addresses		Authors' Addresses
	skipping to change at line 465 ¶		skipping to change at page 11, line 29 ¶
	Email: weiwang94@foxmail.com		Email: weiwang94@foxmail.com
	Aijun Wang		Aijun Wang
	China Telecom		China Telecom
	Beiqijia Town, Changping District		Beiqijia Town, Changping District
	Beijing, Beijing 102209		Beijing, Beijing 102209
	China		China
	Email: wangaj3@chinatelecom.cn		Email: wangaj3@chinatelecom.cn
			Huaimo Chen
			Futurewei
			Beiqijia Town, Changping District
			Boston, MA
			USA
			Email: Huaimo.chen@futurewei.com
			Gyan S. Mishra
			Verizon Inc.
			13101 Columbia Pike
			Silver Spring MD 20904
			United States of America
			Phone: 301 502-1347
			Email: gyan.s.mishra@verizon.com
End of changes. 15 change blocks.
	27 lines changed or deleted		38 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/