rfc9914v6.txt		rfc9914.txt
	skipping to change at line 1898 ¶		skipping to change at line 1898 ¶
	Track ingress; the P-DAO message contains a new VIO that installs a		Track ingress; the P-DAO message contains a new VIO that installs a
	strict or a loose sequence of hops to form a Track segment or a		strict or a loose sequence of hops to form a Track segment or a
	protection path, respectively.		protection path, respectively.
	The Projected DAO Request (P-DAO-REQ) is a new message detailed in		The Projected DAO Request (P-DAO-REQ) is a new message detailed in
	Section 5.1. As per Section 6 of [RPL], if a node receives this		Section 5.1. As per Section 6 of [RPL], if a node receives this
	message and it does not understand this new code, it discards the		message and it does not understand this new code, it discards the
	message. When the Root initiates communication to a node that it has		message. When the Root initiates communication to a node that it has
	not communicated with before and that it has not ascertained to		not communicated with before and that it has not ascertained to
	implement this specification (by means such as capabilities), then		implement this specification (by means such as capabilities), then
	the Root SHOULD request a P-DAO Request Acknowledgment (PDR-ACK).		the Root SHOULD request a Projected DAO Request Acknowledgment (PDR-
			ACK).
	A P-DAO-REQ message enables a Track ingress to request the Track from		A P-DAO-REQ message enables a Track ingress to request the Track from
	the Root. The resulting Track is also a DODAG for which the Track		the Root. The resulting Track is also a DODAG for which the Track
	ingress is the Root, and the owner is the address that serves as the		ingress is the Root, and the owner is the address that serves as the
	DODAGID and is authoritative for the associated namespace from which		DODAGID and is authoritative for the associated namespace from which
	the TrackID is selected. In the context of this specification, the		the TrackID is selected. In the context of this specification, the
	installed route appears as a more-specific route to the Track		installed route appears as a more-specific route to the Track
	Targets, and the Track ingress forwards the packets toward the		Targets, and the Track ingress forwards the packets toward the
	Targets via the Track using normal longest match IP forwarding.		Targets via the Track using normal longest match IP forwarding.
	skipping to change at line 3737 ¶		skipping to change at line 3738 ¶
	+------------+----------------------+-----------+		+------------+----------------------+-----------+
	Table 24: Initial P-DAO-REQ Flags		Table 24: Initial P-DAO-REQ Flags
	11.5. RPL Control Codes		11.5. RPL Control Codes
	IANA has updated the "RPL Control Codes" registry under the "Routing		IANA has updated the "RPL Control Codes" registry under the "Routing
	Protocol for Low Power and Lossy Networks (RPL)" registry group		Protocol for Low Power and Lossy Networks (RPL)" registry group
	[IANA-RPL] as indicated in Table 25:		[IANA-RPL] as indicated in Table 25:
	+======+========================================+===========+		+======+================================================+===========+
	| Code | Description | Reference |		| Code | Description | Reference |
	+======+========================================+===========+		+======+================================================+===========+
	| 0x09 | Projected DAO Request (P-DAO-REQ) | RFC 9914 |		| 0x09 | Projected DAO Request (P-DAO-REQ) | RFC 9914 |
	+------+----------------------------------------+-----------+		+------+------------------------------------------------+-----------+
	| 0x0A | P-DAO Request Acknowledgment (PDR-ACK) | RFC 9914 |		| 0x0A | Projected DAO Request | RFC 9914 |
	+------+----------------------------------------+-----------+		| | Acknowledgment (PDR-ACK) | |
			+------+------------------------------------------------+-----------+
	Table 25: New RPL Control Codes		Table 25: New RPL Control Codes
	11.6. RPL Control Message Options		11.6. RPL Control Message Options
	IANA has updated the "RPL Control Message Options" registry under the		IANA has updated the "RPL Control Message Options" registry under the
	"Routing Protocol for Low Power and Lossy Networks (RPL)" registry		"Routing Protocol for Low Power and Lossy Networks (RPL)" registry
	group [IANA-RPL] as indicated in Table 26:		group [IANA-RPL] as indicated in Table 26:
	+=======+==============================================+===========+		+=======+==============================================+===========+
	skipping to change at line 3935 ¶		skipping to change at line 3937 ¶
	(DAO) Flag		(DAO) Flag
	11.14. Destination Advertisement Object Acknowledgment Flag		11.14. Destination Advertisement Object Acknowledgment Flag
	IANA has updated the "Destination Advertisement Object (DAO)		IANA has updated the "Destination Advertisement Object (DAO)
	Acknowledgment Flags" registry, created in Section 20.12 of [RPL],		Acknowledgment Flags" registry, created in Section 20.12 of [RPL],
	under the "Routing Protocol for Low Power and Lossy Networks (RPL)"		under the "Routing Protocol for Low Power and Lossy Networks (RPL)"
	registry group [IANA-RPL] as indicated in Table 32 (see more in		registry group [IANA-RPL] as indicated in Table 32 (see more in
	Section 4.1.2):		Section 4.1.2):
	+============+========================+===========+		+============+==================================+===========+
	| Bit Number | Capability Description | Reference |		| Bit Number | Capability Description | Reference |
	+============+========================+===========+		+============+==================================+===========+
	| 1 | Projected DAO-ACK (P) | RFC 9914 |		| 1 | Projected DAO Acknowledgment (P) | RFC 9914 |
	+------------+------------------------+-----------+		+------------+----------------------------------+-----------+
	Table 32: New Destination Advertisement Object		Table 32: New Destination Advertisement Object
	Acknowledgment Flag		Acknowledgment Flag
	11.15. ICMPv6 Error Code		11.15. ICMPv6 Error Code
	In some cases, RPL will return an ICMPv6 error message when a message		In some cases, RPL will return an ICMPv6 error message when a message
	cannot be forwarded along a P-Route.		cannot be forwarded along a P-Route.
	Per this specification, IANA has updated the "Type 1 - Destination		Per this specification, IANA has updated the "Type 1 - Destination
End of changes. 3 change blocks.
	13 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.48.