Re: [Roll] [Technical Errata Reported] RFC9008 (7543)

[John Scudder <[e-mail]>]

Hi Authors, ROLL,

This erratum looks right to me and I’m disposed to verify it. I’d appreciate a sanity check, though.

Thanks,

—John

> On Jun 14, 2023, at 6:05 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC9008,
> "Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane".
> 
> --------------------------------------
> You may review the report below and at:
> https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid7543__;!!NEt6yMaO-gk!HaOdTzpY2o3VMwozwgAetX2WqGzJPOqoz4GYCzJt5pS8SC7xmoJ1TOPXfHFYV8mGrQw7g28phjvBY-yp2cdf4w$
> 
> --------------------------------------
> Type: Technical
> Reported by: Mathis Marion <[e-mail]>
> 
> Section: 6
> 
> Original Text
> -------------
> 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.
> 
> Corrected Text
> --------------
> 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.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC9008 (draft-ietf-roll-useofrplinfo-44)
> --------------------------------------
> Title               : Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane
> Publication Date    : April 2021
> Author(s)           : M.I. Robles, M. Richardson, P. Thubert
> Category            : PROPOSED STANDARD
> Source              : Routing Over Low power and Lossy networks
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG