< draft-zhang-bier-babel-extensions-05.txt		draft-zhang-bier-babel-extensions-06.txt >
	BIER WG Z. Zhang		BIER WG Z. Zhang
	Internet-Draft ZTE Corporation		Internet-Draft ZTE Corporation
	Intended status: Standards Track A. Przygienda		Intended status: Standards Track A. Przygienda
	Expires: November 11, 2021 Juniper Networks		Expires: 11 May 2022 Juniper Networks
	May 10, 2021		7 November 2021
	BIER in BABEL		BIER in BABEL
	draft-zhang-bier-babel-extensions-05		draft-zhang-bier-babel-extensions-06
	Abstract		Abstract
	BIER introduces a novel multicast architecture. It does not require		BIER introduces a novel multicast architecture. It does not require
	a signaling protocol to explicitly build multicast distribution		a signaling protocol to explicitly build multicast distribution
	trees, nor does it require intermediate nodes to maintain any per-		trees, nor does it require intermediate nodes to maintain any per-
	flow state.		flow state.
	Babel defines a distance-vector routing protocol that operates in a		Babel defines a distance-vector routing protocol that operates in a
	robust and efficient fashion both in wired as well as in wireless		robust and efficient fashion both in wired as well as in wireless
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 November 11, 2021.		This Internet-Draft will expire on 11 May 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		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 . . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. Conventions Used in This Document . . . . . . . . . . . . . . 2		3. Conventions Used in This Document . . . . . . . . . . . . . . 3
	4. Advertisement of BIER information . . . . . . . . . . . . . . 3		4. Advertisement of BIER information . . . . . . . . . . . . . . 3
	4.1. BIER BFR-prefix and BIER sub-TLV . . . . . . . . . . . . 3		4.1. BIER BFR-prefix and BIER sub-TLV . . . . . . . . . . . . 3
	4.1.1. BIER sub-TLV . . . . . . . . . . . . . . . . . . . . 3		4.1.1. BIER sub-TLV . . . . . . . . . . . . . . . . . . . . 3
	4.2. BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . . 4		4.2. BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . . 4
	4.3. BIER non-MPLS Encapsulation sub-sub-TLV . . . . . . . . . 5		4.3. BIER non-MPLS Encapsulation sub-sub-TLV . . . . . . . . . 5
	4.3.1. BIER IPv6 transportation sub-sub-TLV . . . . . . . . 5		4.3.1. BIER IPv6 transportation sub-sub-TLV . . . . . . . . 6
	5. Tree types and tunneling . . . . . . . . . . . . . . . . . . 6		5. Tree types and tunneling . . . . . . . . . . . . . . . . . . 6
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 6		6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
	8.1. Normative References . . . . . . . . . . . . . . . . . . 6		8.1. Normative References . . . . . . . . . . . . . . . . . . 6
	8.2. Informative References . . . . . . . . . . . . . . . . . 7		8.2. Informative References . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	skipping to change at page 2, line 44 ¶		skipping to change at page 2, line 43 ¶
	maintain any per-flow state. All procedures necessary to support		maintain any per-flow state. All procedures necessary to support
	BIER are abbreviated by the "BIER architecture" moniker in this		BIER are abbreviated by the "BIER architecture" moniker in this
	document.		document.
	[RFC8966] define a distance-vector routing protocol under the name of		[RFC8966] define a distance-vector routing protocol under the name of
	"Babel". Babel operates in a robust and efficient fashion both in		"Babel". Babel operates in a robust and efficient fashion both in
	ordinary wired as well as in wireless mesh networks.		ordinary wired as well as in wireless mesh networks.
	2. Terminology		2. Terminology
	The terminology of this documents follows [RFC8279], [RFC6126],		The terminology of this documents follows [RFC8279] and [RFC8966].
	[RFC7557] and [RFC8966].
	3. Conventions Used in This Document		3. 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", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	4. Advertisement of BIER information		4. Advertisement of BIER information
	skipping to change at page 3, line 45 ¶		skipping to change at page 4, line 5 ¶
	| Type | Length |		| Type | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BAR | IPA | subdomain-id |		| BAR | IPA | subdomain-id |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BFR-id |		| BFR-id |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| sub-sub-TLVs (variable) |		| sub-sub-TLVs (variable) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: BIER sub-TLV		Figure 1: BIER sub-TLV
	o Type: as indicated in IANA section.		* Type: as indicated in IANA section.
	o Length: 1 octet. Include the length of BIER sub-TLV and potential		* Length: 1 octet. Include the length of BIER sub-TLV and potential
	length of the sub-sub-TLVs.		length of the sub-sub-TLVs.
	o BAR: BIER Algorithm. Specifies a BIER-specific algorithm used to		* BAR: BIER Algorithm. Specifies a BIER-specific algorithm used to
	calculate underlay paths to reach BFERs. Values are allocated		calculate underlay paths to reach BFERs. Values are allocated
	from the "BIER Algorithms" registry. 1 octet.		from the "BIER Algorithms" registry. 1 octet.
	o IPA: IGP Algorithm. Specifies an IGP Algorithm to either modify,		* IPA: IGP Algorithm. Specifies an IGP Algorithm to either modify,
	enhance, or replace the calculation of underlay paths to reach		enhance, or replace the calculation of underlay paths to reach
	BFERs as defined by the BAR value. Values are from the IGP		BFERs as defined by the BAR value. Values are from the IGP
	Algorithm registry. 1 octet.		Algorithm registry. 1 octet.
	o subdomain-id: Unique value identifying the BIER sub-domain. 1		* subdomain-id: Unique value identifying the BIER sub-domain. 1
	octet.		octet.
	o BFR-id: A 2 octet field encoding the BFR-id, as documented in		* BFR-id: A 2 octet field encoding the BFR-id, as documented in
	[RFC8279]. If no BFR-id has been assigned this field is set to		[RFC8279]. If no BFR-id has been assigned this field is set to
	the invalid BFR-id.		the invalid BFR-id.
	4.2. BIER MPLS Encapsulation sub-sub-TLV		4.2. BIER MPLS Encapsulation sub-sub-TLV
	The BIER MPLS Encapsulation sub-sub-TLV can be carried by BIER sub-		The BIER MPLS Encapsulation sub-sub-TLV can be carried by BIER sub-
	TLV. The format and restrictions are aligned with [RFC8401],		TLV. The format and restrictions are aligned with [RFC8401],
	[RFC8444] and [I-D.ietf-bier-ospfv3-extensions]. This sub-sub-TLV		[RFC8444] and [I-D.ietf-bier-ospfv3-extensions]. This sub-sub-TLV
	carries the information for the BIER MPLS encapsulation including the		carries the information for the BIER MPLS encapsulation including the
	label range for a specific BSL for a certain <MT,SD> pair.		label range for a specific BSL for a certain <MT,SD> pair.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length |		| Type | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Max SI |BS Len | Label |		| Max SI |BS Len | Label |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: MPLS Encapsulation sub-sub-TLV		Figure 2: MPLS Encapsulation sub-sub-TLV
	o Type: value of 1 indicating MPLS encapsulation.		* Type: value of 1 indicating MPLS encapsulation.
	o Length: 1 octet
	o Max SI: Maximum Set Identifier (Section 1 of [RFC8279]) used in		* Length: 1 octet
			* Max SI: Maximum Set Identifier (Section 1 of [RFC8279]) used in
	the encapsulation for this BIER subdomain for this BitString		the encapsulation for this BIER subdomain for this BitString
	length, 1 octet. Each SI maps to a single label in the label		length, 1 octet. Each SI maps to a single label in the label
	range. The first label is for SI=0, the second label is for SI=1,		range. The first label is for SI=0, the second label is for SI=1,
	etc. If the label associated with the Maximum Set Identifier		etc. If the label associated with the Maximum Set Identifier
	exceeds the 20-bit range, the sub-sub-TLV MUST be ignored.		exceeds the 20-bit range, the sub-sub-TLV MUST be ignored.
	o Local BitString Length (BS Len): Encoded BitString length as per		* Local BitString Length (BS Len): Encoded BitString length as per
	[RFC8296]. 4 bits.		[RFC8296]. 4 bits.
	o Label: First label, 20 bits. The labels are as defined in		* Label: First label, 20 bits. The labels are as defined in
	[RFC8296].		[RFC8296].
	4.3. BIER non-MPLS Encapsulation sub-sub-TLV		4.3. BIER non-MPLS Encapsulation sub-sub-TLV
	The BIER non-MPLS Encapsulation sub-sub-TLV can be carried by BIER		The BIER non-MPLS Encapsulation sub-sub-TLV can be carried by BIER
	sub-TLV. The format and restrictions are aligned with		sub-TLV. The format and restrictions are aligned with
	[I-D.ietf-bier-lsr-ethernet-extensions]. This sub-sub-TLV carries		[I-D.ietf-bier-lsr-ethernet-extensions]. This sub-sub-TLV carries
	the information for the BIER MPLS encapsulation including the label		the information for the BIER MPLS encapsulation including the label
	range for a specific BSL for a certain <MT,SD> pair.		range for a specific BSL for a certain <MT,SD> pair.
	skipping to change at page 5, line 27 ¶		skipping to change at page 5, line 36 ¶
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length |		| Type | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Max SI | BIFT-id |		| Max SI | BIFT-id |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|BS Len | Reserved |		|BS Len | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 3: non-MPLS Encapsulation sub-sub-TLV		Figure 3: non-MPLS Encapsulation sub-sub-TLV
	o Type: value of 2 indicating non-MPLS encapsulation.		* Type: value of 2 indicating non-MPLS encapsulation.
	o Length: 1 octet		* Length: 1 octet
	o Max SI: Maximum Set Identifier (Section 1 of [RFC8279]) used in		* Max SI: Maximum Set Identifier (Section 1 of [RFC8279]) used in
	the encapsulation for this BIER subdomain for this BitString		the encapsulation for this BIER subdomain for this BitString
	length, 1 octet. The first BIFT-id is for SI=0, the second BIFT-		length, 1 octet. The first BIFT-id is for SI=0, the second BIFT-
	id is for SI=1, etc. If the BIFT-id associated with the Maximum		id is for SI=1, etc. If the BIFT-id associated with the Maximum
	Set Identifier exceeds the 20-bit range, the sub-sub-TLV MUST be		Set Identifier exceeds the 20-bit range, the sub-sub-TLV MUST be
	ignored.		ignored.
	o BIFT-id: A 3-octet field, where the 20 rightmost bits represent		* BIFT-id: A 3-octet field, where the 20 rightmost bits represent
	the first BIFT-id in the BIFT-id range. The 4 leftmost bits MUST		the first BIFT-id in the BIFT-id range. The 4 leftmost bits MUST
	be ignored. The "BIFT-id range" is the set of 20-bit values		be ignored. The "BIFT-id range" is the set of 20-bit values
	beginning with the BIFT-id and ending with (BIFT-id + (Max SI)).		beginning with the BIFT-id and ending with (BIFT-id + (Max SI)).
	These BIFT-id's are used for BIER forwarding as described in		These BIFT-id's are used for BIER forwarding as described in
	[RFC8279] and [RFC8296].		[RFC8279] and [RFC8296].
	o Local BitString Length (BS Len): Encoded BitString length as per		* Local BitString Length (BS Len): Encoded BitString length as per
	[RFC8296]. 4 bits.		[RFC8296]. 4 bits.
	4.3.1. BIER IPv6 transportation sub-sub-TLV		4.3.1. BIER IPv6 transportation sub-sub-TLV
	The BIER IPv6 transportation sub-sub-TLV can be carried by BIER non-		The BIER IPv6 transportation sub-sub-TLV can be carried by BIER non-
	MPLS Encapsulation sub-sub-TLV. The format and restrictions are		MPLS Encapsulation sub-sub-TLV. The format and restrictions are
	aligned with [I-D.zhang-bier-bierin6]. A node that requires IPv6		aligned with [I-D.ietf-bier-bierin6]. A node that requires IPv6
	encapsualtion MUST advertise the BIER IPv6 transportation sub-sub-TLV		encapsualtion MUST advertise the BIER IPv6 transportation sub-sub-TLV
	according to local configuration or policy in the BIER domain to		according to local configuration or policy in the BIER domain to
	request other BFRs to always use IPv6 encapsulation.		request other BFRs to always use IPv6 encapsulation.
	The format is the same with the definition in section 4.1,		The format is the same with the definition in section 4.1,
	[I-D.zhang-bier-bierin6].		[I-D.ietf-bier-bierin6].
	5. Tree types and tunneling		5. Tree types and tunneling
	Since Babel is performing a diffusion computation, support for		Since Babel is performing a diffusion computation, support for
	different tree types is not as natural as with link-state protocols.		different tree types is not as natural as with link-state protocols.
	Hence this specification is assuming that normal Babel reachability		Hence this specification is assuming that normal Babel reachability
	computation is performed without further modifications.		computation is performed without further modifications.
	BIER architecture does not rely on all routers in a domain performing		BIER architecture does not rely on all routers in a domain performing
	BFR procedures. How to support tunnels that will allow to tunnel		BFR procedures. How to support tunnels that will allow to tunnel
	BIER across such routers in Babel is for further study.		BIER across such routers in Babel is for further study.
	6. Security Considerations		6. Security Considerations
	TBD		Security considerations discussed in [RFC8296], [RFC8966] apply to
			this document
	7. IANA Considerations		7. IANA Considerations
	A new type of Babel update sub-TLV needs to be defined for BIER		A new type of Babel update sub-TLV needs to be defined for BIER
	information advertisement.		information advertisement.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[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>.
	[RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126,
	DOI 10.17487/RFC6126, April 2011,
	<https://www.rfc-editor.org/info/rfc6126>.
	[RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing
	Protocol", RFC 7557, DOI 10.17487/RFC7557, May 2015,
	<https://www.rfc-editor.org/info/rfc7557>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[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>.
	skipping to change at page 7, line 34 ¶		skipping to change at page 7, line 38 ¶
	Extensions for Bit Index Explicit Replication (BIER)",		Extensions for Bit Index Explicit Replication (BIER)",
	RFC 8444, DOI 10.17487/RFC8444, November 2018,		RFC 8444, DOI 10.17487/RFC8444, November 2018,
	<https://www.rfc-editor.org/info/rfc8444>.		<https://www.rfc-editor.org/info/rfc8444>.
	[RFC8966] Chroboczek, J. and D. Schinazi, "The Babel Routing		[RFC8966] Chroboczek, J. and D. Schinazi, "The Babel Routing
	Protocol", RFC 8966, DOI 10.17487/RFC8966, January 2021,		Protocol", RFC 8966, DOI 10.17487/RFC8966, January 2021,
	<https://www.rfc-editor.org/info/rfc8966>.		<https://www.rfc-editor.org/info/rfc8966>.
	8.2. Informative References		8.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)", Work in Progress, Internet-Draft, draft-ietf-
			bier-bierin6-00, 14 June 2021,
			<https://www.ietf.org/archive/id/draft-ietf-bier-
			bierin6-00.txt>.
	[I-D.ietf-bier-lsr-ethernet-extensions]		[I-D.ietf-bier-lsr-ethernet-extensions]
	Dhanaraj, S., Yan, G., Wijnands, I., Psenak, P., Zhang,		Dhanaraj, S., Yan, G., Wijnands, I., Psenak, P., Zhang,
	Z., and J. Xie, "LSR Extensions for BIER over Ethernet",		Z., and J. Xie, "LSR Extensions for BIER over Ethernet",
	draft-ietf-bier-lsr-ethernet-extensions-02 (work in		Work in Progress, Internet-Draft, draft-ietf-bier-lsr-
	progress), December 2020.		ethernet-extensions-02, 2 December 2020,
			<https://www.ietf.org/archive/id/draft-ietf-bier-lsr-
			ethernet-extensions-02.txt>.
	[I-D.ietf-bier-ospfv3-extensions]		[I-D.ietf-bier-ospfv3-extensions]
	Psenak, P., Nainar, N. K., and I. Wijnands, "OSPFv3		Psenak, P., Nainar, N. K., and I. Wijnands, "OSPFv3
	Extensions for BIER", draft-ietf-bier-ospfv3-extensions-03		Extensions for BIER", Work in Progress, Internet-Draft,
	(work in progress), November 2020.		draft-ietf-bier-ospfv3-extensions-04, 18 May 2021,
			<https://www.ietf.org/archive/id/draft-ietf-bier-ospfv3-
	[I-D.zhang-bier-bierin6]		extensions-04.txt>.
	Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
	H., and G. Mishra, "Supporting BIER in IPv6 Networks
	(BIERin6)", draft-zhang-bier-bierin6-09 (work in
	progress), February 2021.
	Authors' Addresses		Authors' Addresses
	Zheng(Sandy) Zhang		Zheng(Sandy) Zhang
	ZTE Corporation		ZTE Corporation
	No. 50 Software Ave, Yuhuatai Distinct
	Nanjing
	China
	Email: zhang.zheng@zte.com.cn		Email: zhang.zheng@zte.com.cn
	Tony Przygienda		Tony Przygienda
	Juniper Networks		Juniper Networks
	Email: prz@juniper.net		Email: prz@juniper.net
End of changes. 30 change blocks.
	57 lines changed or deleted		50 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/