[netconf] Re: ***CAUTION_Invalid_Signature*** Re: netconf 121, draft-netana-netconf-notif-envelope-01, extensions

[Andy Bierman <[e-mail]>]

On Sat, Dec 14, 2024 at 2:17 AM <[e-mail]> wrote:

> Dear Carsten,
>
> That refers to wherever operators would like to annotate metadata to
> notifications. draft-netana-netconf-notif-envelope doesn't cover this
> aspect, however there were interests from operators raised offlist, hence
> the question.
>
> This is not to be mistaken with RFC 7952 which defines how metadata can be
> annotated to YANG.
>
> In [e-mail] defined in RFC8639, a
> purpose leaf allows a network operator to describe the subscription and be
> encoded in the subscription state change notifications.
>
> https://datatracker.ietf.org/doc/html/rfc8639#section-2.7.1
> https://datatracker.ietf.org/doc/html/rfc8639#section-3.3
> https://datatracker.ietf.org/doc/html/rfc8639#section-4
>
>     leaf purpose {
>       if-feature "configured";
>       type string;
>       description
>         "Open text allowing a configuring entity to embed the
>          originator or other specifics of this subscription.";
>     }
>   }
>
>

I may have used to term metadata to refer to subscription properties that
are sent in each update.

A client can read /subscriptions/subscription=id at any time.
IMO it is odd that the subscription-started and subscription-modified
events copy most of the configuration
and announce it on an event-stream.  A netconf-config-change event is also
sent for these events.
Not sure if any other config objects have this extra reporting mechanism.
Just another way YANG Push is too heavyweight.



> I assume that the question raised has similar origin.
>
> Best wishes
> Thomas
>


Andy


>
> -----Original Message-----
> From: Carsten Bormann <[e-mail]>
> Sent: Saturday, December 14, 2024 10:25 AM
> To: Graf Thomas, INI-NET-VNC-HCS <[e-mail]>
> Cc: [e-mail]; [e-mail]; Andy Bierman <[e-mail]>;
> Rob Wilton (rwilton) <[e-mail]>; [e-mail];
> maqiufang1=[e-mail]; [e-mail];
> [e-mail]; Elhassany Ahmed, INI-NET-VNC-HCS <
> [e-mail]>; Buchs Yannick, INI-NET-VNC-HCS <
> [e-mail]>; [e-mail];
> [e-mail]; [e-mail]
> Subject: ***CAUTION_Invalid_Signature*** Re: [netconf] netconf 121,
> draft-netana-netconf-notif-envelope-01, extensions
>
>
> Be aware: This is an external email.
>
>
>
> On 2024-12-14, at 09:36, [e-mail] wrote:
> >
> >
> https://datatracker.ietf.org/meeting/121/materials/slides-121-netconf-draft-netana-netconf-notif-envelope-00-00.pdf
>
> Thanks.
>
> Can you explain/give an example for how “metadata" enters the picture?
> The document does not reference RFC 7952.
>
> Grüße, Carsten
>
>