< draft-wang-bier-rh-bier-01.txt		draft-wang-bier-rh-bier-02.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: April 28, 2022 October 25, 2021		Expires: April 28, 2022 October 25, 2021
	Routing Header Based BIER Information Encapsulation		Routing Header Based BIER Information Encapsulation
	draft-wang-bier-rh-bier-01		draft-wang-bier-rh-bier-02
	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 defining a new IPv6 Routing		packets within the IPv6 network. By using a new IPv6 Routing Header
	Header type, it keeps the original source address and destination		type to forward the packet, the original source address and
	address unchanged in forwarding process. The encapsulation schema		destination address of the multicast packet is kept unchanged along
	can make full use of the existing IPv6 quality assurance methods to		the forwarding path. Such encapsulation schema can make full use of
	provide high-quality multicast service.		the existing IPv6 quality assurance solutions to provide high-quality
			multicast service.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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/.
	skipping to change at page 2, line 12 ¶		skipping to change at page 2, line 13 ¶
	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. The transmission process of packets with BIER Routing Header 4		4. Multicast Packet Forwarding Procedures . . . . . . . . . . . 5
	4.1. All devices in BIER domain support BIER Routing Header . 5		4.1. All devices in BIER domain support BIER Routing Header . 5
	4.2. Some devices in BIER domain do not support BIER Routing		4.2. Some devices in BIER domain do not support BIER Routing
	Header . . . . . . . . . . . . . . . . . . . . . . . . . 6		Header . . . . . . . . . . . . . . . . . . . . . . . . . 7
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 8		5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	7. Normative References . . . . . . . . . . . . . . . . . . . . 8		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
			7.1. Normative References . . . . . . . . . . . . . . . . . . 9
			7.2. Informative References . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	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 technology, the nodes in BIER domain do not need to		multicast technology, the nodes in BIER domain do not need to
	maintain a multicast tree and save the multicast flow state for each		maintain a multicast tree and keep the multicast flow state for each
	multicast flow.		multicast flow.
	At present, there are two methods for encapsulating BIER information		Currently, there are two methods for encapsulating BIER information
	based on IPv6 in IETF: bierin6([I-D.ietf-bier-bierin6]) and		based on IPv6 in IETF: BIERn6([I-D.ietf-bier-bierin6]) and
	bierv6([I-D.xie-bier-ipv6-encapsulation]).		BIERv6([I-D.xie-bier-ipv6-encapsulation]).
	BIERin6 carries BIER information by defining a new IPv6 next header		BIERin6 carries BIER information by defining a new IPv6 next header
	type. In the process of transmission, the source address and		type. During the forwarding process, the source address and
	destination address in the header will change. BIERv6 carries bier		destination address in the header will be changed.
	related information by creating an option type of destination options
	header (i.e. bier option). During transmission, the source address
	in the header remains unchanged and the destination address will
	change.
	There are some differences between the above two BIER encapsulation		BIERv6 carries bier related information by defining an new option
	and forwarding schemes, which is unfavorable to the development of		type of destination options header (i.e. bier option). The source
	BIER and its derivatives. In addition, when there is an error in the		address in the header remains unchanged but the destination address
	transmission process of the message, the source address and		will be changed along the forwarding path.
	destination address help the operators locate and trace the fault.
	The change of source address and destination address during		The differences between the above two BIER encapsulation and
	transmission will increase the difficulty of fault location and		forwarding schemes are unfavorable for the development of BIER and
	traceability.		its derivatives. In addition, when there is error in the forward
			process of the multicast packet, the change of source address and
			destination address during transmission will increase the difficulty
			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 source and destination addresses. By defining an IPv6		changing the multicast source and destination addresses. The
	Routing Header type, it carries the relevant information of BIER and		relevant BIER information is encapsulated within the newly defined
	ensures that the source address and destination address do not change		IPv6 Routing Header type, each intermediate BIER router will route
	during message transmission. The characteristics of this scheme are		the multicast packet based on the BitString information and its
	conducive to rapid fault location and traceability, and can make full		associated BIFT. The multicast source and destination address are
	use of the existing IPv6 quality assurance technologies to provide		not changed along the forwarding path.
	high-quality multicast service.
			The characteristics of such schema are helpful to the rapid fault
			location and traceability, and can make full use of the existing IPv6
			quality assurance technologies to provide high-quality multicast
			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
	document are to be interpreted as described in [RFC2119] .		document are to be interpreted as described in [RFC2119] .
	3. BIER Routing Header		3. BIER Routing Header
	One new IPv6 Routing Header is defined according to RFC8200[RFC8200].		One new type of IPv6 Routing Header is defined according to
	The message format is shown in Figure 1.		[RFC8200]. The message format is shown in Figure 1.
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Next Header | Hdr Ext Len | Routing Type | Segment Left |		| Next Header | Hdr Ext Len | Routing Type | Segment Left |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BIFT-id | Ver | TTL |		| BIFT-id | Ver | TTL |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BSL | Entropy | DSCP |OAM|		| BSL | Entropy | DSCP |OAM|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BFIR-id |Rsv| Reserved |		| BFIR-id |Rsv| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 4, line 41 ¶		skipping to change at page 5, line 5 ¶
	o BFIR-id(16 bits): indicating BFR ID of BFIR.		o BFIR-id(16 bits): indicating BFR ID of BFIR.
	o Rsv(2 bits): unused, set to 0.		o Rsv(2 bits): unused, set to 0.
	o Reserved (14 bits): reserved field, set to 0.		o Reserved (14 bits): reserved field, set to 0.
	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. The transmission process of packets with BIER Routing Header		4. Multicast Packet Forwarding Procedures
	Based on the newly defined BIER Routing Header, the devices support		Based on the newly defined BIER Routing Header, the devices support
	BIER Routing Header resolution will perform the following steps:		BIER Routing Header will perform the following steps to forward the
			multicast packets:
	1) Checking whether there is BIFT corresponding to the BIFT-id		1) When BFIR receives the IPv6 multicast packets from the mulicast
	locally.		source, it will add BIER Routing Header to indicate the BFERs that
			want to receives such multicast packet. The encapsulated multicast
			packet will be forwarded according to the BIFT that identified by the
			BIFT-id.
	2) Checking whether the direct-connected device support BIER Routing		2) Each BFR (includes BFIR) will check whether the direct-connected
	Header. If yes, proceed to step 3; otherwise, proceed to step 2.1.		device support BIER Routing Header. If yes, proceed to step 3);
			otherwise, proceed to step 2.1).
	2.1) Calculating the IPv6 address of next hop that support BIER		2.1) Calculating the IPv6 address of next hop that support BIER
	Routing Header.		Routing Header.
	2.2) Encapsulating an outer IPv6 Header to the packet. The		2.2) Encapsulating an outer IPv6 Header to the multicast packet. The
	calculated IPv6 address is used as the destination address of the		calculated IPv6 address is used as the destination address of the
	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 next-connected device,		2.3) Sending the encapsulated packet to the direct-connected device,
	the device will perform normal IPv6 forwarding according to the outer		the device will perform normal IPv6 forwarding according to the outer
	IPv6 Header.		IPv6 Header.
	3) Performing the normal BIER forwarding process as described in		3) On the router that supports the BIER Routing Header, perform the
	[RFC8279].		normal BIER forwarding process as described in [RFC8279].
	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 devices in BIER domain support BIER Routing Header		4.1. All devices in BIER domain support BIER Routing Header
	+---+		+---+
	+-----------+ B +----------+		+-----------+ B +----------+
	| +---+ |		| +---+ |
	skipping to change at page 5, line 45 ¶		skipping to change at page 6, line 12 ¶
	+-+-+ +-+-+ +---+ +---+		+-+-+ +-+-+ +---+ +---+
	| | 0:00001000 0:00000100		| | 0:00001000 0:00000100
	| |		| |
	| |		| |
	| |		| |
	| 0:00010000 |		| 0:00010000 |
	| +---+ |		| +---+ |
	+-----------+ D +----------+		+-----------+ D +----------+
	(Packet 1) +---+		(Packet 1) +---+
	Packet 1		Packet 1
	+----------------------------+		+------------------------------------+
	IPv6 | Source IP Address = A |		IPv6 | IPv6 Address of Multicast Source |
	Header +----------------------------+		Header +------------------------------------+
	| Destination IP Address = F |		| IPv6 Multicast Destination Address |
	BIER +----------------------------+		BIER +------------------------------------+
			Routing| BitString = 00101100 |
	Routing| BitString = 00101100 |		Header +------------------------------------+
	Header +----------------------------+
	Packet 2		Packet 2
	+----------------------------+		+------------------------------------+
	IPv6 | Source IP Address = A |		IPv6 | IPv6 Address of Multicast Source |
	Header +----------------------------+		Header +------------------------------------+
	| Destination IP Address = F |		| IPv6 Multicast Destination Address |
	BIER +----------------------------+		BIER +------------------------------------+
	Routing| BitString = 00001100 |		Routing| BitString = 00001100 |
	Header +----------------------------+		Header +------------------------------------+
	Packet 3		Packet 3
	+----------------------------+		+------------------------------------+
	Inner | Source IP Address = A |		IPv6 | IPv6 Address of Multicast Source |
	IPv6 +----------------------------+		Header +------------------------------------+
	Header | Destination IP Address = F |		| IPv6 Multicast Destination Address |
	+----------------------------+		BIER +------------------------------------+
	BIER | BitString = 00000100 |		Routing| BitString = 00000100 |
	Routing+----------------------------+		Header +------------------------------------+
	Header
	Figure 2: All devices in BIER domain support BIER Routing Header		Figure 2: All devices in BIER domain support BIER Routing Header
	The topology is shown in Figure 3, device A-F support BIER Routing		The topology is shown in Figure 2, device A-F support BIER Routing
	Header resolution. The packet need to be transmitted from A to F.		Header. The packet need to be transmitted from A to F. The changes
	The change of the Header has been given in the Figure. Each device		of the Routing Header have been given in Figure 2. Each device will
	will perform the following steps after receiving the packet:		perform the following steps after receiving the packet:
	1. Checking whether there is BIFT corresponding to the BIFT-id		1). Checking whether there is BIFT corresponding to the BIFT-id
	locally. If yes, proceed to step 2; otherwise, discard the packet.		locally. If yes, proceed to step 2); otherwise, discard the packet.
	2. Checking whether the direct-connected device support BIER Routing		2). Checking whether the direct-connected device support BIER
	Header. If yes, forwarding the packet according to the BIFT related		Routing Header. If yes, forwarding the packet according to the BIFT
	to the BIFT-id; otherwise, see sectionSection 4.2 for detail		related to the BIFT-id; otherwise, see sectionSection 4.2 for detail
	procedures.		procedures.
	In this forwarding process, the source address and destination		During the forwarding procedures, the source address and destination
	address in the Inner IPv6 Header are not changed, only the BitString		address of the IPv6 multicast packet are not changed, only the
	in BIER Routing Header is changed.		BitString in BIER Routing Header is updated.
	4.2. Some devices in BIER domain do not support BIER Routing Header		4.2. Some devices in BIER domain do not support BIER Routing Header
	+---+		+---+
	+-----------+ B +-----------+		+-----------+ B +-----------+
	| +---+ |		| +---+ |
	| 0:01000000 |		| 0:01000000 |
	| |		| |
	| |		| |
	| |		| |
	+-+-+ +-+-+ (Packet 2) +---+ (Packet 3) +---+		+-+-+ +-+-+ +---+ (Packet 3) +---+
	| A |0:10000000 | C +------------+ E +------------+ F |		| A |0:10000000 | C +------------+ E +------------+ F |
	+-+-+ +-+-+ +---+ +---+		+-+-+ +-+-+ +---+ +---+
	| | 0:00001000 0:00000100		| | 0:00001000 0:00000100
	| |		| |
	| |		| |
	| |		| |
	| 0:00010000 |		| 0:00010000 |
	| +---+ |		| +---+ |
	+-----------+ D +-----------+		+-----------+ D +-----------+
	(Packet 1) +---+		(Packet 1) +---+(Packet 2)
			Packet 1
			+------------------------------------+
			IPv6 | IPv6 Address of Multicast Source |
			Header +------------------------------------+
			| IPv6 Multicast Destination Address |
			BIER +------------------------------------+
			Routing| BitString = 00101100 |
			Header +------------------------------------+
	Packet 1
	+----------------------------+
	Outer | Source IP Address = A |
	IPv6 +----------------------------+
	Header | Destination IP Address = E |
	+----------------------------+
	Inner | Source IP Address = A |
	IPv6 +----------------------------+
	Header | Destination IP Address = F |
	+----------------------------+
	BIER | BitString = 00001100 |
	Routing+----------------------------+
	Header
	Packet 2		Packet 2
	+----------------------------+		+------------------------------------+
	Outer | Source IP Address = C |		Outer | Source IP Address = D |
	IPv6 +----------------------------+		IPv6 +------------------------------------+
	Header | Destination IP Address = E |		Header | Destination IP Address = E |
	+----------------------------+		+------------------------------------+
	Inner | Source IP Address = A |		Inner | IPv6 Address of Multicast Source |
	IPv6 +----------------------------+		IPv6 +------------------------------------+
	Header | Destination IP Address = F |
	+----------------------------+		Header | IPv6 Multicast Destination Address |
	BIER | BitString = 00001100 |		+------------------------------------+
	Routing+----------------------------+		BIER | BitString = 00001100 |
			Routing+------------------------------------+
	Header		Header
	Packet 3		Packet 3
	+----------------------------+		+-------------------------------------+
	IPv6 | Source IP Address = A |		IPv6 | IPv6 Address of Multicast Source |
	Header +----------------------------+		Header +-------------------------------------+
	| Destination IP Address = F |		| IPv6 Multicast Destination Address |
	BIER +----------------------------+		BIER +-------------------------------------+
			Routing| BitString = 00000100 |
	Routing| BitString = 00000100 |		Header +-------------------------------------+
	Header +----------------------------+
	Figure 3: Some devices in BIER domain do not support BIER Routing Header		Figure 3: Some devices in BIER domain do not support BIER Routing Header
	The topology is shown in Figure 4, all devices expect device C		The topology is shown in Figure 3, all devices expect device C
	support BIER Routing Header resolution. The packet need to be		support BIER Routing Header. The packet need to be transmitted from
	transmitted from A to F. The change of the Header has been given in		A to F. The change of the Header has been given in the Figure 3.
	the Figure 4. When it is found that device C does not support BIER		When it is found that device C does not support BIER Routing Header,
	Routing Header resolution, device A will perform the following steps		device D will perform the following steps after receiving the packet:
	after receiving the packet:
	1. Calculating the IPv6 address of next hop device that supports		1. Calculating the IPv6 address of next hop device(Node E) that
	BIER Routing Header.		supports BIER Routing Header.
	2. Encapsulating an outer IPv6 Header to the packet. The calculated		2. Encapsulating an outer IPv6 Header to the packet. The calculated
	IPv6 address is used as the destination address of the outer IPv6		IPv6 address(E) is used as the destination address of the outer IPv6
	Header, and its own IPv6 address is used as the source address of the		Header, and its own IPv6 address(D) is used as the source address of
	outer IPv6 Header. BitString will not be changed.		the outer IPv6 Header. BitString will not be changed.
	3. Sending the packet to device C.		3. Sending the packet to directed-connected device C.
	After receiving the packet, device C will perform IPv6 forwarding		After receiving the packet, device C will perform IPv6 forwarding
	according the information in outer IPv6 Header, and send the packet		according the information in outer IPv6 Header, and send the packet
	to device E. Device E will send it to device F according the		to device E. Device E will send it to device F according the
	information in BIER Routing Header. In the forwarding process, the		information in BIER Routing Header. In the forwarding process, the
	source address and destination address in the Inner IPv6 Header are		source address and destination address in the Inner IPv6 Header are
	not changed.		not changed.
	5. Security Considerations		5. Security Considerations
	TBD		TBD
	6. IANA Considerations		6. IANA Considerations
	This document defines a new IPv6 Routing Header - BIER Routing		This document defines a new IPv6 Routing Header - BIER Routing
	Header. The code point is from the "Internet Protocol Version 6		Header. The code point is from the "Internet Protocol Version 6
	(IPv6) Parameters - Routing Types". It is recommended to set the		(IPv6) Parameters - Routing Types". It is recommended to set the
	code point of BIER Routing Header to 7.		code point of BIER Routing Header to 7.
	7. Normative References		7. References
	[I-D.ietf-bier-bierin6]
	Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
	H., and G. Mishra, "Supporting BIER in IPv6 Networks
	(BIERin6)", draft-ietf-bier-bierin6-00 (work in progress),
	June 2021.
	[I-D.xie-bier-ipv6-encapsulation]		7.1. Normative References
	Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
	Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
	"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
	xie-bier-ipv6-encapsulation-10 (work in progress),
	February 2021.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6		[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", STD 86, RFC 8200,		(IPv6) Specification", STD 86, RFC 8200,
	DOI 10.17487/RFC8200, July 2017,		DOI 10.17487/RFC8200, July 2017,
	<https://www.rfc-editor.org/info/rfc8200>.		<https://www.rfc-editor.org/info/rfc8200>.
	[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,		[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
	Przygienda, T., and S. Aldrin, "Multicast Using Bit Index		Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
	Explicit Replication (BIER)", RFC 8279,		Explicit Replication (BIER)", RFC 8279,
	DOI 10.17487/RFC8279, November 2017,		DOI 10.17487/RFC8279, November 2017,
	<https://www.rfc-editor.org/info/rfc8279>.		<https://www.rfc-editor.org/info/rfc8279>.
			7.2. Informative References
			[I-D.ietf-bier-bierin6]
			Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
			H., and G. Mishra, "Supporting BIER in IPv6 Networks
			(BIERin6)", draft-ietf-bier-bierin6-00 (work in progress),
			June 2021.
			[I-D.xie-bier-ipv6-encapsulation]
			Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
			Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
			"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
			xie-bier-ipv6-encapsulation-10 (work in progress),
			February 2021.
	Authors' Addresses		Authors' Addresses
	Wei Wang		Wei Wang
	China Telecom		China Telecom
	Beiqijia Town, Changping District		Beiqijia Town, Changping District
	Beijing, Beijing 102209		Beijing, Beijing 102209
	China		China
	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
End of changes. 40 change blocks.
	145 lines changed or deleted		152 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/