rfc9915v3.txt		rfc9915.txt
	Internet Engineering Task Force (IETF) T. Mrugalski		Internet Engineering Task Force (IETF) T. Mrugalski
	Request for Comments: 9915 ISC		Request for Comments: 9915 ISC
	Obsoletes: 8415 B. Volz		STD: 102 B. Volz
	Category: Standards Track Individual Contributor		Obsoletes: 8415 Individual Contributor
	ISSN: 2070-1721 M. Richardson		Category: Standards Track M. Richardson
	SSW		ISSN: 2070-1721 SSW
	S. Jiang		S. Jiang
	BUPT		BUPT
	T. Winters		T. Winters
	QA Cafe		QA Cafe
	December 2025		December 2025
	Dynamic Host Configuration Protocol for IPv6 (DHCPv6)		Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
	Abstract		Abstract
	skipping to change at line 3179 ¶		skipping to change at line 3179 ¶
	described in Section 18.2.5, with the exception that the		described in Section 18.2.5, with the exception that the
	retransmission parameters should be set as for the Confirm message		retransmission parameters should be set as for the Confirm message
	(see Section 18.2.3). The client includes IA_NAs and IA_PDs, along		(see Section 18.2.3). The client includes IA_NAs and IA_PDs, along
	with the associated leases, in its Rebind message.		with the associated leases, in its Rebind message.
	If the client has only obtained network information using		If the client has only obtained network information using
	Information-request/Reply message exchanges, the client MUST initiate		Information-request/Reply message exchanges, the client MUST initiate
	an Information-request/Reply message exchange as described in		an Information-request/Reply message exchange as described in
	Section 18.2.6.		Section 18.2.6.
	A client not detected as having moved to a new link SHOULD initiate		If the client has not detected having moved to a new link but has
	one of the Renew/Reply, Confirm/Reply or Information-request/Reply		detected a significant change regarding the prefixes available on the
	exchanges, if the client detects a significant change regarding the		link, the client SHOULD initiate one of the Renew/Reply, Confirm/
	prefixes available on the link. A change is considered significant		Reply, or Information-request/Reply exchanges. A change is
	when one or more on-link prefixes are added, and/or one or more		considered significant when one or more on-link prefixes are added
	existing on-link prefixes are deprecated. The reason for this is		and/or one or more existing on-link prefixes are deprecated. The
	that such a significant change may indicate a configuration change at		reason for this is that such a significant change may indicate a
	the server. However, a client MUST rate-limit such initiation		configuration change at the server. However, a client MUST rate-
	attempts to avoid flooding a server with requests when there are link		limit such initiation attempts to avoid flooding a server with
	issues (for example, only doing one of these at most every 30		requests when there are link issues (for example, only doing one of
	seconds).		these at most every 30 seconds).
	The above selection of an exchange to initiate depends on the		The above selection of an exchange to initiate depends on the
	client's current state:		client's current state:
	* If the client has any valid delegated prefixes obtained from the		* If the client has any valid delegated prefixes obtained from the
	server, it sends Renew (as if the T1 time expired) as described in		server, it sends Renew (as if the T1 time expired) as described in
	Section 18.2.4.		Section 18.2.4.
	* Else, if the client obtained an address(es) from the server, it		* Else, if the client obtained an address(es) from the server, it
	sends Confirm as described in Section 18.2.3.		sends Confirm as described in Section 18.2.3.
	skipping to change at line 5294 ¶		skipping to change at line 5294 ¶
	MUST follow the rules defined in Section 14.2.		MUST follow the rules defined in Section 14.2.
	If a client receives an IA_PD with T1 greater than T2 and both T1 and		If a client receives an IA_PD with T1 greater than T2 and both T1 and
	T2 are greater than 0, the client discards the IA_PD option and		T2 are greater than 0, the client discards the IA_PD option and
	processes the remainder of the message as though the server had not		processes the remainder of the message as though the server had not
	included the IA_PD option.		included the IA_PD option.
	21.22. IA Prefix Option		21.22. IA Prefix Option
	The IA Prefix option is used to specify a prefix associated with an		The IA Prefix option is used to specify a prefix associated with an
	IA_PD. The IA Prefix option must be encapsulated in the IA_PD-		IA_PD. The IA Prefix option must be encapsulated in the
	options field of an IA_PD option (see Section 21.21).		IA_PD-options field of an IA_PD option (see Section 21.21).
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OPTION_IAPREFIX | option-len |		| OPTION_IAPREFIX | option-len |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| preferred-lifetime |		| preferred-lifetime |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| valid-lifetime |		| valid-lifetime |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
End of changes. 3 change blocks.
	17 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.48.