rfc9866v3.txt		rfc9866.txt
	skipping to change at line 609 ¶		skipping to change at line 609 ¶
	switch from Sentinel to Acceptor vary depending on the node's value		switch from Sentinel to Acceptor vary depending on the node's value
	of LORS before the switch:		of LORS before the switch:
	* For "GLOBALLY DOWN", the node MUST NOT modify its LORS,		* For "GLOBALLY DOWN", the node MUST NOT modify its LORS,
	PositiveCFRC, and NegativeCFRC.		PositiveCFRC, and NegativeCFRC.
	* For "LOCALLY DOWN", the node MUST set its LORS to "UP" but MUST		* For "LOCALLY DOWN", the node MUST set its LORS to "UP" but MUST
	NOT modify its PositiveCFRC and NegativeCFRC.		NOT modify its PositiveCFRC and NegativeCFRC.
	* For "UP" and "SUSPECTED DOWN", the node MUST set its LORS to "UP"		* For "UP" and "SUSPECTED DOWN", the node MUST set its LORS to "UP"
	and MUST NOT modify its PositiveCFRC, but it MUST add itself to		and MUST NOT modify its PositiveCFRC, but the node MUST add itself
	NegativeCFRC. That is, it MUST replace its NegativeCFRC, denoted		to NegativeCFRC, by replacing its NegativeCFRC, denoted oldnc,
	oldnc, with newnc = merge(oldnc, selfc), where selfc is the		with newnc = merge(oldnc, selfc), where selfc is the counter
	counter generated with self() when the node last added itself to		generated with self() when the node last added itself to its
	its PositiveCFRC.		PositiveCFRC.
	5.2. Detecting and Verifying Problems with the DODAG Root		5.2. Detecting and Verifying Problems with the DODAG Root
	Only nodes that are Sentinels take an active part in detecting		Only nodes that are Sentinels take an active part in detecting
	crashes of the DODAG root; Acceptors just disseminate their		crashes of the DODAG root; Acceptors just disseminate their
	observations, reflected in the CFRCs.		observations, reflected in the CFRCs.
	The DODAG root monitoring SHOULD be based on both internal inputs,		The DODAG root monitoring SHOULD be based on both internal inputs,
	notably the values of CFRCs and LORS, and external inputs, such as		notably the values of CFRCs and LORS, and external inputs, such as
	triggers from RPL and other protocols. External input monitoring		triggers from RPL and other protocols. External input monitoring
	skipping to change at line 815 ¶		skipping to change at line 815 ¶
	When RNFD at a node is initially inactive for a DODAG Version, the		When RNFD at a node is initially inactive for a DODAG Version, the
	node MUST NOT attach any RNFD Option to the messages it sends (in		node MUST NOT attach any RNFD Option to the messages it sends (in
	particular, because it may not know the desired CFRC length; see		particular, because it may not know the desired CFRC length; see
	Section 5.6). When the protocol has been explicitly deactivated, the		Section 5.6). When the protocol has been explicitly deactivated, the
	node MAY also decide not to attach the option to its outgoing		node MAY also decide not to attach the option to its outgoing
	messages. However, it is RECOMMENDED that it send a sufficient		messages. However, it is RECOMMENDED that it send a sufficient
	number of messages with the option to the link-local all-RPL-nodes		number of messages with the option to the link-local all-RPL-nodes
	multicast IPv6 address to allow its neighbors to learn that RNFD has		multicast IPv6 address to allow its neighbors to learn that RNFD has
	been deactivated in the current DODAG Version. In particular, it MAY		been deactivated in the current DODAG Version. In particular, it MAY
	reset its Trickle timer to this end but MAY also use some reactive		reset its Trickle timer to this end but MAY also use some reactive
	mechanisms. For example, it MAY reply with a unicast DIO or DIS		mechanisms. For example, it might reply with a unicast DIO or DIS
	containing the RNFD Option with no CFRCs to a message from a neighbor		containing the RNFD Option with no CFRCs to a message from a neighbor
	that contains the option with some CFRCs, as such a neighbor appears		that contains the option with some CFRCs, as such a neighbor appears
	not to have learned about the deactivation of RNFD.		not to have learned about the deactivation of RNFD.
	5.6. Processing CFRCs of Incompatible Lengths		5.6. Processing CFRCs of Incompatible Lengths
	The merge() and compare() operations on CFRCs require both arguments		The merge() and compare() operations on CFRCs require both arguments
	to be compatible, that is, to have the same bit length. However, the		to be compatible, that is, to have the same bit length. However, the
	processing rules for the RNFD Option (see Section 4.2) do not		processing rules for the RNFD Option (see Section 4.2) do not
	necessitate this. This fact is made use of not only in the		necessitate this. This fact is made use of not only in the
	skipping to change at line 1037 ¶		skipping to change at line 1037 ¶
	6.3. Monitoring		6.3. Monitoring
	For monitoring the operation of RNFD, its implementation SHOULD		For monitoring the operation of RNFD, its implementation SHOULD
	provide the following information about a node:		provide the following information about a node:
	* whether the protocol is active, and		* whether the protocol is active, and
	* whether LORS is "GLOBALLY DOWN".		* whether LORS is "GLOBALLY DOWN".
	This information MUST be accompanied by the recommended monitoring		This information MUST be accompanied by the monitoring parameters
	parameters provided by RPL itself [RFC6550], notably the DODAG		defined by RPL [RFC6550], including at least the DODAG Version Number
	Version number and the Rank. To offer even finer-grained visibility		and the Rank. To offer even finer-grained visibility into RNFD's
	into RNFD's state at the node, the implementation MAY also provide:		state at the node, the implementation MAY also provide:
	* the assigned role (i.e., Sentinel or Acceptor),		* the assigned role (i.e., Sentinel or Acceptor),
	* the exact value of LORS (i.e., "UP", "SUSPECTED DOWN", "LOCALLY		* the exact value of LORS (i.e., "UP", "SUSPECTED DOWN", "LOCALLY
	DOWN", or "GLOBALLY DOWN"),		DOWN", or "GLOBALLY DOWN"),
	* the two CFRCs (i.e., PositiveCFRC and NegativeCFRC), and		* the two CFRCs (i.e., PositiveCFRC and NegativeCFRC), and
	* the constants listed in Section 5.8.		* the constants listed in Section 5.8.
End of changes. 3 change blocks.
	10 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48.