RFC Errata
Found 2 records.
Status: Verified (2)
RFC 9008, "Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane", April 2021
Source of RFC: roll (rtg)
Errata ID: 7543
Status: Verified
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Mathis Marion
Date Reported: 2023-06-14
Verifier Name: John Scudder
Date Verified: 2024-01-12
Section 6 says:
As the Rank information in the RPI artifact is changed at each hop, it will typically be zero when it arrives at the DODAG root.
It should say:
As the Rank information in the RPI artifact is changed at each hop, it will typically be non-zero when it arrives at the DODAG root.
Notes:
The SenderRank is 0 if:
- The packet comes from Internet (and has an RPI)
- The packet has not been forwarded (ie. if the source is a direct child of the DODAG root), as RFC 6550 section 11.2 tells to set SenderRank to 0 at the source.
The typical case is rather a packet that arrives at the DODAG root from a child node forwarding a packet, in which case SenderRank is set to DAGRank(rank) > 0.
Errata ID: 6557
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Pascal Thubert
Date Reported: 2021-04-23
Verifier Name: Alvaro Retana
Date Verified: 2021-04-23
Section 11.1 says:
DODAG Configuration Option Flag to Indicate the RPI Flag Day
It should say:
DODAG Configuration Option Flag to Set the Value of the RPI Option Type
Notes:
The point of the new flag is to avoid a flag day.
This text is as the name for Tables 1 and 26 on sections 4.1.3 and 11.1, respectively.