1 module openconfig-extensions {
3 namespace "http://openconfig.net/yang/openconfig-ext";
6 organization "OpenConfig working group";
9 "OpenConfig working group
13 "This module provides extensions to the YANG language to allow
14 OpenConfig specific functionality and meta-data to be defined.";
16 revision "2017-01-29" {
18 "Added extension for annotating encrypted values.";
22 revision "2015-10-09" {
24 "Initial OpenConfig public release";
28 revision "2015-10-05" {
34 oc-ext:openconfig-version "0.0.1";
36 extension openconfig-version {
41 "The OpenConfig version number for the module. This is
42 expressed as a semantic version number of the form:
45 * x corresponds to the major version,
46 * y corresponds to a minor version,
47 * z corresponds to a patch version.
48 This version corresponds to the model file within which it is
49 defined, and does not cover the whole set of OpenConfig models.
50 Where several modules are used to build up a single block of
51 functionality, the same module version is specified across each
52 file that makes up the module.
54 A major version number of 0 indicates that this model is still
55 in development (whether within OpenConfig or with industry
56 partners), and is potentially subject to change.
58 Following a release of major version 1, all modules will
59 increment major revision number where backwards incompatible
60 changes to the model are made.
62 The minor version is changed when features are added to the
63 model that do not impact current clients use of the model.
65 The patch-level version is incremented when non-feature changes
66 (such as bugfixes or clarifications to human-readable
67 descriptions that do not impact model functionality) are made
68 that maintain backwards compatibility.
70 The version number is stored in the module meta-data.";
73 extension openconfig-encrypted-value {
75 "This extension provides an annotation on schema nodes to
76 indicate that the corresponding value should be stored and
77 reported in encrypted form.
78 Clients reading the configuration or applied configuration
79 for the node should expect to receive only the encrypted value.
80 This annotation may be used on nodes such as secure passwords
81 in which the device never reports a cleartext value, even
82 if the input is provided as cleartext.";