Re: [YANG] keyref

Andy Bierman <ietf@andybierman.com> wrote:
> Why does it work the same as other types.
> That's kind of a circular definition.
> 
> I don't see the use case for writable keyrefs.
> When you read the object the first time, it has the value
> from the ptarh target, and when you set the keyref leaf,
> it has the new value and no longer is a reference to the key leaf.
> Then it changes back to a reference if the manager deletes the
> keyref leaf?

That's not how it works.  What part of the text supports this
interpretation?  The idea is that the value space of the keyref type
is constrained to the set of values of the existing instances.

This means that if you have a keyref to ifIndex, and the interface 1,
3, and 4 exists, the value space is {1, 3, 4}.  When setting a leaf of
this type, you must set it to one of 1, 3, and 4.

/martin

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