Forwarding to the authors of the RFC. K.
> On May 30, 2023, at 3:47 AM, Vanapatla Ramana (Nokia) > <[email protected]> wrote: > > Hello Team, > > Gentle remainder on the below query. > > Regards, > Ramana > > From: Vanapatla Ramana (Nokia) > Sent: Friday, May 5, 2023 8:05 PM > To: [email protected]; [email protected] > Cc: Bart Bogaert (Nokia) <[email protected]>; Ludwig Pauwels (Nokia) > <[email protected]>; Yves Beauville (Nokia) <[email protected]> > Subject: Query RFC-8348 hardware model > > 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 this be changed to "/hardware/component[name = > current()/../name]/state/admin-state","/hardware/component[name = > current()/../name]/state/alarm-state" so that it is in-line with the notation > shown in RFC7950 examples? > > RFC-8348 Example > notification hardware-state-oper-disabled { > leaf name { > type leafref { > path "/hardware/component/name"; > } > leaf admin-state { > type leafref { > path "/hardware/component/state/admin-state"; > } > leaf alarm-state { > type leafref { > path "/hardware/component/state/alarm-state"; > } > } > RFC7950 indicates to refer instance in page 162, 160 > Page 162 > The following notification defines two leafrefs to refer to an existing > admin-status: > notification link-failure { > leaf if-name { > type leafref { > path "/interface/name"; > } > } > leaf admin-status { > type leafref { > path "/interface[name = current()/../if-name]" > + "/admin-status"; > } > } > > Page 160 > The following leafrefs refer to an existing address of an interface: > container default-address { > leaf ifname { > type leafref { > path "../../interface/name"; > } > } > leaf address { > type leafref { > path "../../interface[name = current()/../ifname]" > + "/address/ip"; > } > } > } > > Regards, > Ramana > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
