Re: [YANG] key clause issues

See below

PS.:
The reason for the existence of YANG is that it is more simple then XSD." quote from Balazs

Andy Bierman wrote:
> Hi,
> 
> I have a few concerns with the key clause...
...

> Issue 2)
> 
>   Why is the CLR about a leaf appearing more than once in the key needed?
>   It should be up to the DM writer to decide if this makes sense or not:
> 
>    list addr-pairs {
>      key "addr-type src-addr addr-type dest-addr";
> 
>      leaf addr-type { type ietf:InetAddressType; }
>      leaf src-addr { type ietf:InetAddress; }
>      leaf dest-addr { type ietf:InetAddress; }
>      // ... rest of list entry
>    }
> 
>    Why is this illegal?
>    It may be bad practice (according to RFC 4001), but should it be 
> illegal?
[BALAZS]: When the user/programmer uses this in an edit-config he might think that the two 
add-types are two distinct pieces of data, while they are actually the same.

Would the user actually have to provide the addr-type twice in a netconf message?
How do you handle if the two provided values in a netconf request are not the same?

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