[Lsr] Re: [Technical Errata Reported] RFC9983 (9311)
Acee Lindem <acee.ietf@gmail.com> Tue, 17 November 2026 01:55 UTC
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id F2E1846 for <lsr@ietf.org>; Tue, 17 Nov 2026 01:55:45 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20260707 header.b="SZ1Bx5a/"; spf=pass (mx.ietf.org: domain of acee.ietf@gmail.com designates 2607:f8b0:4864:20::732 as permitted sender) smtp.mailfrom=acee.ietf@gmail.com; dmarc=pass (policy=none) header.from=gmail.com
Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-9495f083657so396010685a.0 for <lsr@ietf.org>; Mon, 16 Nov 2026 17:55:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20260707; t=1794880539; x=1795485339; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:content-type:from:to:cc :subject:date:message-id:reply-to:content-type; bh=2dZcWkaCCoW/2woOoHWqWBRCAvtOveYSJnhA9ThGq2s=; b=SZ1Bx5a/CyqZxBkKsxQmHFl3pGmMGMQGxtUV/DXv0d5bhFDSmLKbSaE/ilvLX6L/PT +HE/fcxFt+pPo3Zfblr9i22us6GhGj1qQWKIvqrEaFeB3Uiuz/pfbyJ2c4dxhC222wIb oDwKwYhueKMeR5KQUCN62/aK5T0HUtsK40BCQwLHIWSTwFayYrIRH+rdTdthHkxGJ1iJ F5JYb/WFEI/0itylH4orfrz8pp0xKwGg07T3hATUm6PJcWmbXU1/69LD6/sZrm9FsGp0 KEzlIbrvgDqjxBSs6Te7m59Zx2Is58PbazWNnSxXxeZ35J4Q4wEYuMCT7q84FHvM9WKe zK4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1794880539; x=1795485339; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:content-type:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=2dZcWkaCCoW/2woOoHWqWBRCAvtOveYSJnhA9ThGq2s=; b=b204aXCjf0J9F2FOwRVkEzVxeYVjice/oPsDiwT2ihxepc0fBXQGbVJwkgY4vVV82V 7bqeGXQ4X/ByXOjYunMLxDKIctZHAHgPfzX+N7rKLzzR3mrBDD8l5oYqEjgL2NTw60GO iuPcg1UULwTQoIk10UhMrCZEVlu2g96zgQhiBtA+92r8Qcl4UhSVNJEw+mz7xj6p+7nL eaH0AvPxSMepZJjKchXFoAsGCvadM1JNmXayt0oflU6Bo+xaPDxT8Y99qZ2mIxvAhUdn nEN4CgNHzwfZajHqDl55KzzlpSbUbobMTLWqRL2TSQvfx246SSctUZKnyfGHxwHrI95m +o8A==
X-Forwarded-Encrypted: i=1; AL+hErFYl05w05LZTa3MoOWfodHhgN/DRAoDUlOWldtx1N0qkzaMURwBmPe379h4rqsI+S/twFY=@ietf.org
X-Gm-Message-State: APuU4Z+OV/pQ8jBLZn/FfwU4lijhQURSFOM1EDrIvs8m0Wg0eMItBSkm FSoYn556Z6X3XIkeyj1039AVHUdno46BekWvyMK2Jyb3kvLqXMKAp4Lt
X-Gm-Gg: AYBFou1a7a2VWUUF6dl7SIaDiIZpbmzrevF4Skuf932c+2eThRa5ovn32gGQ1Vo7iHU s0lNgtvEHuV+XpDPUTZU+68thGy7DgYoMHieoRw27s/LwS2HYnuGbS9HLybOrHFm1XeF9gDFPwR EV+r4F524lWS4G2ddiLuXKiWi7+L5iW17hur/NOscCMD75ghzjilKfiTGibFVXuFXZ+yhw5v43N saFT1L6vxJkqyIS00dfdA8f/GFBjGBH0Y+1p9aTOrR5nx3/D3SEwqgft5Kg53vZ/M6M+LXj+F+t 4R+YpS+bXMU++9AqWfRQA3AlgZdLKdyBnaNwxphOJlzrOfB0VABVoyQltRHtSYMFGhEWSIljEJ0 35rMehR0eRzkhdH2cPXdmd/I4cCrAp5bIGEZ4P8C13j8NfBHCqx/yE4MyJzh2XBjyCKa/aL1jTk PAAbAtjYAvA/JtZdjlwylCdBPM59s9P0RFiVJN+IS5NcXd8SxNyANz6KcrbbhMyxT41vA5BGlWO CRT5LVLzb3sWr0iF+L4apoca8S8KZouVBJYtUHYm43y9BYvasXpOB7MVFde0QpL6tAFs03qUvLf JsH3oro7R6sxEx65EIlP6+L4F/W1p3s83OCmEvnCxBtMRpNlQlmOLRouq4XR
X-Received: by 2002:a05:620a:29d4:b0:949:70ec:7e98 with SMTP id af79cd13be357-94970ec8d8cmr1241330985a.40.1794880539315; Mon, 16 Nov 2026 17:55:39 -0800 (PST)
Received: from smtpclient.apple ([2605:a601:a6e6:6300:70ae:7559:a55:eefc]) by smtp.gmail.com with ESMTPSA id af79cd13be357-9494c8e1c94sm979538185a.39.2026.11.16.17.55.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Nov 2026 17:55:38 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.200.71.1.16\))
From: Acee Lindem <acee.ietf@gmail.com>
In-Reply-To: <CAChaegmOxq96y39GW93KoJJW7Q5pBxbG6O7wEWmdwrS89kAmJw@mail.gmail.com>
Date: Mon, 16 Nov 2026 20:55:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCC96E5B-3711-4179-B360-C8ED9A26A070@gmail.com>
References: <179485447767.17.15520869052470635043@rfc-editor.org> <CAChaegmOxq96y39GW93KoJJW7Q5pBxbG6O7wEWmdwrS89kAmJw@mail.gmail.com>
To: Renato Westphal <renatowestphal@gmail.com>
X-Mailer: Apple Mail (2.3901.200.71.1.16)
X-Spamd-Bar: -----------
Message-ID-Hash: CWWQJSNF6RA56OLOD2BG4LRCW234JDHW
X-Message-ID-Hash: CWWQJSNF6RA56OLOD2BG4LRCW234JDHW
X-MailFrom: acee.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-lsr.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, james.n.guichard@futurewei.com, gunter@vandevelde.cc, chen.ran@zte.com.cn, linchangwang.04414@h3c.com, zhao.detao@zte.com.cn, Peter Psenak <ppsenak@cisco.com>, ketant.ietf@gmail.com, gunter.van_de_velde@nokia.com, yan8925298@gmail.com, lsr <lsr@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Lsr] Re: [Technical Errata Reported] RFC9983 (9311)
List-Id: Link State Routing Working Group <lsr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/9rzgDyz10UlvbhO9MKVKvHqIWnY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Owner: <mailto:lsr-owner@ietf.org>
List-Post: <mailto:lsr@ietf.org>
List-Subscribe: <mailto:lsr-join@ietf.org>
List-Unsubscribe: <mailto:lsr-leave@ietf.org>
Hey Renato, I agree it is valid. Unfortunately, this augmentation was used as a model for the RFC 10041 advertise-unreachable-link interface augmentation and it has the same problem. Thanks, Acee > On Nov 16, 2026, at 8:42 PM, Renato Westphal <renatowestphal@gmail.com> wrote: > > Hi all, > > This erratum looks correct to me. > > I noticed the same problems while implementing RFC 9983 in Holo and > fixed the module in place, but forgot to report the erratum. > > My fix is equivalent to the corrected text: > https://github.com/holo-routing/holo/commit/d07f5d9be > > Regards, > Renato > > Em seg., 16 de nov. de 2026 às 15:42, <rfc-editor@rfc-editor.org> escreveu: >> >> The following errata report has been submitted for RFC9983, >> "OSPFv2 Anycast Property Advertisement" >> >> -------------------------------------- >> You may review the report below and at: >> https://errata.rfc-editor.org/eid9311/ >> >> -------------------------------------- >> Type: Technical >> Reported by: Yan Chen <yan8925298@gmail.com> >> >> Section 4.2 says: >> >> Original Text >> ------------- >> augment "/rt:routing/rt:control-plane-protocols/" >> + "rt:control-plane-protocol/ospf:ospf/" >> + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { >> when "derived-from(/rt:routing/rt:control-plane-protocols/" >> + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { >> description >> "This augments the OSPFv2 interface."; >> } >> description >> "This augments OSPFv2 interface with anycast >> property advertisement."; >> leaf anycast-flag { >> type boolean; >> must "not(../anycast-flag = 'true' and " >> + "/rt:routing/rt:control-plane-protocols/" >> + "rt:control-plane-protocol/ospf:ospf/" >> + "ospf:areas/ospf:area/ospf:interfaces/" >> + "ospf:interface/ospf:node-flag = 'true')" { >> error-message "The anycast-flag and the node-flag MUST " >> + "NOT both be set to 1 (true)."; >> description >> "Ensures architectural consistency by preventing a prefix >> from being marked as both anycast and node-specific."; >> } >> >> Corrected Text >> -------------- >> augment "/rt:routing/rt:control-plane-protocols/" >> + "rt:control-plane-protocol/ospf:ospf/" >> + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { >> when "derived-from-or-self(../../../../../rt:type, " >> + "'ospf:ospfv2')" { >> description >> "This augments the OSPFv2 interface."; >> } >> description >> "This augments OSPFv2 interface with anycast >> property advertisement."; >> leaf anycast-flag { >> type boolean; >> must "not(../anycast-flag = 'true' and " >> + "../ospf:node-flag = 'true')" { >> error-message "The anycast-flag and the node-flag MUST " >> + "NOT both be set to 1 (true)."; >> description >> "Ensures architectural consistency by preventing a prefix >> from being marked as both anycast and node-specific."; >> } >> >> Notes >> ----- >> The YANG module ietf-ospf-anycast-flag@2026-05-19 in Section 4.2 contains two XPath defects that cause standards-compliant YANG 1.1 validators (RFC 7950) to reject valid OSPFv2 configurations: >> >> 1. In the augment's "when" statement: >> (a) Per RFC 9129, identity "ospf:ospfv2" (base "ospf:ospf-protocol") has no derived identities in standard OSPF configurations where rt:type is set to "ietf-ospf:ospfv2". Per RFC 7950 Section 10.4.1, derived-from() returns true only if the first argument is strictly derived from (and NOT equal to) the second argument, so derived-from(..., 'ospf:ospfv2') evaluates to false for rt:type = 'ietf-ospf:ospfv2' and makes anycast-flag invalid to configure. RFC 9129 itself uses derived-from-or-self(..., 'ospf:ospfv2'). >> (b) The absolute path /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/rt:type has no predicate binding it to the enclosing control-plane-protocol instance; relative path ../../../../../rt:type scopes the check to the augmented protocol instance (from ospf:interface -> ospf:interfaces -> ospf:area -> ospf:areas -> ospf:ospf -> rt:control-plane-protocol). >> >> 2. In leaf anycast-flag's "must" statement: >> The second operand (/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area/ospf:interfaces/ospf:interface/ospf:node-flag = 'true') is an unbound absolute XPath across all OSPF interfaces on the router. Because XPath "=" over a node-set is existential, setting node-flag = 'true' on any single interface (e.g., loopback lo0) causes configuring anycast-flag = 'true' on a different interface (e.g., anycast loopback lo1) to fail validation. Per Section 2 ("Both the AC-Flag and the N-Flag MUST NOT be set to 1 for the same prefix"), the constraint applies to the same interface (../ospf:node-flag = 'true'). >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". Please >> use "Reply All" to discuss whether it should be verified or >> rejected. When a decision is reached, the verifying party >> will log in to change the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC9983 (draft-ietf-lsr-anycast-flag) >> -------------------------------------- >> Title : OSPFv2 Anycast Property Advertisement >> Publication Date : May 2026 >> Author(s) : R. Chen, D. Zhao, P. Psenak, K. Talaulikar, C. Lin >> Category : Proposed Standard >> Source : lsr (rtg) >> Stream : IETF >> Verifying Party : IESG >> _______________________________________________ >> Lsr mailing list -- lsr@ietf.org >> To unsubscribe send an email to lsr-leave@ietf.org > > > > -- > Renato Westphal
- [Lsr] [Technical Errata Reported] RFC9983 (9311) rfc-editor
- [Lsr] Re: [Technical Errata Reported] RFC9983 (93… Renato Westphal
- [Lsr] Re: [Technical Errata Reported] RFC9983 (93… Acee Lindem