-module openconfig-extensions {
- oc-ext:openconfig-version "0.0.1";
- yang-version "1";
- namespace "http://openconfig.net/yang/openconfig-ext";
- prefix "oc-ext";
+module semantic-version {
+ sv:semantic-version "0.0.1";
- organization "OpenConfig working group";
+ namespace "urn:opendaylight:yang:extension:semantic-version";
+ prefix sv;
+ yang-version 1;
- contact
- "OpenConfig working group
- www.openconfig.net";
-
- description
- "This module provides extensions to the YANG language to allow
- OpenConfig specific functionality and meta-data to be defined.";
-
- revision "2017-01-29" {
- description
- "Added extension for annotating encrypted values.";
- reference "TBD";
- }
-
- revision "2015-10-09" {
- description
- "Initial OpenConfig public release";
- reference "TBD";
+ revision 2016-02-02 {
+ description "Initial verison";
}
- revision "2015-10-05" {
- description
- "Initial revision";
- reference "TBD";
- }
-
- extension openconfig-version {
- argument "semver" {
+ extension semantic-version {
+ argument "semantic-version" {
yin-element false;
}
description
The version number is stored in the module meta-data.";
}
-
- extension openconfig-encrypted-value {
- description
- "This extension provides an annotation on schema nodes to
- indicate that the corresponding value should be stored and
- reported in encrypted form.
- Clients reading the configuration or applied configuration
- for the node should expect to receive only the encrypted value.
- This annotation may be used on nodes such as secure passwords
- in which the device never reports a cleartext value, even
- if the input is provided as cleartext.";
- }
-}
\ No newline at end of file
+}