Re: [netconf] leafrefed data item in YANG Push

["Sterne, Jason (Nokia - CA/Ottawa)" <[e-mail]>]

This thread has moved on but a minor correction to my reply below.  I meant to say "that should *not* be accepted" 😊

From: netconf <[e-mail]> On Behalf Of Sterne, Jason (Nokia - CA/Ottawa)
Sent: Friday, December 13, 2019 2:20 PM
To: Qin Wu <[e-mail]>; [e-mail]
Subject: Re: [netconf] leafrefed data item in YANG Push

Hi Qin,

For subscriptions, I don't think it matters if 2 leafs are associated with each other via a leafref.  When you subscribe to each of those leafs, it is just like subscribing to any other 2 leafs (that aren't associated with eachother).

About the 'dangling reference': that should be accepted into the running datastore. It would fail validation. So it can only exist in the candidate.

Jason

From: netconf <[e-mail]<mailto:[e-mail]>> On Behalf Of Qin Wu
Sent: Thursday, December 12, 2019 11:09 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [netconf] leafrefed data item in YANG Push

Hello:
Can I subscribe to specific data item that refer to data item in another YANG module with other data item in the same subscription?
Module bar {
import foo {prefix ex;}
     leaf cc{type int8;}
     leaf bb {
       type leafref {
         path "../ex:aa";
       }
     }
}

Module foo {
     leaf aa {
       type int8;
     }
}
In addition, If there is dangling reference, e.g., leaf bb refer to leaf aa which doesn’t exist, how this failure is handled by the server
and exposed to the client?

-Qin