IETF Logo Mail Archive

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

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 14 June 2023 10:05 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20490C14CF1B for <roll@ietfa.amsl.com>; Wed, 14 Jun 2023 03:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHOLOV2T7WXT for <roll@ietfa.amsl.com>; Wed, 14 Jun 2023 03:05:34 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3842DC14CE24 for <roll@ietf.org>; Wed, 14 Jun 2023 03:05:34 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0BA8955EB3; Wed, 14 Jun 2023 03:05:34 -0700 (PDT)
To: mariainesrobles@gmail.com, mcr+ietf@sandelman.ca, pthubert@cisco.com, aretana.ietf@gmail.com, jgs@juniper.net, andrew-ietf@liquid.tech, mariainesrobles@googlemail.com, dominique.barthel@orange.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mathis.marion@silabs.com, roll@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230614100534.0BA8955EB3@rfcpa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/yyoQStPVhlW03zc6BwfNKb7QBxg>
X-Mailman-Approved-At: Mon, 17 Jul 2023 08:13:09 -0700
Subject: [Roll] [Technical Errata Reported] RFC9008 (7543)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
Date: Wed, 14 Jun 2023 10:05:38 -0000
X-Original-Date: Wed, 14 Jun 2023 03:05:34 -0700 (PDT)
X-List-Received-Date: Wed, 14 Jun 2023 10:05:38 -0000

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://www.rfc-editor.org/errata/eid7543

--------------------------------------
Type: Technical
Reported by: Mathis Marion <mathis.marion@silabs.com>

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

v2.23.0 | Report a Bug | By Email