rfc9859v2.txt		rfc9859.txt
	skipping to change at line 381 ¶		skipping to change at line 381 ¶
	sender MUST send a separate notification for each one.		sender MUST send a separate notification for each one.
	When a primary name server publishes a new RRset in the child, there		When a primary name server publishes a new RRset in the child, there
	typically is a time delay until all publicly visible copies of the		typically is a time delay until all publicly visible copies of the
	zone are updated. If the primary sends a notification at the exact		zone are updated. If the primary sends a notification at the exact
	time of publication, there is a potential for CDS/CDNSKEY/CSYNC		time of publication, there is a potential for CDS/CDNSKEY/CSYNC
	processing to be attempted before the corresponding records are		processing to be attempted before the corresponding records are
	served. As a result, a desired update may not be detected (or appear		served. As a result, a desired update may not be detected (or appear
	inconsistent), preventing it from being applied.		inconsistent), preventing it from being applied.
	Therefore, it is RECOMMENDED that the child delay sending		Therefore, it is RECOMMENDED that the child would delay sending
	notifications to the recipient until a consistent public view of the		notifications to the recipient until a consistent public view of the
	pertinent records is ensured.		pertinent records could be ensured.
	4.2.1. Timeouts and Error Handling		4.2.1. Timeouts and Error Handling
	NOTIFY messages are expected to elicit a response from the recipient		NOTIFY messages are expected to elicit a response from the recipient
	([RFC1996], Section 4.7). If no response is received, senders SHOULD		([RFC1996], Section 4.7). If no response is received, senders SHOULD
	employ the same logic as for SOA notifications ([RFC1996], Sections		employ the same logic as for SOA notifications ([RFC1996], Sections
	3.5 and 3.6).		3.5 and 3.6).
	The recipient's attempt to act upon the delegation update request may		The recipient's attempt to act upon the delegation update request may
	fail for a variety of reasons (e.g., due to violation of the		fail for a variety of reasons (e.g., due to violation of the
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.