rfc9914v10.txt		rfc9914.txt
	skipping to change at line 2312 ¶		skipping to change at line 2312 ¶
	subset of the other Targets; the details of the subset selection are		subset of the other Targets; the details of the subset selection are
	out of scope. The RTO signals the Track egress (see more in		out of scope. The RTO signals the Track egress (see more in
	Section 6.2).		Section 6.2).
	The RPL Control Code for the P-DAO-REQ is 0x09. The format of the P-		The RPL Control Code for the P-DAO-REQ is 0x09. The format of the P-
	DAO-REQ Base Object is as follows:		DAO-REQ Base Object is as follows:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| TrackID |K|R| Flags | ReqLifetime |PDAOReqSequence|		| TrackID |K|R| Flags | ReqLifetime | PDRSequence |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Option(s)...		| Option(s)...
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	Figure 13: New P-DAO Request Format		Figure 13: New P-DAO Request Format
	TrackID: 8-bit field. In the context of this specification, the		TrackID: 8-bit field. In the context of this specification, the
	TrackID field signals the RPLInstanceID of the DODAG formed by the		TrackID field signals the RPLInstanceID of the DODAG formed by the
	Track; see Sections 3.4 and 6.3. To allocate a new Track, the		Track; see Sections 3.4 and 6.3. To allocate a new Track, the
	ingress Node must provide a value that is not in use at this time.		ingress Node must provide a value that is not in use at this time.
	skipping to change at line 2337 ¶		skipping to change at line 2337 ¶
	R: The 'R' flag is set to request a Complex Track for redundancy.		R: The 'R' flag is set to request a Complex Track for redundancy.
	Flags: Reserved. The Flags field MUST be initialized to zero by the		Flags: Reserved. The Flags field MUST be initialized to zero by the
	sender and MUST be ignored by the receiver.		sender and MUST be ignored by the receiver.
	ReqLifetime: 8-bit unsigned integer. The requested lifetime for the		ReqLifetime: 8-bit unsigned integer. The requested lifetime for the
	Track expressed in Lifetime Units (obtained from the DODAG		Track expressed in Lifetime Units (obtained from the DODAG
	Configuration option). The value of 255 (0xFF) represents		Configuration option). The value of 255 (0xFF) represents
	infinity (never time out).		infinity (never time out).
	A P-DAO-REQ with a fresher PDAOReqSequence refreshes the lifetime,		A P-DAO-REQ with a fresher PDRSequence refreshes the lifetime, and
	and a ReqLifetime of 0 indicates that the Track MUST be destroyed,		a ReqLifetime of 0 indicates that the Track MUST be destroyed,
	e.g., when the application that requested the Track terminates.		e.g., when the application that requested the Track terminates.
	PDAOReqSequence: 8-bit wrapping sequence number, obeying the		PDRSequence: 8-bit wrapping sequence number, obeying the operation
	operation in Section 7.2 of [RPL]. The PDAOReqSequence is used to		in Section 7.2 of [RPL]. The PDRSequence is used to correlate a
	correlate a PDR-ACK message with the P-DAO-REQ message that		PDR-ACK message with the P-DAO-REQ message that triggered it. It
	triggered it. It is incremented at each P-DAO-REQ message and		is incremented at each P-DAO-REQ message and echoed in the PDR-ACK
	echoed in the PDR-ACK by the Root.		by the Root.
	5.2. New PDR-ACK Control Message		5.2. New PDR-ACK Control Message
	The new PDR-ACK is sent as a response to a P-DAO-REQ message with the		The new PDR-ACK is sent as a response to a P-DAO-REQ message with the
	'K' flag set. The RPL Control Code for the PDR-ACK is 0x0A. Its		'K' flag set. The RPL Control Code for the PDR-ACK is 0x0A. Its
	format is as follows:		format is as follows:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| TrackID | Flags | Track Lifetime|PDAOReqSequence|		| TrackID | Flags | Track Lifetime| PDRSequence |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| PDR-ACK Status| Reserved |		| PDR-ACK Status| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Option(s)...		| Option(s)...
	+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+
	Figure 14: New PDR-ACK Control Message Format		Figure 14: New PDR-ACK Control Message Format
	TrackID: Set to the TrackID indicated in the TrackID field of the P-		TrackID: Set to the TrackID indicated in the TrackID field of the P-
	DAO-REQ messages that this replies to.		DAO-REQ messages that this replies to.
	Flags: Reserved. The Flags field MUST be initialized to zero by the		Flags: Reserved. The Flags field MUST be initialized to zero by the
	sender and MUST be ignored by the receiver.		sender and MUST be ignored by the receiver.
	Track Lifetime: Indicates the remaining lifetime for the Track,		Track Lifetime: Indicates the remaining lifetime for the Track,
	expressed in Lifetime Units. The value of 255 (0xFF) represents		expressed in Lifetime Units. The value of 255 (0xFF) represents
	infinity. The value of zero (0x00) indicates that the Track was		infinity. The value of zero (0x00) indicates that the Track was
	destroyed or not created.		destroyed or not created.
	PDAOReqSequence: 8-bit wrapping sequence number. It is incremented		PDRSequence: 8-bit wrapping sequence number. It is incremented at
	at each P-DAO-REQ message and echoed in the PDR-ACK.		each P-DAO-REQ message and echoed in the PDR-ACK.
	PDR-ACK Status: 8-bit field indicating the completion. The PDR-ACK		PDR-ACK Status: 8-bit field indicating the completion. The PDR-ACK
	Status is substructured as indicated in Figure 15:		Status is substructured as indicated in Figure 15:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	|E|R| Value |		|E|R| Value |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	Figure 15: PDR-ACK Status Format		Figure 15: PDR-ACK Status Format
End of changes. 5 change blocks.
	11 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.48.