Subject: Re: [netconf] RFC 8639 configured subscriptions

From: Kent Watsen <[email-masked]>
Date: Thu, 1 Apr 2021 16:50:25 +0000

Hi Michal,

The “https-notif” and “udp-notif” drafts moving through the WG enable *configured* subscriptions to be delivered.

So far there seems to be no interest in publishing a standard for RESTCONF or NETCONF based *configured* subscriptions.  

That said, it’s pretty easy to configure a RC/NC “call-home” connection over which the call-home client (i.e., the NMS/Orchestrator) immediately initiates a *dynamic” subscription for notifications.

Cheers,
Kent

> On Mar 9, 2021, at 10:24 AM, Eric Voit (evoit) <evoit=[email-masked]> wrote:
> 
> Hi Michal,
> 
> There is nothing which halts an implementation.   The question really is someone wanting to push the rest of the rest of NETCONF Configured Subscription requirements through the IETF process.  It shouldn't controversial to complete the work.  But the IETF process is always time consuming.
> 
> Eric
> 
>> From: Michal Vaško, March 9, 2021 1:51 AM
>> 
>> Hi Eric,
>> 
>> I appreciate the help but what is the official situation then?
>> NETCONF/RESTCONF has RFCs only for dynamic subscriptions so for these
>> protocols configured subscriptions are not supported? Actually, there are no
>> protocols that support it, currently?
>> 
>> Michal
>> 
>> On Monday, March 08, 2021 18:06 CET, "Eric Voit (evoit)" <[email-masked]>
>> wrote:
>> 
>>> Hi Michal,
>>> 
>>> Configured subscriptions for NETCONF was originally in RFC-8640.  But
>>> the draft was rescoped to just dynamic subscriptions by the time it
>>> was published.
>>> 
>>> So it might be worth looking through:
>>> https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notificat
>>> ions-1
>>> 0
>>> This version does include the module you request below.  Also included
>>> is other text which might be of interest.
>>> 
>>> Eric
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: netconf <[email-masked]> On Behalf Of Michal Vaško
>>>> Sent: Monday, March 8, 2021 10:17 AM
>>>> To: netconf <[email-masked]>
>>>> Subject: [netconf] RFC 8639 configured subscriptions
>>>> 
>>>> Hi,
>>>> 
>>>> we want to implement both dynamic and configured subscriptions for a
>>>> NETCONF server. Reading through the RFC, it is pretty clear that the
>>> configured
>>>> subscriptions require a YANG module with NETCONF-specific parameters
>>>> including a "netconf" identity derived from the "transport" identity
>>>> (juts
>>> like the
>>>> "foo" example[1]). We have not managed to find such a module, does
>>>> it
>>> exist? If
>>>> not, could someone provide some more information about how it can be
>>>> implemented? Thank you.
>>>> 
>>>> Regards,
>>>> Michal
>>>> 
>>>> [1] https://tools.ietf.org/html/rfc8639#appendix-A
>>>> 
>>>> _______________________________________________
>>>> netconf mailing list
>>>> [email-masked]
>>>> https://www.ietf.org/mailman/listinfo/netconf
> _______________________________________________
> netconf mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/netconf