Hi,
No changes are needed.
The notification definition says each leaf will be set to a value that
matches an instance of the leafref path.
The 'current()' linkage in your example links the sibling 'ifname' leaf to
select a matching instance.
That is not relevant to this notification example.
Forwarding to the authors of the RFC.
K.
> On May 30, 2023, at 3:47 AM, Vanapatla Ramana (Nokia)
> wrote:
>
> Hello Team,
>
> Gentle remainder on the below query.
>
> Regards,
> Ramana
>
> From: Vanapatla Ramana (Nokia)
> Sent: Friday, May 5, 2023 8:05 PM
> To:
Forwarding to the authors of the RFC.
K.
> On May 30, 2023, at 3:47 AM, Vanapatla Ramana (Nokia)
> wrote:
>
> Hello Team,
>
> Gentle remainder on the below query.
>
> Regards,
> Ramana
>
> From: Vanapatla Ramana (Nokia)
> Sent: Friday, May 5, 2023 8:05 PM
> To:
Hello Team,
Gentle remainder on the below query.
Regards,
Ramana
From: Vanapatla Ramana (Nokia)
Sent: Friday, May 5, 2023 8:05 PM
To: draft-ietf-netmod-ent...@ietf.org; netmod@ietf.org
Cc: Bart Bogaert (Nokia) ; Ludwig Pauwels (Nokia)
; Yves Beauville (Nokia)
Subject: Query RFC-8348 hardware
Hello
notification 'hardware-state-oper-enabled', notification
'hardware-state-oper-disabled' contains leaf admin-state, alarm-state
referring to path "/hardware/component/state/admin-state" ,
"/hardware/component/state/alarm-state" but not specifying instance of hardware
component
Should
