< draft-zhang-bier-babel-extensions-04.txt		draft-zhang-bier-babel-extensions-05.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: May 19, 2021 Juniper Networks		Expires: November 11, 2021 Juniper Networks
	November 15, 2020		May 10, 2021
	BIER in BABEL		BIER in BABEL
	draft-zhang-bier-babel-extensions-04		draft-zhang-bier-babel-extensions-05
	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 May 19, 2021.		This Internet-Draft will expire on November 11, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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/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 38 ¶		skipping to change at page 2, line 38 ¶
	1. Introduction		1. Introduction
	[RFC8279] introduces a novel multicast architecture. It does not		[RFC8279] introduces a novel multicast architecture. It does not
	require a signaling protocol to explicitly build multicast		require a signaling protocol to explicitly build multicast
	distribution trees, nor does it require intermediate nodes to		distribution trees, nor does it require intermediate nodes to
	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.
	[I-D.ietf-babel-rfc6126bis] define a distance-vector routing protocol		[RFC8966] define a distance-vector routing protocol under the name of
	under the name of "Babel". Babel operates in a robust and efficient		"Babel". Babel operates in a robust and efficient fashion both in
	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], [RFC6126],
	[RFC7557] and [I-D.ietf-babel-rfc6126bis].		[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
	In case a router is configured with BIER information, and Babel is		In case a router is configured with BIER information, and Babel is
	the routing protocol used, such a router MAY use Babel protocol to		the routing protocol used, such a router MAY use Babel protocol to
	announce the BIER information using the BIER sub-TLV specified below.		announce the BIER information using the BIER sub-TLV specified below.
	4.1. BIER BFR-prefix and BIER sub-TLV		4.1. BIER BFR-prefix and BIER sub-TLV
	BFR-prefix and according information is carried in a Babel Update TLV		BFR-prefix and according information is carried in a Babel Update TLV
	per [I-D.ietf-babel-rfc6126bis]. A new sub-TLV is defined to convey		per [RFC8966]. A new sub-TLV is defined to convey further BIER
	further BIER information such as BFR-id, sub-domain-id and BSL. Two		information such as BFR-id, sub-domain-id and BSL. Two sub-sub-TLVs
	sub-sub-TLVs are carried as payload of BIER sub-TLV.		are carried as payload of BIER sub-TLV.
	The mandatory bit of BIER sub-TLV should be set to 0. If a router		The mandatory bit of BIER sub-TLV should be set to 0. If a router
	cannot recognize a sub-TLV, the router MUST ignore this unknown sub-		cannot recognize a sub-TLV, the router MUST ignore this unknown sub-
	TLV.		TLV.
	4.1.1. BIER sub-TLV		4.1.1. BIER sub-TLV
	The BIER sub-TLV format aligns exactly with the definition and		The BIER sub-TLV format aligns exactly with the definition and
	restrictions in [RFC8401] , [RFC8444] and		restrictions in [RFC8401] , [RFC8444] and
	[I-D.ietf-bier-ospfv3-extensions]. It is a sub-TLV of Babel update		[I-D.ietf-bier-ospfv3-extensions]. It is a sub-TLV of Babel update
	skipping to change at page 6, line 35 ¶		skipping to change at page 6, line 35 ¶
	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
	[I-D.ietf-babel-rfc6126bis]
	Chroboczek, J. and D. Schinazi, "The Babel Routing
	Protocol", draft-ietf-babel-rfc6126bis-20 (work in
	progress), August 2020.
	[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,		[RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126,
	DOI 10.17487/RFC6126, April 2011,		DOI 10.17487/RFC6126, April 2011,
	<https://www.rfc-editor.org/info/rfc6126>.		<https://www.rfc-editor.org/info/rfc6126>.
	[RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing		[RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing
	skipping to change at page 7, line 32 ¶		skipping to change at page 7, line 28 ¶
	Zhang, "Bit Index Explicit Replication (BIER) Support via		Zhang, "Bit Index Explicit Replication (BIER) Support via
	IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,		IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
	<https://www.rfc-editor.org/info/rfc8401>.		<https://www.rfc-editor.org/info/rfc8401>.
	[RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A.,		[RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A.,
	Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2		Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2
	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
			Protocol", RFC 8966, DOI 10.17487/RFC8966, January 2021,
			<https://www.rfc-editor.org/info/rfc8966>.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-bier-lsr-ethernet-extensions]		[I-D.ietf-bier-lsr-ethernet-extensions]
	Dhanaraj, S., Wijnands, I., Psenak, P., Zhang, Z., Yan,		Dhanaraj, S., Yan, G., Wijnands, I., Psenak, P., Zhang,
	G., 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-01 (work in		draft-ietf-bier-lsr-ethernet-extensions-02 (work in
	progress), July 2019.		progress), December 2020.
	[I-D.ietf-bier-ospfv3-extensions]		[I-D.ietf-bier-ospfv3-extensions]
	Psenak, P., Nainar, N., and I. Wijnands, "OSPFv3		Psenak, P., Nainar, N. K., and I. Wijnands, "OSPFv3
	Extensions for BIER", draft-ietf-bier-ospfv3-extensions-02		Extensions for BIER", draft-ietf-bier-ospfv3-extensions-03
	(work in progress), May 2020.		(work in progress), November 2020.
	[I-D.zhang-bier-bierin6]		[I-D.zhang-bier-bierin6]
	Zhang, Z., Zhang, Z., Wijnands, I., Bidgoli, H., and M.		Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
	McBride, "BIER in IPv6 (BIERin6)", draft-zhang-bier-		H., and G. Mishra, "Supporting BIER in IPv6 Networks
	bierin6-07 (work in progress), July 2020.		(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		No. 50 Software Ave, Yuhuatai Distinct
	Nanjing		Nanjing
	China		China
	Email: zhang.zheng@zte.com.cn		Email: zhang.zheng@zte.com.cn
End of changes. 12 change blocks.
	27 lines changed or deleted		27 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/