< draft-chen-bier-te-ospfv3-00.txt		draft-chen-bier-te-ospfv3-01.txt >
	Network Working Group H. Chen		Network Working Group H. Chen
	Internet-Draft M. McBride		Internet-Draft M. McBride
	Intended status: Standards Track Futurewei		Intended status: Standards Track Futurewei
	Expires: October 16, 2021 A. Wang		Expires: 28 January 2022 A. Wang
	China Telecom		China Telecom
	G. Mishra		G. Mishra
	Verizon Inc.		Verizon Inc.
	Y. Fan		Y. Fan
	Casa Systems		Casa Systems
	L. Liu		L. Liu
	Fujitsu		Fujitsu
	X. Liu		X. Liu
	Volta Networks		Volta Networks
	April 14, 2021		27 July 2021
	OSPFv3 Extensions for BIER-TE		OSPFv3 Extensions for BIER-TE
	draft-chen-bier-te-ospfv3-00		draft-chen-bier-te-ospfv3-01
	Abstract		Abstract
	This document describes OSPFv3 extensions for distributing		This document describes OSPFv3 extensions for distributing
	BitPositions configured on the links in "Bit Index Explicit		BitPositions configured on the links in "Bit Index Explicit
	Replication Traffic Engineering" (BIER-TE) domain.		Replication Traffic Engineering" (BIER-TE) domain.
	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 49 ¶		skipping to change at page 1, line 49 ¶
	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 October 16, 2021.		This Internet-Draft will expire on 28 January 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
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Extensions to OSPFv3 . . . . . . . . . . . . . . . . . . . . 3		2. Extensions to OSPFv3 . . . . . . . . . . . . . . . . . . . . 3
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 4		3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	6.1. Normative References . . . . . . . . . . . . . . . . . . 5		6.1. Normative References . . . . . . . . . . . . . . . . . . 5
	6.2. Informative References . . . . . . . . . . . . . . . . . 6		6.2. Informative References . . . . . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	[I-D.ietf-bier-te-arch] introduces Bit Index Explicit Replication		[I-D.ietf-bier-te-arch] introduces Bit Index Explicit Replication
	(BIER) Traffic/Tree Engineering (BIER-TE). It is an architecture for		(BIER) Traffic/Tree Engineering (BIER-TE). It is an architecture for
	per-packet stateless explicit point to multipoint (P2MP) multicast		per-packet stateless explicit point to multipoint (P2MP) multicast
	path/tree. A link in a BIER-TE domain has its BitPositions. For a		path/tree. A link in a BIER-TE domain has its BitPositions. For a
	link between two nodes X and Y, there are two BitPositions for two		link between two nodes X and Y, there are two BitPositions for two
	forward connected adjacencies. These two adjacency BitPositions		forward connected adjacencies. These two adjacency BitPositions
	could be configured on nodes X and Y respectively. The BitPosition		could be configured on nodes X and Y respectively. The BitPosition
	configured on X is the forward connected adjacency of Y. The		configured on X is the forward connected adjacency of Y. The
	BitPosition configured on Y is the forward connected adjacency of X.		BitPosition configured on Y is the forward connected adjacency of X.
	This document proposes OSPFv3 extensions for distributing		This document proposes OSPFv3 extensions for distributing
	BitPositions configured on the links in "Bit Index Explicit		BitPositions configured on the links in "Bit Index Explicit
	Replication Traffic Engineering" (BIER-TE) domain.		Replication Traffic Engineering" (BIER-TE) domain.
	1.1. Terminology		1.1. Terminology
	BIER: Bit Index Explicit Replication.		BIER: Bit Index Explicit Replication.
	BIER-TE: BIER Traffic Engineering.		BIER-TE: BIER Traffic Engineering.
	BFR: Bit-Forwarding Router.		BFR: Bit-Forwarding Router.
	BFIR: Bit-Forwarding Ingress Router.		BFIR: Bit-Forwarding Ingress Router.
	BFER: Bit-Forwarding Egress Router.		BFER: Bit-Forwarding Egress Router.
	BFR-id: BFR Identifier. It is a number in the range [1,65535].		BFR-id: BFR Identifier. It is a number in the range [1,65535].
	BFR-NBR: BFR Neighbor.		BFR-NBR: BFR Neighbor.
	LSA: Link State Advertisement.		LSA: Link State Advertisement.
	OSPF: Open Shortest Path First.		OSPF: Open Shortest Path First.
	2. Extensions to OSPFv3		2. Extensions to OSPFv3
	This section describes protocol extensions to OSPFv3 for distributing		This section describes protocol extensions to OSPFv3 for distributing
	BIER-TE information such as the BitPositions configured on the links		BIER-TE information such as the BitPositions configured on the links
	in a BIER-TE domain.		in a BIER-TE domain.
	[RFC8362] defines OSPFv3 Extended Router LSA, which may include		[RFC8362] defines OSPFv3 Extended Router LSA, which may include
	multiple Router-Link TLVs. A Router-Link TLV defines a single router		multiple Router-Link TLVs. A Router-Link TLV defines a single router
	link. A Router-Link TLV may include a BIER-TE Sub-TLV below for		link. A Router-Link TLV may include a BIER-TE Sub-TLV below for
	skipping to change at page 3, line 46 ¶		skipping to change at page 3, line 40 ¶
	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 (TBD1) | Length |		| Type (TBD1) | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| sub-domain-id | MT-ID | BAR | IPA |		| sub-domain-id | MT-ID | BAR | IPA |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BitPosition | DrEndBitPosition |		| BitPosition | DrEndBitPosition |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	~ ~		~ ~
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: BIER-TE Sub-TLV in Router-Link TLV		Figure 1: BIER-TE Sub-TLV in Router-Link TLV
	Type: TBD1 is to be assigned by IANA.		Type: TBD1 is to be assigned by IANA.
	Length: Variable, dependent on Sub-Sub-TLVs.		Length: Variable, dependent on Sub-Sub-TLVs.
	sub-domain-id: Unique value identifying a BIER-TE sub-domain.		sub-domain-id: Unique value identifying a BIER-TE sub-domain.
	MT-ID: Multi-Topology ID identifying the topology that is associated		MT-ID: Multi-Topology ID identifying the topology that is associated
	with the BIER-TE sub-domain.		with the BIER-TE sub-domain.
	BAR: Single-octet BIER Algorithm used to calculate underlay paths to		BAR: Single-octet BIER Algorithm used to calculate underlay paths to
	reach other BFRs. Values are allocated from the "BIER		reach other BFRs. Values are allocated from the "BIER
	skipping to change at page 4, line 35 ¶		skipping to change at page 4, line 31 ¶
	connection to Transit Network or say LAN).		connection to Transit Network or say LAN).
	DrEndBitPosition: A 2-octet field encoding the BitPosition of the		DrEndBitPosition: A 2-octet field encoding the BitPosition of the
	connection on the designated router (DR) end. This field is		connection on the designated router (DR) end. This field is
	valid when the Link Type in the Router-Link TLV containing this		valid when the Link Type in the Router-Link TLV containing this
	Sub-TLV is 2 (i.e., Transit Network or LAN). For the other		Sub-TLV is 2 (i.e., Transit Network or LAN). For the other
	value of the Link Type, this field MUST be ignored. The		value of the Link Type, this field MUST be ignored. The
	DrEndBitPosition may be configured on the link/interface to a		DrEndBitPosition may be configured on the link/interface to a
	transit network (i.e., broadcast link or say LAN).		transit network (i.e., broadcast link or say LAN).
	No Sub-Sub-TLV is defined so far. Note that if each of BitPosition		No Sub-TLV is defined so far. Note that if each of BitPosition and
	and DrEndBitPosition uses more than 2 octets, we use 4 or more octets		DrEndBitPosition uses more than 2 octets, we use 4 or more octets for
	for each of them.		each of them.
	3. Security Considerations		3. Security Considerations
	TBD.		TBD.
	4. IANA Considerations		4. IANA Considerations
	Under "OSPFv3 Extended-LSA sub-TLV registry" as defined in [RFC8362],		Under "OSPFv3 Extended-LSA Sub-TLVs registry" as defined in
	IANA is requested to assign a new registry type for BIER-TE Sub-TLV		[RFC8362], IANA is requested to assign a new registry value for BIER-
	as follows:		TE Sub-TLV as follows:
	+==============+===================+=====================+		+==============+===================+=====================+
	| Sub-TLV Type | Sub-TLV Name | reference |		| Value | Description | reference |
	+==============+===================+=====================+		+==============+===================+=====================+
	| TBD1 | BIER-TE | This document |		| TBD1 (30) | BIER-TE | This document |
	+--------------+-------------------+---------------------+		+--------------+-------------------+---------------------+
	5. Acknowledgements		5. Acknowledgements
	The authors would like to thank people for their comments to this		The authors would like to thank Acee Lindem and Tony Przygienda for
	work.		their comments on this work.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[I-D.ietf-bier-te-arch]		[I-D.ietf-bier-te-arch]
	Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering		Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering
	for Bit Index Explicit Replication (BIER-TE)", draft-ietf-		for Bit Index Explicit Replication (BIER-TE)", Work in
	bier-te-arch-09 (work in progress), October 2020.		Progress, Internet-Draft, draft-ietf-bier-te-arch-10, 9
			July 2021, <https://www.ietf.org/archive/id/draft-ietf-
			bier-te-arch-10.txt>.
	[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>.
	[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,
	skipping to change at page 6, line 42 ¶		skipping to change at page 6, line 35 ¶
	[RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S.,		[RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S.,
	and A. Dolganow, "Multicast VPN Using Bit Index Explicit		and A. Dolganow, "Multicast VPN Using Bit Index Explicit
	Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April		Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April
	2019, <https://www.rfc-editor.org/info/rfc8556>.		2019, <https://www.rfc-editor.org/info/rfc8556>.
	Authors' Addresses		Authors' Addresses
	Huaimo Chen		Huaimo Chen
	Futurewei		Futurewei
	Boston, MA		Boston, MA,
	USA		United States of America
	Email: Huaimo.chen@futurewei.com		Email: Huaimo.chen@futurewei.com
	Mike McBride		Mike McBride
	Futurewei		Futurewei
	Email: michael.mcbride@futurewei.com		Email: michael.mcbride@futurewei.com
	Aijun Wang		Aijun Wang
	China Telecom		China Telecom
	Beiqijia Town, Changping District		Beiqijia Town, Changping District
	Beijing, 102209		Beijing
			102209
	China		China
	Email: wangaj3@chinatelecom.cn		Email: wangaj3@chinatelecom.cn
	Gyan S. Mishra		Gyan S. Mishra
	Verizon Inc.		Verizon Inc.
	13101 Columbia Pike		13101 Columbia Pike
	Silver Spring MD 20904		Silver Spring, MD 20904
	USA		United States of America
	Phone: 301 502-1347		Phone: 301 502-1347
	Email: gyan.s.mishra@verizon.com		Email: gyan.s.mishra@verizon.com
	Yanhe Fan		Yanhe Fan
	Casa Systems		Casa Systems
	USA		United States of America
	Email: yfan@casa-systems.com		Email: yfan@casa-systems.com
	Lei Liu		Lei Liu
	Fujitsu		Fujitsu
			United States of America
	USA
	Email: liulei.kddi@gmail.com		Email: liulei.kddi@gmail.com
	Xufeng Liu		Xufeng Liu
	Volta Networks		Volta Networks
	McLean, VA		McLean, VA
	USA		United States of America
	Email: xufeng.liu.ietf@gmail.com		Email: xufeng.liu.ietf@gmail.com
End of changes. 28 change blocks.
	44 lines changed or deleted		44 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/