[Idr] [Errata Verified] RFC9085 (7736)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 16 January 2024 18:09 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD64C14F70F; Tue, 16 Jan 2024 10:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 rIzb-LHgoxGQ; Tue, 16 Jan 2024 10:09:53 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 BAA78C14F711; Tue, 16 Jan 2024 10:09:53 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 91A391A49953; Tue, 16 Jan 2024 10:09:53 -0800 (PST)
To: ketant.ietf@gmail.com, stefano@previdi.net, ketant@cisco.com, cfilsfil@cisco.com, hannes@rtbrick.com, mach.chen@huawei.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jgs@juniper.net, iesg@ietf.org, idr@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240116180953.91A391A49953@rfcpa.amsl.com>
Date: Tue, 16 Jan 2024 10:09:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4n-zcrT6crNyk308NWL0NwsKYZE>
X-Mailman-Approved-At: Tue, 16 Jan 2024 10:22:55 -0800
Subject: [Idr] [Errata Verified] RFC9085 (7736)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 18:09:57 -0000

The following errata report has been verified for RFC9085,
"Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7736

--------------------------------------
Status: Verified
Type: Technical

Reported by: Ketan Talaulikar <ketant.ietf@gmail.com>
Date Reported: 2023-12-20
Verified by: John Scudder (IESG)

Section: 2.3.5

Original Text
-------------
   A Prefix NLRI, that has been advertised with a Range TLV, is
   considered a normal routing prefix (i.e., prefix reachability) only
   when there is also an IGP metric TLV (TLV 1095) associated it.
   Otherwise, it is considered only as the first prefix in the range for
   prefix-to-SID mapping advertisement.

Corrected Text
--------------
   A Prefix NLRI, that has been advertised with a Range TLV, is
   considered a normal routing prefix (i.e., prefix reachability) only
   when there is also a Prefix Metric TLV (TLV 1155) associated with it.
   Otherwise, it is considered only as the first prefix in the range for
   prefix-to-SID mapping advertisement.

Notes
-----
The current text is referring to the wrong BGP-LS TLV. Since the Range TLV is associated with a Prefix NLRI, the "Prefix Metric TLV (TLV 1155)" should be referenced here since the "IGP metric TLV (TLV 1095)" is associated with a Link NLRI.

Verifier note: in addition to the fix proposed by Ketan, I added a preposition: "associated with it", and corrected an indefinite article: "a Prefix".

--------------------------------------
RFC9085 (draft-ietf-idr-bgp-ls-segment-routing-ext-18)
--------------------------------------
Title               : Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing
Publication Date    : August 2021
Author(s)           : S. Previdi, K. Talaulikar, Ed., C. Filsfils, H. Gredler, M. Chen
Category            : PROPOSED STANDARD
Source              : Inter-Domain Routing
Area                : Routing
Stream              : IETF
Verifying Party     : IESG