Subject: Re: [netconf] More capabilities for ietf-notification-capabilities (WGLC)

From: "Reshad Rahman (rrahman)" <[email-masked]>
Date: Tue, 15 Oct 2019 13:05:45 +0000

Hi Balazs,

Makes sense to add these capabilities.

Regards,
Reshad.

From: netconf <[email-masked]> on behalf of Balázs Lengyel <balazs.lengyel=[email-masked]>
Date: Wednesday, October 9, 2019 at 10:33 AM
To: Netconf <[email-masked]>, Alexander Clemm <[email-masked]>, "Eric Voit (evoit)" <[email-masked]>, "Rob Wilton (rwilton)" <[email-masked]>
Subject: [netconf] More capabilities for ietf-notification-capabilities (WGLC)

Hello,
During WGLC it was asked that  we could/should add some more capabilities to the ietf-notification-capabilities model.
In https://tools.ietf.org/html/rfc8641#appendix-A.1 there are two more error conditions mentioned.
cant-exclude
datastore-not-subscribable

The publisher might be able to declare which change types can be used in the  leaf-list excluded-change
The publisher might want to declare that not even periodic subscriptions are supported for a specific datastore. Some people stated that supporting periodic subscriptions is mandatory if RFC8641 (Yang-Push) is supported, so we should not add this capability. But is it really mandatory to support periodic subscriptions for e.g. the start-up datastore?

I intend to add these 2 to the model.

Opinions?

Regards Balazs

--
Balazs Lengyel                    Senior Specialist                       Ericsson Hungary Ltd.
Mobile: +36-70-330-7909              email: [email-masked]