Re: [Rtg-yang-coord] Restrictions on list keys

[Mahesh Jethanandani <[e-mail]>]

Juergen,

I did read that section but it was not clear to me. So here are some examples.

list foo {
      // Assuming one of these forms the key ...
      key “x y”; // is this valid?
      key “x z”;  // is this valid?
      key  “mode”; // is this valid? If not, how would I define a key for a choice statement?

      leaf x {
           type uint16;
      }

      leaf y {
          type uint8;
      }

      leaf z {
           type uint8;
           config false;
      }

      choice mode {
            case a {
                   leaf p {
                        type uint16;
                   }
           }
 
           case b {
                   leaf q {
                         type uint8;
                  }
           }
      }
}

> On Mar 1, 2015, at 1:43 PM, Juergen Schoenwaelder <[e-mail]> wrote:
> 
> RFC 6020 section 7.8.2:
> 
>   All key leafs in a list MUST have the same value for their "config"
>   as the list itself.
> 
> /js
> 
> On Sun, Mar 01, 2015 at 07:59:53AM -0500, Mahesh Jethanandani wrote:
>> Pardon if these questions have already been asked.
>> 
>> Are there restrictions on the following use of keys in lists
>> 
>> - a combination of rw and ro leafs
>> - a ro leaf
>> - a union of of leafs
>> 
>> Mahesh Jethanandani
>> [e-mail]
>> 
>> _______________________________________________
>> Rtg-yang-coord mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>

Mahesh Jethanandani
[e-mail]