< draft-ietf-ospf-segment-routing-msd-19.txt		draft-ietf-ospf-segment-routing-msd-20.txt >
	skipping to change at page 1, line 14 ¶		skipping to change at page 1, line 14 ¶
	Internet-Draft Nuage Networks		Internet-Draft Nuage Networks
	Intended status: Standards Track U. Chunduri		Intended status: Standards Track U. Chunduri
	Expires: March 4, 2019 Huawei Technologies		Expires: March 4, 2019 Huawei Technologies
	S. Aldrin		S. Aldrin
	Google, Inc		Google, Inc
	P. Psenak		P. Psenak
	Cisco Systems		Cisco Systems
	August 31, 2018		August 31, 2018
	Signaling MSD (Maximum SID Depth) using OSPF		Signaling MSD (Maximum SID Depth) using OSPF
	draft-ietf-ospf-segment-routing-msd-19		draft-ietf-ospf-segment-routing-msd-20
	Abstract		Abstract
	This document defines a way for an Open Shortest Path First (OSPF)		This document defines a way for an Open Shortest Path First (OSPF)
	Router to advertise multiple types of supported Maximum SID Depths		Router to advertise multiple types of supported Maximum SID Depths
	(MSDs) at node and/or link granularity. Such advertisements allow		(MSDs) at node and/or link granularity. Such advertisements allow
	entities (e.g., centralized controllers) to determine whether a		entities (e.g., centralized controllers) to determine whether a
	particular SID stack can be supported in a given network. This		particular SID stack can be supported in a given network. This
	document defines only one type of MSD, but defines an encoding that		document defines only one type of MSD, but defines an encoding that
	can support other MSD types. Here the term OSPF means both OSPFv2		can support other MSD types. Here the term OSPF means both OSPFv2
	skipping to change at page 6, line 27 ¶		skipping to change at page 6, line 27 ¶
	If this sub-TLV is advertised multiple times in the same OSPFv2		If this sub-TLV is advertised multiple times in the same OSPFv2
	Extended Link Opaque LSA/E-Router-LSA, only the first instance of the		Extended Link Opaque LSA/E-Router-LSA, only the first instance of the
	TLV MUST be used by receiving OSPF routers. This situation SHOULD be		TLV MUST be used by receiving OSPF routers. This situation SHOULD be
	logged as an error.		logged as an error.
	If this sub-TLV is advertised multiple times for the same link in		If this sub-TLV is advertised multiple times for the same link in
	different OSPF Extended Link Opaque LSAs/E-Router-LSAs originated by		different OSPF Extended Link Opaque LSAs/E-Router-LSAs originated by
	the same OSPF router, the OSPFv2 Extended Link TLV in the OSPFv2		the same OSPF router, the OSPFv2 Extended Link TLV in the OSPFv2
	Extended Link Opaque LSA with the smallest Opaque ID or in the OSPFv3		Extended Link Opaque LSA with the smallest Opaque ID or in the OSPFv3
	E-Router-LSA with the smallest Link State ID MUSR be used by		E-Router-LSA with the smallest Link State ID MUST be used by
	receiving OSPF routers. This situation MAY be logged as a warning.		receiving OSPF routers. This situation MAY be logged as a warning.
	4. Using Node and Link MSD Advertisements		4. Using Node and Link MSD Advertisements
	When Link MSD is present for a given MSD type, the value of the Link		When Link MSD is present for a given MSD type, the value of the Link
	MSD MUST take preference over the Node MSD. When a Link MSD type is		MSD MUST take preference over the Node MSD. When a Link MSD type is
	not signalled but the Node MSD type is, then the value of that Node		not signalled but the Node MSD type is, then the value of that Node
	MSD type MUST be considered as the corresponding Link MSD type value.		MSD type MUST be considered as the corresponding Link MSD type value.
	In order to increase flooding efficiency, it is RECOMMENDED, that		In order to increase flooding efficiency, it is RECOMMENDED, that
	routers with homogenous Link MSD values advertise just the Node MSD		routers with homogenous Link MSD values advertise just the Node MSD
End of changes. 2 change blocks.
	2 lines changed or deleted		2 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/