rfc9513v3.txt		rfc9513.txt
	skipping to change at line 372 ¶		skipping to change at line 372 ¶
	Locators associated with Flexible Algorithms SHOULD NOT be advertised		Locators associated with Flexible Algorithms SHOULD NOT be advertised
	in the base OSPFv3 prefix reachability advertisements. Advertising		in the base OSPFv3 prefix reachability advertisements. Advertising
	the Flexible Algorithm locator in a regular prefix reachability		the Flexible Algorithm locator in a regular prefix reachability
	advertisement would make it available for non-Flexible Algorithm		advertisement would make it available for non-Flexible Algorithm
	forwarding (i.e., algorithm 0).		forwarding (i.e., algorithm 0).
	The procedures for OSPFv3 Flexible Algorithm for SR-MPLS, as		The procedures for OSPFv3 Flexible Algorithm for SR-MPLS, as
	specified in [RFC9350], also apply for SRv6; these procedures include		specified in [RFC9350], also apply for SRv6; these procedures include
	a) ASBR reachability, b) inter-area, external, and NSSA prefix		a) ASBR reachability, b) inter-area, external, and NSSA prefix
	advertisements, and 3) the use of those prefix advertisements in		advertisements, and c) the use of those prefix advertisements in
	Flexible Algorithm route computation.		Flexible Algorithm route computation.
	6. Advertisement of Anycast Property		6. Advertisement of Anycast Property
	Both prefixes and SRv6 Locators may be configured as anycast, and as		Both prefixes and SRv6 Locators may be configured as anycast, and as
	such, the same value can be advertised by multiple routers. It is		such, the same value can be advertised by multiple routers. It is
	useful for other routers to know that the advertisement is for an		useful for other routers to know that the advertisement is for an
	anycast identifier.		anycast identifier.
	The AC-bit (value 0x80) in the OSPFv3 PrefixOptions field [RFC5340]		The AC-bit (value 0x80) in the OSPFv3 PrefixOptions field [RFC5340]
	skipping to change at line 1201 ¶		skipping to change at line 1201 ¶
	applicable for the "OSPFv3 Extended-LSA Sub-TLVs" registry.		applicable for the "OSPFv3 Extended-LSA Sub-TLVs" registry.
	| Note: Allocations made in this registry for sub-TLVs that are		| Note: Allocations made in this registry for sub-TLVs that are
	| associated with OSPFv3 SRv6 Locator TLVs MUST be evaluated for		| associated with OSPFv3 SRv6 Locator TLVs MUST be evaluated for
	| their applicability as OSPFv3 Extended-LSA sub-TLVs, which are		| their applicability as OSPFv3 Extended-LSA sub-TLVs, which are
	| required to be allocated in the "OSPFv3 Extended-LSA Sub-TLVs"		| required to be allocated in the "OSPFv3 Extended-LSA Sub-TLVs"
	| registry.		| registry.
	13.10. OSPFv3 Extended-LSA Sub-TLVs		13.10. OSPFv3 Extended-LSA Sub-TLVs
	IANA has added the the following note to the "OSPFv3 Extended-LSA		IANA has added the following note to the "OSPFv3 Extended-LSA Sub-
	Sub-TLVs" registry within the "Open Shortest Path First v3 (OSPFv3)		TLVs" registry within the "Open Shortest Path First v3 (OSPFv3)
	Parameters" registry group. The purpose of this note is to ensure		Parameters" registry group. The purpose of this note is to ensure
	that any document requesting allocations in this registry for sub-		that any document requesting allocations in this registry for sub-
	TLVs of any of the OSPFv3 Extended Prefix TLVs checks if allocations		TLVs of any of the OSPFv3 Extended Prefix TLVs checks if allocations
	are also applicable for the "OSPFv3 SRv6 Locator LSA Sub-TLVs"		are also applicable for the "OSPFv3 SRv6 Locator LSA Sub-TLVs"
	registry defined in this document.		registry defined in this document.
	| Note: Allocations made in this registry for sub-TLVs that are		| Note: Allocations made in this registry for sub-TLVs that are
	| associated with OSPFv3 Extended TLVs related to prefix		| associated with OSPFv3 Extended TLVs related to prefix
	| advertisements MUST be evaluated for their applicability as OSPFv3		| advertisements MUST be evaluated for their applicability as OSPFv3
	| SRv6 Locator sub-TLVs, which are required to be allocated in the		| SRv6 Locator sub-TLVs, which are required to be allocated in the
	skipping to change at line 1314 ¶		skipping to change at line 1314 ¶
	14.2. Informative References		14.2. Informative References
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003,
	<https://www.rfc-editor.org/info/rfc3630>.		<https://www.rfc-editor.org/info/rfc3630>.
	[RFC9514] Dawra, G., Filsfils, C., Talaulikar, K., Ed., Chen, M.,		[RFC9514] Dawra, G., Filsfils, C., Talaulikar, K., Ed., Chen, M.,
	Bernier, D., and B. Decraene, "Border Gateway Protocol -		Bernier, D., and B. Decraene, "Border Gateway Protocol -
	Link State (BGP-LS) Extensions for Segment Routing over		Link State (BGP-LS) Extensions for Segment Routing over
	IPv6 (SRv6)", RFC 9514, DOI 10.17487/RFC9514, October		IPv6 (SRv6)", RFC 9514, DOI 10.17487/RFC9514, November
	2023, <https://www.rfc-editor.org/info/rfc9514>.		2023, <https://www.rfc-editor.org/info/rfc9514>.
	Acknowledgements		Acknowledgements
	The authors would like to acknowledge the contributions of Dean Cheng		The authors would like to acknowledge the contributions of Dean Cheng
	in the early draft versions of this document. The authors would like		in the early draft versions of this document. The authors would like
	to thank Ran Chen and Detao Zhao for their suggestions related to the		to thank Ran Chen and Detao Zhao for their suggestions related to the
	extension of PrefixOptions for the signaling of the anycast property.		extension of PrefixOptions for the signaling of the anycast property.
	The authors would like to thank Chenzichao, Dirk Goethals, Baalajee		The authors would like to thank Chenzichao, Dirk Goethals, Baalajee
End of changes. 3 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.