Re: [YANG] keyref

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Tue, Jan 22, 2008 at 10:09:16AM +0100, Martin Bjorklund wrote:
> > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > > On Tue, Jan 22, 2008 at 09:44:30AM +0100, Martin Bjorklund wrote:
> > > 
> > > > That's why we don't want to allow keyrefs from config to non-config.
> > > > 
> > > > Maybe this is a use case that we want to support as well.  But I don't
> > > > see the difference between such a ref and a InterfaceIndex type
> > > > solution.
> > > 
> > > Well, the InterfaceIndex type just says "the value identifies an
> > > interface" - no more no less. The keyref is much more ambitiuous.
> > > Despite the fact that it is only usable for keys, your aim is to bind
> > > things together such that value changes automatically propagate.
> > 
> > No, no automatic propagation.
> > 
> > See
> > http://www.yang-central.org/twiki/bin/view/Main/YangExamplesExecdNtp
> > for a YANG example.  The idea in this example is that there is a list
> > of keys and a list of servers.  Each server uses exactly one key, and
> > this is done through a keyref.  When you try to set server/key, it
> > will only accept the name of an existing key.  If you try to remove
> > the key, the config will not validate.
> 
> But if I change the value of key.name of a key referenced by say
> requestkey, does the value of requestkey change as well?

No.

/martin

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang