Setting mandatory for keys is redundant as mentioned in RFC 7950 section
7.8.2: Any "mandatory" statements in the key leafs are ignored.
So they were removed. This now makes it consistent with how data is
declared in option-data as well.
grouping option-data-list {
description "Option data list grouping.";
list option-data {
- key "code space";
+ key "code space data";
description "Option data entry.";
leaf code {
type uint8;
- mandatory true;
description "Option code.";
}
leaf space {
type string;
- mandatory true;
description "Option space.";
}
uses dhcp:option-data-name;
grouping option-data-list {
description "Option data list grouping.";
list option-data {
- key "code space";
+ key "code space data";
description "Option data entry.";
leaf code {
type uint16;
- mandatory true;
description "Option code.";
}
leaf space {
type string;
- mandatory true;
description "Option space.";
}
uses dhcp:option-data-name;