rfc9914v13.txt		rfc9914.txt
	skipping to change at line 2885 ¶		skipping to change at line 2885 ¶
	indicated in the Target Options. The segment is to be included in a		indicated in the Target Options. The segment is to be included in a
	DODAG indicated by the P-DAO Base Object, which may be the one formed		DODAG indicated by the P-DAO Base Object, which may be the one formed
	by the main DODAG, or a Track associated with a Local RPL Instance.		by the main DODAG, or a Track associated with a Local RPL Instance.
	------+---------		------+---------
	| Internet		| Internet
	|		|
	+-----+		+-----+
	| | Border Router		| | Border Router
	| | (RPL Root)		| | (RPL Root)
	+-----+ | ^ |		+-----+ | P- ^ |
	| | DAO | ACK |		| | DAO | P-DAO-ACK |
	o o o o | | |		o o o o | | |
	o o o o Ingress o o o | ^ | Projected .		o o o o Ingress o o o | ^ | Projected .
	o o o o o \\ o o o | | DAO | Route .		o o o o o \\ o o o | | P-DAO | Route .
	o o o o \\ o o o o | ^ | .		o o o o \\ o o o o | ^ | .
	o o o o o Egress o o v | DAO v .		o o o o o Egress o o v | P-DAO v .
	o o LLN o o o |		o o LLN o o o |
	o o o o o Loose Source Route Path |		o o o o o Loose Source Route Path |
	o o o o v		o o o o v
	Figure 18: Projecting a Route		Figure 18: Projecting a Route
	In order to install the relevant routing state along the segment, the		In order to install the relevant routing state along the segment, the
	Root sends a unicast P-DAO message to the Track egress router of the		Root sends a unicast P-DAO message to the Track egress router of the
	routing segment that is being installed. The P-DAO message contains		routing segment that is being installed. The P-DAO message contains
	an SM-VIO with a strict sequence of Via Addresses. The SM-VIO		an SM-VIO with a strict sequence of Via Addresses. The SM-VIO
	skipping to change at line 2973 ¶		skipping to change at line 2973 ¶
	order. The content of the NSM-VIO starting at the first SRH-6LoRH		order. The content of the NSM-VIO starting at the first SRH-6LoRH
	header MUST be used verbatim by the Track ingress when it		header MUST be used verbatim by the Track ingress when it
	encapsulates a packet to forward it over the Track.		encapsulates a packet to forward it over the Track.
	------+---------		------+---------
	| Internet		| Internet
	|		|
	+-----+		+-----+
	| | Border Router		| | Border Router
	| | (RPL Root)		| | (RPL Root)
	+-----+ | P ^ ACK		+-----+ | P- ^ P-DAO-ACK
	| Track | DAO |		| Track | DAO |
	o o o o Ingress X V | X		o o o Ingress V |
	o o o o o o o X o X Source-		o o o o o o X o X Source-
	o o o o o o o o X o o X Routed		o o o o o o o X o o X Routed
	o o o o o o o X o X Segment		o o o o o o X o X Segment
	o o o o o o o o X Egress X		o o o o o o o o X X
	o o o o o |		Egress
	o o o Target		o o o o o |
	o o LLN o o		Target
			o o LLN o
	o o o o		o o o o
	Figure 19: Projecting a Non-Storing Route		Figure 19: Projecting a Non-Storing Route
	The next entry in the source-routed path must be either a neighbor of		The next entry in the source-routed path must be either a neighbor of
	the previous entry or reachable as a Target via another P-Route,		the previous entry or reachable as a Target via another P-Route,
	either Storing or Non-Storing, which implies that the nested P-Route		either Storing or Non-Storing, which implies that the nested P-Route
	has to be installed before the loose sequence is and that P-Routes		has to be installed before the loose sequence is and that P-Routes
	must be installed from the last to the first along the datapath. For		must be installed from the last to the first along the datapath. For
	instance, a segment of a Track must be installed before the		instance, a segment of a Track must be installed before the
	skipping to change at line 3800 ¶		skipping to change at line 3801 ¶
	+------------+----------------------------------------+-----------+		+------------+----------------------------------------+-----------+
	| 1 | Requested path should be redundant (R) | RFC 9914 |		| 1 | Requested path should be redundant (R) | RFC 9914 |
	+------------+----------------------------------------+-----------+		+------------+----------------------------------------+-----------+
	| 2..255 | Unassigned | |		| 2..255 | Unassigned | |
	+------------+----------------------------------------+-----------+		+------------+----------------------------------------+-----------+
	Table 27: Initial P-DAO-REQ Flags		Table 27: Initial P-DAO-REQ Flags
	11.8. Registry for Projected DAO Request Acknowledgment (PDR-ACK) Flags		11.8. Registry for Projected DAO Request Acknowledgment (PDR-ACK) Flags
	IANA has created the "PDR-ACK Flags" registry under the "Routing		IANA has created the "Projected DAO Request Acknowledgment (PDR-ACK)
	Protocol for Low Power and Lossy Networks (RPL)" registry group		Flags" registry under the "Routing Protocol for Low Power and Lossy
	[IANA-RPL]. The bits are indexed from 0 (leftmost) to 7. Each bit		Networks (RPL)" registry group [IANA-RPL]. The bits are indexed from
	is tracked with the following qualities:		0 (leftmost) to 7. Each bit is tracked with the following qualities:
	* Bit number (counting from bit 0 as the most significant bit)		* Bit number (counting from bit 0 as the most significant bit)
	* Capability description		* Capability description
	* Reference		* Reference
	The registration procedure is Standards Action [RFC8126]. At the		The registration procedure is Standards Action [RFC8126]. At the
	time of publication of this document, no bit has been assigned in		time of publication of this document, no bit has been assigned in
	this registry.		this registry.
End of changes. 6 change blocks.
	17 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.48.