Subject: Re: [netconf] [netconf-wg/https-notif] Should the receivers container be moved under the augment statement and the leafref renamed? (#2)

From: Kent Watsen <[email-masked]>
Date: Wed, 15 Jan 2020 00:34:19 +0000

Hi Martin,

> On Nov 19, 2019, at 10:18 AM, Martin Bjorklund <[email-masked]> wrote:
> 
>> The reason to not move the receiver container under the augment is so
>> as to allow the leafref to point to multiple receivers.
> 
> I don't understand this reason.

Each "receiver" (in https-notif) maps to an HTTPS connection from the publisher to the receiver.

There is likely to be more than one configured subscription, yet all notifications should go to the same receiver.

We'd like to use the same HTTPS "connection" for all, as opposed to having an HTTPS connection for each.

The "receiver-ref" leaf provides an indirection enabling this many-to-one relationship.

> Since this is not a stand-alone model, I think it should augment
> /sn:subscriptions.  In some way it doesn't matter what nodes are
> called and where they are located, but having descriptive names and
> keep related nodes under common subtrees helps the understanding of
> models.

Is s/receiver-ref/https-receiver-ref/ what you had in mind?

Kent // contributor