[Idr] [Errata Verified] RFC9857 (8709)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 27 January 2026 15:24 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@mail2.ietf.org
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 mail2.ietf.org (Postfix) with ESMTPS id E9B7EADC2C19; Tue, 27 Jan 2026 07:24:47 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id CD1C6C000CE0; Tue, 27 Jan 2026 07:24:47 -0800 (PST)
To: min0921110@gmail.com, stefano@previdi.net, ketant.ietf@gmail.com, jie.dong@huawei.com, hannes@rtbrick.com, jefftant.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260127152447.CD1C6C000CE0@rfcpa.rfc-editor.org>
Date: Tue, 27 Jan 2026 07:24:47 -0800
Message-ID-Hash: 6WVNNNHNEULO7W5A6I66NNZXKOZVYNTU
X-Message-ID-Hash: 6WVNNNHNEULO7W5A6I66NNZXKOZVYNTU
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: iesg@ietf.org, idr@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] [Errata Verified] RFC9857 (8709)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/PptIfIEgfX8MKmRDwLwDmTLnSpE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

The following errata report has been verified for RFC9857,
"Advertisement of Segment Routing Policies Using BGP - Link State". 

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

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Hyeonmin Lee <min0921110@gmail.com>
Date Reported: 2026-01-19
Verified by: Ketan Talaulikar (IESG)

Section: 5.1

Original Text
-------------
   In the case of an SRv6, the SR Binding SID sub-TLV does not have the
   ability to signal the SRv6 Endpoint behavior [RFC8986] or the
   structure of the SID.  Therefore, the SR Binding SID sub-TLV SHOULD
   NOT be used for the advertisement of an SRv6 Binding SID.  Instead,
   the SRv6 Binding SID TLV defined in Section 5.2 SHOULD be used for
   the signaling of an SRv6 Binding SID.  The use of the SR Binding SID
   sub-TLV for advertisement of the SRv6 Binding SID has been
   deprecated, and it is documented here only for backward compatibility
   with implementations that followed early draft versions of this
   specification.

Corrected Text
--------------
   In the case of an SRv6, the SR Binding SID TLV does not have the
   ability to signal the SRv6 Endpoint behavior [RFC8986] or the
   structure of the SID.  Therefore, the SR Binding SID TLV SHOULD
   NOT be used for the advertisement of an SRv6 Binding SID.  Instead,
   the SRv6 Binding SID TLV defined in Section 5.2 SHOULD be used for
   the signaling of an SRv6 Binding SID.  The use of the SR Binding SID
   TLV for advertisement of the SRv6 Binding SID has been
   deprecated, and it is documented here only for backward compatibility
   with implementations that followed early draft versions of this
   specification.

Notes
-----
The incorrect term `SR Binding SID sub-TLV' appears three times in the last paragraph of Section 5.1. The correct term is `SR Binding SID TLV'.

--------------------------------------
RFC9857 (draft-ietf-idr-bgp-ls-sr-policy-17)
--------------------------------------
Title               : Advertisement of Segment Routing Policies Using BGP - Link State
Publication Date    : October 2025
Author(s)           : S. Previdi, K. Talaulikar, Ed., J. Dong, H. Gredler, J. Tantsura
Category            : PROPOSED STANDARD
Source              : Inter-Domain Routing
Stream              : IETF
Verifying Party     : IESG