Re: [YANG] keyref

Andy Bierman <ietf@andybierman.com> wrote:
> Not only is the TC approach simpler

As Juergen pointed out, there is no formalism to help tools.  Also, it
becomes awkward to reference mulit-level and/or multi-key instances.

> but keyref does not support
> the ability to hold a 'not-set' value, such as InterfaceIndexOrZero.

Mark it as optional instead - why set to some in-band invalid value?

      leaf mgmt-interface {
          mandatory false;
          type keyref {
              path "/if:interfaces/if:interface/if:ifIndex";
          }
      }

If it is set, it has to point to an existing interface.

> YANG is also missing the ability to use key leafs from different
> tables, like SMIv2.

No:

  list myIfTable {
    key myIfIndex;
    leaf myIfIndex {
       type keyref {
         path "/if:interfaces/if:interface/if:ifIndex";
       }
     }
   }

covers this case.

>       leaf myInOctets {
>         type smi:Counter32;
>         leafref "/if:interfaces/if:interface/if:ifInOctets";
>       }
>    }

This is a very good example.  How can you tell which ifEntry's
ifInOctets this myInOctets actually refer to??

/martin

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