< draft-ietf-bier-bar-ipa-10.txt		draft-ietf-bier-bar-ipa-11.txt >
	BIER Z. Zhang		BIER Z. Zhang
	Internet-Draft A. Przygienda		Internet-Draft A. Przygienda
	Updates: 8401, 8444 (if approved) Juniper Networks		Updates: 8401, 8444 (if approved) Juniper Networks
	Intended status: Standards Track A. Dolganow		Intended status: Standards Track A. Dolganow
	Expires: 14 October 2022 Individual		Expires: 25 September 2022 Individual
	H. Bidgoli		H. Bidgoli
	Nokia		Nokia
	I. Wijnands		I. Wijnands
	Individual		Individual
	A. Gulko		A. Gulko
	Edward Jones Wealth Management		Edward Jones Wealth Management
	12 April 2022		24 March 2022
	BIER Underlay Path Calculation Algorithm and Constraints		BIER Underlay Path Calculation Algorithm and Constraints
	draft-ietf-bier-bar-ipa-12		draft-ietf-bier-bar-ipa-11
	Abstract		Abstract
	This document specifies general rules for the interaction between the		This document specifies general rules for the interaction between the
	BIER Algorithm (BAR) and the IGP Algorithm (IPA) used for underlay		BIER Algorithm (BAR) and the IGP Algorithm (IPA) used for underlay
	path calculation. The semantics defined in this document update		path calculation. The semantics defined in this document update
	RFC8401 and RFC8444.		RFC8401 and RFC8444.
	Requirements Language		Requirements Language
	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 14 October 2022.		This Internet-Draft will expire on 25 September 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2022 IETF Trust and the persons identified as the		Copyright (c) 2022 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 3, line 18 ¶		skipping to change at page 3, line 18 ¶
	semantics defined in this document update [RFC8401], [RFC8444].		semantics defined in this document update [RFC8401], [RFC8444].
	2. Updated Definition for BAR and IPA Fields		2. Updated Definition for BAR and IPA Fields
	The definition for the BAR and IPA fields in [RFC8401] and [RFC8444]		The definition for the BAR and IPA fields in [RFC8401] and [RFC8444]
	are updated as follows.		are updated as follows.
	IPA: IGP Algorithm. Specifies a generic Routing Algorithm (RA) and		IPA: IGP Algorithm. Specifies a generic Routing Algorithm (RA) and
	related Routing Constraints (RC) to calculate underlay paths to reach		related Routing Constraints (RC) to calculate underlay paths to reach
	other Bit-Forwarding Routers (BFRs). Values are from the "IGP		other Bit-Forwarding Routers (BFRs). Values are from the "IGP
	Algorithm Types" registry [RFC8665]. One Octet.		Algorithm Types" registry [RFC8665].
	BAR: BIER Algorithm. Specifies a BIER-specific Algorithm (BA) and		BAR: BIER Algorithm. Specifies a BIER-specific Algorithm (BA) and
	BIER-specific Constraints (BC) used to either modify, enhance, or		BIER-specific Constraints (BC) used to either modify, enhance, or
	replace the calculation of underlay paths to reach other BFRs as		replace the calculation of underlay paths to reach other BFRs as
	defined by the IPA value. Values are allocated from the "BIER		defined by the IPA value. Values are allocated from the "BIER
	Algorithm" registry [RFC8401]. One Octet.		Algorithm" registry [RFC8401].
	When a BAR value is defined, the corresponding BA and BC semantics		When a BAR value is defined, the corresponding BA and BC semantics
	SHOULD be specified. For an IGP Algorithm to be used as a BIER IPA,		SHOULD be specified. For an IGP Algorithm to be used as a BIER IPA,
	its RA and RC semantics SHOULD be specified.		its RA and RC semantics SHOULD be specified.
	None of the components of the BAR or IPA can be unknown. If any of		None of the components of the BAR or IPA can be unknown. If any of
	the components is not specified, it is interpreted as "NULL"		the components is not specified, it is interpreted as "NULL"
	algorithm or constraint. For example, the IGP Algorithm 0 defined in		algorithm or constraint. For example, the IGP Algorithm 0 defined in
	[RFC8665] is treated as having a NULL RC, i.e., no constraints.		[RFC8665] is treated as having a NULL RC, i.e., no constraints.
	skipping to change at page 6, line 11 ¶		skipping to change at page 6, line 11 ¶
	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>.
	[RFC8665] Psenak, P., Ed., Previdi, S., Ed., Filsfils, C., Gredler,
	H., Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
	Extensions for Segment Routing", RFC 8665,
	DOI 10.17487/RFC8665, December 2019,
	<https://www.rfc-editor.org/info/rfc8665>.
	Authors' Addresses		Authors' Addresses
	Zhaohui Zhang		Zhaohui Zhang
	Juniper Networks		Juniper Networks
	Email: zzhang@juniper.net		Email: zzhang@juniper.net
	Antoni Przygienda		Antoni Przygienda
	Juniper Networks		Juniper Networks
	Email: prz@juniper.net		Email: prz@juniper.net
	Andrew Dolganow		Andrew Dolganow
	Individual		Individual
	Email: adolgano@gmail.com		Email: adolgano@gmail.com
	Hooman Bidgoli		Hooman Bidgoli
	Nokia		Nokia
	Email: hooman.bidgoli@nokia.com		Email: hooman.bidgoli@nokia.com
	IJsbrand Wijnands		IJsbrand Wijnands
	Individual		Individual
	Email: ice@braindump.be		Email: ice@braindump.be
	Arkadiy Gulko		Arkadiy Gulko
	Edward Jones Wealth Management		Edward Jones Wealth Management
	Email: arkadiy.gulko@edwardjones.com		Email: arkadiy.gulko@edwardjones.com
End of changes. 13 change blocks.
	18 lines changed or deleted		6 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/