rfc9871v5.txt		rfc9871.txt
	skipping to change at line 645 ¶		skipping to change at line 645 ¶
	BGP-LU/BGP-IP (e.g., Appendix A.3.2) for brownfield scenarios.		BGP-LU/BGP-IP (e.g., Appendix A.3.2) for brownfield scenarios.
	Route resolution via a different color C2 can be automated by		Route resolution via a different color C2 can be automated by
	attaching BGP Color-EC C2 to CAR route (E2, C1), leveraging automated		attaching BGP Color-EC C2 to CAR route (E2, C1), leveraging automated
	steering as described in Section 8.4 of "Segment Routing Policy		steering as described in Section 8.4 of "Segment Routing Policy
	Architecture" [RFC9256] for BGP CAR routes. This mechanism is		Architecture" [RFC9256] for BGP CAR routes. This mechanism is
	illustrated in Appendix B.2. This mechanism SHOULD be supported.		illustrated in Appendix B.2. This mechanism SHOULD be supported.
	For CAR route resolution, if Color-EC color is present with the		For CAR route resolution, if Color-EC color is present with the
	route, it takes precedence over the route's intent color. The		route, it takes precedence over the route's intent color. The
	route’s intent color is the LCM-EC color if present (see		route's intent color is the LCM-EC color if present (see
	Section 2.9.5), or else it is the NLRI color.		Section 2.9.5), or else it is the NLRI color.
	Local policy takes precedence over the color-based automated		Local policy takes precedence over the color-based automated
	resolution specified above.		resolution specified above.
	The color-aware route (N, C1) may be provided by BGP CAR itself in a		The color-aware route (N, C1) may be provided by BGP CAR itself in a
	hierarchical transport routing design. In such cases, based on the		hierarchical transport routing design. In such cases, based on the
	procedures described above, recursive resolution may occur over the		procedures described above, recursive resolution may occur over the
	same or different CAR route type. Section 7.1.2 describes a scenario		same or different CAR route type. Section 7.1.2 describes a scenario
	where CAR (E, C) route resolves over CAR IP Prefix route.		where CAR (E, C) route resolves over CAR IP Prefix route.
End of changes. 1 change blocks.
	1 lines changed or deleted		1 lines changed or added
This html diff was produced by rfcdiff 1.48.