Re: [netconf] Defaults and NP containers in YangPush

[Balázs Lengyel <[e-mail]>]

-----Original Message-----
From: netconf <[e-mail]> On Behalf Of Martin Bjorklund
Sent: 2019. december 12., csütörtök 9:57
To: balazs.lengyel=[e-mail]
Cc: [e-mail]; Mark Hollmann <[e-mail]>
Subject: Re: [netconf] Defaults and NP containers in YangPush

Hi,
Balázs Lengyel <balazs.lengyel=[e-mail]> 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
_______________________________________________
BALAZS2:  I agree with you, because this way if the client reacts to all these notifications with additional edit-config operations, it will receive the expected results considering the potential error messages for create and delete operations. 

Regards Balazs