Re: [YANG] keyref

[Balazs Lengyel <[e-mail]>]

Hello,
We are trying to define a formal way to specify relationships between config database nodes. 
The this problem has many facets
- reference to multi-keyed items
- reference to leafs versus keys
- constraining references to certain items or having free pointers
- reference integrity

The problem we try to solve is how to define these relations in a way that allows automatic 
checking. We need some solution, even if we do not solve the complete problem. E.g. I think 
referential integrity is a too high goal.

Balazs

Andy Bierman wrote:
> IMO, it is not clear what problem is being solved by keyref.
> There seems to be some assumption that the purpose of all this
> complexity is justified because of all the value it provides.
> 
> The InterfaceIndex approach is well-established and simple.
> 
>      leaf mgmt-interface {
>          type keyref {
>              path "/if:interfaces/if:interface/if:ifIndex";
>          }
>      }
> 
>      leaf mgmt-interface {
>          type if:InterfaceIndex;
>      }
> 
> Not only is the TC approach simpler, but keyref does not support
> the ability to hold a 'not-set' value, such as InterfaceIndexOrZero.


_______________________________________________
YANG mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/yang