Hello Juergen,
https://tools.ietf.org/html/rfc7950#section-7.6.5 states: 

If "mandatory" is "true", the behavior of the constraint depends on
   the type of the leaf's closest ancestor node in the schema tree that
   is not a non-presence container (see Section 7.5.1):
   o  If no such ancestor exists in the schema tree, the leaf MUST
      exist.
   o  Otherwise, if this ancestor is a case node, the leaf MUST exist if
      any node from the case exists in the data tree.
   o  Otherwise, the leaf MUST exist if the ancestor node exists in the
      data tree.

Let's take the simplest example a top level leaf. If it is mandatory=true ->
the leaf MUST exist. The above statements do not differentiate between
config=true or config=false leaves. 

If the leaf exists, for me, it is trivial that the reply to a get/get-data
operation MUST return it.  (assuming it is not filtered out)
Anything else would be counter-intuitive and IMHO contradict RFC 7950.

Do you agree? 
If not, could you please describe what does a mandatory=true statement mean
for a config=false leaf in your interpretation?

-------------------------------------------------------------------
IMHO we never stated that 


Regards Balazs

-----Original Message-----
From: Juergen Schoenwaelder <[email protected]> 
Sent: 2021. április 14., szerda 17:08
To: Balázs Lengyel <[email protected]>
Cc: Sterne, Jason (Nokia - CA/Ottawa) <[email protected]>; Andy Bierman
<[email protected]>; [email protected]
Subject: Re: [netmod] YANG Versioning Weekly Call Minutes - 2021-04-13

On Wed, Apr 14, 2021 at 01:55:04PM +0000, Balázs Lengyel wrote:

> *     On the other hand, changing a state leaf from mandatory false to
true means always including the leaf in a <get> response.

Where do you get this from?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103
<https://protect2.fireeye.com/v1/url?k=9e758f86-c1eeb764-9e75cf1d-86073b36ea
28-0d304a28a3dae2f9&q=1&e=81180de4-8958-40ba-aeb8-c689e3da33e8&u=https%3A%2F
%2Fwww.jacobs-university.de%2F>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to