Re: [netmod] [netconf] netconf-config-change and NMDA

Martin Bjorklund <> Tue, 05 March 2019 13:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1134D1312C0; Tue, 5 Mar 2019 05:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZqL_oPD9gcQ5; Tue, 5 Mar 2019 05:54:43 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1E89A131291; Tue, 5 Mar 2019 05:54:43 -0800 (PST)
Received: from localhost (unknown []) by (Postfix) with ESMTPSA id 208111AE0386; Tue, 5 Mar 2019 14:54:41 +0100 (CET)
Date: Tue, 05 Mar 2019 14:54:41 +0100
Message-Id: <>
From: Martin Bjorklund <>
In-Reply-To: <4a3-5c7e7a80-3-125b9e20@241827065>
References: <4a3-5c7e7a80-3-125b9e20@241827065>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [netmod] [netconf] netconf-config-change and NMDA
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Mar 2019 13:54:48 -0000


Michal Vaško <> wrote:
> Hi,
> I have encountered a problem while validating
> ietf-netconf-notifications netconf-config-change notification while
> following NMDA. The RFC [1] says that the "target" instance-identifier
> in this notification should be validated against operational
> datastore. In my use-case there was a running datastore modification
> and the "target" was not found in the operational datastore so the
> notification failed to be validated. I still believe the notification
> should be valid and this seems to be the result of a flaw in the
> specification somewhere. Thanks for any input.

I think that the problem existed even before NMDA.  The
netconf-config-change says that the target refers to a node in the
affected datastore, and if the affected datastore was startup the
instance-identifier wouldn't validate with the given XPath context.

Also, even in the case that the datastore was 'running', if the
operation was 'delete', the target node could presumably point to the
deleted node, which wouldn't validate.

Not sure what the right fix is; maybe we shouldn't use an
instance-identifier at all in this notification?  Or maybe it is ok
since the description clearly says that the target refers to a node in
the affected datastore.

[OTOH, in general it is very hard to tell if validation against the
operational state works or not, since it requires a stable snapshot of
the operational state.]


> Regards,
> Michal
> [1]
> _______________________________________________
> netconf mailing list