rfc9666v2.txt		rfc9666.txt
	skipping to change at line 246 ¶		skipping to change at line 246 ¶
	circuits between Outside Edge Routers and Inside Edge Routers.		circuits between Outside Edge Routers and Inside Edge Routers.
	Area Proxy Boundary multi-access circuits (i.e., Ethernets in LAN		Area Proxy Boundary multi-access circuits (i.e., Ethernets in LAN
	mode) with multiple Inside Edge Routers on them are not supported.		mode) with multiple Inside Edge Routers on them are not supported.
	The Inside Edge Router on any boundary LAN MUST NOT flood Inside		The Inside Edge Router on any boundary LAN MUST NOT flood Inside
	Router LSPs on this link. Boundary LANs SHOULD NOT be enabled for		Router LSPs on this link. Boundary LANs SHOULD NOT be enabled for
	Level 1. An Inside Edge Router may be elected as the Designated		Level 1. An Inside Edge Router may be elected as the Designated
	Intermediate System (DIS) for a Boundary LAN. In this case, using		Intermediate System (DIS) for a Boundary LAN. In this case, using
	the Area Proxy System ID as the basis for the LAN pseudonode		the Area Proxy System ID as the basis for the LAN pseudonode
	identifier could create a collision, so the Insider Edge Router		identifier could create a collision, so the Insider Edge Router
	SHOULD compose the pseudonode identifier using its built-in system		SHOULD compose the pseudonode identifier using its originally
	identifier. This choice of pseudonode identifier may confuse		configured system identifier. This choice of pseudonode identifier
	neighbors with an extremely strict implementation. In this case, the		may confuse neighbors with an extremely strict implementation. In
	Inside Edge Router may be configured with priority 0, causing an		this case, the Inside Edge Router may be configured with priority 0,
	Outside Router to be elected as the DIS.		causing an Outside Router to be elected as the DIS.
	2.1. Segment Routing		2.1. Segment Routing
	If the Inside Area supports Segment Routing (SR) [RFC8402], then all		If the Inside Area supports Segment Routing (SR) [RFC8402], then all
	Inside Nodes MUST advertise a Segment Routing Global Block (SRGB).		Inside Nodes MUST advertise a Segment Routing Global Block (SRGB).
	The first value of the SRGB advertised by all Inside Nodes MUST start		The first value of the SRGB advertised by all Inside Nodes MUST start
	at the same value. If the Area Leader detects SRGBs that do not		at the same value. If the Area Leader detects SRGBs that do not
	start with the same value, it MUST log an error and not advertise an		start with the same value, it MUST log an error and not advertise an
	SRGB in the Proxy LSP. The range advertised for the area will be the		SRGB in the Proxy LSP. The range advertised for the area will be the
	minimum of that advertised by all Inside Nodes.		minimum of that advertised by all Inside Nodes.
End of changes. 1 change blocks.
	5 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48.