< draft-xie-bier-ipv6-isis-extension-01.txt		draft-xie-bier-ipv6-isis-extension-02.txt >
	Network Working Group J. Xie		Network Working Group J. Xie
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track A. Wang		Intended status: Standards Track A. Wang
	Expires: July 17, 2020 China Telecom		Expires: April 30, 2021 China Telecom
	G. Yan		G. Yan
	S. Dhanaraj		S. Dhanaraj
			X. Geng
	Huawei Technologies		Huawei Technologies
	January 14, 2020		October 27, 2020
	BIER IPv6 Encapsulation (BIERv6) Support via IS-IS		BIER IPv6 Encapsulation (BIERv6) Support via IS-IS
	draft-xie-bier-ipv6-isis-extension-01		draft-xie-bier-ipv6-isis-extension-02
	Abstract		Abstract
	This document defines IS-IS extensions to support multicast		This document defines IS-IS extensions to support multicast
	forwarding using the Bit Index Explicit Replication (BIER) with IPv6		forwarding using the Bit Index Explicit Replication (BIER) with IPv6
	encapsulation (BIERv6).		encapsulation (BIERv6).
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 44 ¶
	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 17, 2020.		This Internet-Draft will expire on April 30, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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
	skipping to change at page 4, line 36 ¶		skipping to change at page 4, line 41 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Max SI |BS Len | BIFT-id |		| Max SI |BS Len | BIFT-id |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Type: 1 octet value indicating BIER IPv6 encapsulation. TBD2 to be		Type: 1 octet value indicating BIER IPv6 encapsulation. TBD2 to be
	assigned by IANA.		assigned by IANA.
	Length: 1 octet length in octets. Value 4 is set to this field.		Length: 1 octet length in octets. Value 4 is set to this field.
	Max SI: 1 octet value. Maximum Set Identifier (Section 1 of		Max SI: 1 octet value. Maximum Set Identifier (Section 1 of
	[RFC8279]) used in the encapsulation for this BIER subdomain for this		[RFC8279]) used in the encapsulation for this BIER sub-domain for
	BitString length. Each SI maps to a single BIFT-id in the BIFT-id		this BitString length. Each SI maps to a single BIFT-id in the BIFT-
	range. The first BIFT-id is for SI=0, the second BIFT-id is for		id range. 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 Set Identifier		SI=1, etc. If the BIFT-id 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.
	BS Len: 4 bits value of Local BitString Length. Encoded BitString		BS Len: 4 bits value of Local BitString Length. Encoded BitString
	length as per [RFC8296].		length as per [RFC8296].
	BIFT-id: 20 bits value. First BIFT-id of the range. The BIFT-id(s)		BIFT-id: 20 bits value. First BIFT-id of the range. The BIFT-id(s)
	are as defined in [RFC8296], or refer to		are as defined in [RFC8296], or refer to
	[I-D.ietf-bier-lsr-ethernet-extensions] for Non-MPLS encapsulation.		[I-D.ietf-bier-lsr-ethernet-extensions] for Non-MPLS encapsulation.
	4. Security Considerations		4. Security Considerations
	The procedures of this document do not, in themselves, provide		The security considerations defined in [RFC8401] and
	privacy, integrity, or authentication for the control plane or the		[I-D.xie-bier-ipv6-encapsulation] apply equally to this document.
	data plane.
	5. IANA Considerations		5. IANA Considerations
	5.1. Encapsulation sub-sub-TLV Type Code		5.1. Encapsulation sub-sub-TLV Type Code
	Allocation is expected from IANA for two sub-sub-TLV codepoints from		Allocation is expected from IANA for two sub-sub-TLV codepoints from
	the "sub-sub-TLVs for BIER Info sub-TLV" sub-registry.		the "sub-sub-TLVs for BIER Info sub-TLV" sub-registry.
	Type: TBD1 to be assigned by IANA.		Type: TBD1 to be assigned by IANA.
	skipping to change at page 5, line 45 ¶		skipping to change at page 5, line 44 ¶
	7.1. Normative References		7.1. Normative 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., Wijnands, I., Psenak, P., Zhang, Z., Yan,
	G., and J. Xie, "LSR Extensions for BIER over Ethernet",		G., and J. Xie, "LSR Extensions for BIER over Ethernet",
	draft-ietf-bier-lsr-ethernet-extensions-01 (work in		draft-ietf-bier-lsr-ethernet-extensions-01 (work in
	progress), July 2019.		progress), July 2019.
	[I-D.xie-bier-ipv6-encapsulation]		[I-D.xie-bier-ipv6-encapsulation]
	Xie, J., Geng, L., McBride, M., Asati, R., and S.		Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
	Dhanaraj, "Encapsulation for BIER in Non-MPLS IPv6		Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
	Networks", draft-xie-bier-ipv6-encapsulation-04 (work in		"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
	progress), December 2019.		xie-bier-ipv6-encapsulation-08 (work in progress), July
			2020.
	[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi		[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi
	Topology (MT) Routing in Intermediate System to		Topology (MT) Routing in Intermediate System to
	Intermediate Systems (IS-ISs)", RFC 5120,		Intermediate Systems (IS-ISs)", RFC 5120,
	DOI 10.17487/RFC5120, February 2008,		DOI 10.17487/RFC5120, February 2008,
	<https://www.rfc-editor.org/info/rfc5120>.		<https://www.rfc-editor.org/info/rfc5120>.
	[RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308,		[RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308,
	DOI 10.17487/RFC5308, October 2008,		DOI 10.17487/RFC5308, October 2008,
	<https://www.rfc-editor.org/info/rfc5308>.		<https://www.rfc-editor.org/info/rfc5308>.
	skipping to change at page 6, line 26 ¶		skipping to change at page 6, line 26 ¶
	U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4		U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4
	and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794,		and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794,
	March 2016, <https://www.rfc-editor.org/info/rfc7794>.		March 2016, <https://www.rfc-editor.org/info/rfc7794>.
	[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>.
			[RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
			Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
			for Bit Index Explicit Replication (BIER) in MPLS and Non-
			MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
			2018, <https://www.rfc-editor.org/info/rfc8296>.
			[RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z.
			Zhang, "Bit Index Explicit Replication (BIER) Support via
			IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
			<https://www.rfc-editor.org/info/rfc8401>.
	7.2. Informative References		7.2. Informative 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>.
	[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>.
	skipping to change at page 6, line 38 ¶		skipping to change at page 7, line 4 ¶
	[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>.
	[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>.
	Authors' Addresses		Authors' Addresses
	Jingrong Xie		Jingrong Xie
	Huawei Technologies		Huawei Technologies
	Email: xiejingrong@huawei.com		Email: xiejingrong@huawei.com
	Aijun Wang		Aijun Wang
	China Telecom		China Telecom
	Email: wangaj3@chinatelecom.cn		Email: wangaj3@chinatelecom.cn
	Gang Yan		Gang Yan
	Huawei Technologies		Huawei Technologies
	Email: yangang@huawei.com		Email: yangang@huawei.com
	Senthil Dhanaraj		Senthil Dhanaraj
	Huawei Technologies		Huawei Technologies
	Email: senthil.dhanaraj@huawei.com		Email: senthil.dhanaraj@huawei.com
			Xuesong Geng
			Huawei Technologies
			Email: gengxuesong@huawei.com
End of changes. 12 change blocks.
	15 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/