[YANG] 7.8.3 unique statement

Hi,

There seem to be many details left out for the unique-stmt (within a list)
that need to be in a standard:

   - what if not all the leafs listed in the unique-stmt are mandatory?
       - is the unique-stmt ignored?
       - Is NULL-value treated as one of the unique values?
       - what if some missing leafs have defaults (ensuring they will not be unique)?
   - where are the detailed specifications of the canonical formats
     for each YANG datatype (especially bits, anyxml, string) so that
     every implementation will come up with the same answer when evaluating
     uniqueness?
   - what is the exact behavior required for a NETCONF agent wrt/ <edit-config>
     processing and unique-stmt enforcement?
   - Is there any significance to the order of node identifiers?
       unique "addr port";
       unique "port addr";
   - Are the target nodes limited to direct definitions and expanded uses?
     (I.e., unique clauses that include leafs expanded from augment not allowed)

Andy

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