Re: [netmod] evaluation of "when" under NMDA

Martin Bjorklund <mbj@tail-f.com> Tue, 05 December 2017 14:39 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416CC1294E6 for <netmod@ietfa.amsl.com>; Tue, 5 Dec 2017 06:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjeS0qmvD3xD for <netmod@ietfa.amsl.com>; Tue, 5 Dec 2017 06:39:45 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3C709124F57 for <netmod@ietf.org>; Tue, 5 Dec 2017 06:39:45 -0800 (PST)
Received: from localhost (unknown [173.38.220.60]) by mail.tail-f.com (Postfix) with ESMTPSA id 37B1D1AE0144; Tue, 5 Dec 2017 15:39:44 +0100 (CET)
Date: Tue, 05 Dec 2017 15:38:24 +0100
Message-Id: <20171205.153824.189055168841663121.mbj@tail-f.com>
To: balazs.lengyel@ericsson.com
Cc: rwilton@cisco.com, andy@yumaworks.com, lhotka@nic.cz, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <aa579364-ac89-36f4-8947-4a5eb1c6ba48@ericsson.com>
References: <CABCOCHRg7H=DbS1oxOhdq=dkQgAcL_r1ECSFgcU=DkE-vXwcOg@mail.gmail.com> <409e9bb5-fcbe-d94f-a7cb-cb7961d9fdb2@cisco.com> <aa579364-ac89-36f4-8947-4a5eb1c6ba48@ericsson.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/HY6qdhX7yQgxQftRh8AqZm-O-bE>
Subject: Re: [netmod] evaluation of "when" under NMDA
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 14:39:47 -0000

Balazs Lengyel <balazs.lengyel@ericsson.com> wrote:
> On 2017-12-05 11:04, Robert Wilton wrote:
> 
> 
> 
> 
> 
>         I see your point now.
>         The server has to evaluate the when-stmts in operational.
> 
>     I think that this is probably down to implementation, but I don't
>     think that this is necessarily required. A server is meant to
>     conform to 'when' statements in <operational> (e.g. if the system
>     is in a normal steady state), but they are allowed to be violated,
>     and I'm not expecting that a server would evaluate them (except
>     perhaps to discover implementation bugs). Further, if violations
>     of when statements in <operational> are detected then I don't
>     think that there is anything that the server can reasonable do.
> 
> 
> 
> BALAZS: I always thought that if a when statement's argument was true
> but becomes false, all instance data that is set/written according to
> the schema nodes affected by the when statement shall be removed by
> the server. So IMHO the server can and should do something about a
> violated when statement.

Yes.

> Actually I would like a list of statements and constraints that MUST
> be satisfied in the different data stores. Speaking about syntactic
> versus semantic seems fluffy.

See RFC 7950, section 8 (esp. 8.1 and 8.2).


/martin