[babel] [Errata Held for Document Update] RFC8966 (7373)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 30 October 2024 14:10 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAB11C14F615; Wed, 30 Oct 2024 07:10:47 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 1F6547F9E0; Wed, 30 Oct 2024 07:10:47 -0700 (PDT)
To: dxld@darkboxed.org, jch@irif.fr, dschinazi.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20241030141047.1F6547F9E0@rfcpa.rfc-editor.org>
Date: Wed, 30 Oct 2024 07:10:47 -0700
Message-ID-Hash: X5PIOLRZTZGSBXAVEUSBZTNMJE2BCUHH
X-Message-ID-Hash: X5PIOLRZTZGSBXAVEUSBZTNMJE2BCUHH
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-babel.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: gunter.van_de_velde@nokia.com, iesg@ietf.org, babel@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [babel] [Errata Held for Document Update] RFC8966 (7373)
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/dN4dDAI1LOBjD6islYVI7l8J7ns>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Owner: <mailto:babel-owner@ietf.org>
List-Post: <mailto:babel@ietf.org>
List-Subscribe: <mailto:babel-join@ietf.org>
List-Unsubscribe: <mailto:babel-leave@ietf.org>
The following errata report has been held for document update for RFC8966, "The Babel Routing Protocol". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7373 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Daniel Gröber <dxld@darkboxed.org> Date Reported: 2023-02-27 Held by: Gunter Van de Velde (IESG) Section: 3.8.2.2. Original Text ------------- Additionally, since metric computation does not necessarily coincide with the delay in propagating updates, a node might receive an unfeasible update from a currently unselected neighbour that is preferable to the currently selected route (e.g., because it has a much smaller metric); in that case, the node SHOULD send a unicast seqno request to the neighbour that advertised the preferable update. Corrected Text -------------- Additionally, since metric computation does not necessarily coincide with the delay in propagating updates, a node might receive an unfeasible update from a currently unselected neighbour that would lead to the received route becoming selected were it feasible. In that case, the node SHOULD send a unicast seqno request to the neighbour that advertised the preferable update. Notes ----- As currently written the text does not recommend sending a seqno request when no route is currently selected because ".. that is preferable to the currently selected route" implies a selected route as a precondition. We recommend reinstating some of the RFC6126 wording instead. (Thanks to Juliusz for pointing this out) -------------------------------------- RFC8966 (draft-ietf-babel-rfc6126bis-20) -------------------------------------- Title : The Babel Routing Protocol Publication Date : January 2021 Author(s) : J. Chroboczek, D. Schinazi Category : PROPOSED STANDARD Source : Babel routing protocol Stream : IETF Verifying Party : IESG
- [babel] [Errata Held for Document Update] RFC8966… RFC Errata System