Re: [netconf] Defaults and NP containers in YangPush

Martin Bjorklund <mbj@tail-f.com> Thu, 12 December 2019 08:57 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1EA6120859 for <netconf@ietfa.amsl.com>; Thu, 12 Dec 2019 00:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 ALh3H9LR-DrZ for <netconf@ietfa.amsl.com>; Thu, 12 Dec 2019 00:57:48 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA4A1200C7 for <netconf@ietf.org>; Thu, 12 Dec 2019 00:57:48 -0800 (PST)
Received: from localhost (unknown [173.38.220.41]) by mail.tail-f.com (Postfix) with ESMTPSA id CFFAD1AE02AA; Thu, 12 Dec 2019 09:57:45 +0100 (CET)
Date: Thu, 12 Dec 2019 09:57:09 +0100
Message-Id: <20191212.095709.2123523251711416815.mbj@tail-f.com>
To: balazs.lengyel=40ericsson.com@dmarc.ietf.org
Cc: netconf@ietf.org, mark.hollmann@ericsson.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <VI1PR0702MB3680D83DEA1B90619678013DF05A0@VI1PR0702MB3680.eurprd07.prod.outlook.com>
References: <VI1PR0702MB3680D83DEA1B90619678013DF05A0@VI1PR0702MB3680.eurprd07.prod.outlook.com>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/BCpi2jehs8_HQqoSg1k5GdaisyI>
Subject: Re: [netconf] Defaults and NP containers in YangPush
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2019 08:57:50 -0000

Hi,


Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org> wrote:
> Hello,
> 
> If I have the data model 
> 
>  
> 
> container cont1 {
> 
> presence “xx”;
> 
>   container cont2 {
> 
>     leaf leaf1 {
> 
>       type string;
> 
>       default ddd;
> 
> }}}
> 
>  
> 
> And I create cont1 
> 
> *	should Yang-Push report cont2 or leaf1 as created?
> *	Is this affected by with-default ?

Great question!

I think it must be affected by the server's basic-mode for
with-defaults.

My assumption is that we want the subscriber to be able to keep a copy
of the data on the publisher, and we must allow different default
handling strategies in this copy - i.e., allow different
implementation strategies.

[Another way of viewing this is that if we pass the data in the notif
back to the server in an edit-config, it should effectively be a
no-op.]

So, a 'report-all' server will send 'leaf1' in the notif, but an
'explicit' or 'trim' server will not send it.

Here's another case.  After your operation above, suppose a client
sets 'leaf1' to 'ddd'.  A 'trim' server will not include 'leaf1' in
the notis, but an 'explicit' will include it.  (And a 'report-all'
server will not see a change at all, since 'leaf1' already had
'ddd').

This means that the subscriber may need to be aware of the server's
basic-mode, in order to be able to correctly interpret the notifs.


/martin