1 <?xml version="1.0" encoding="UTF-8"?>
2 <module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext"
3 name="openconfig-extensions">
4 <yang-version value="1"></yang-version>
5 <namespace uri="http://openconfig.net/yang/openconfig-ext"></namespace>
6 <prefix value="oc-ext"></prefix>
8 <text>OpenConfig working group</text>
11 <text>OpenConfig working group www.openconfig.net</text>
15 This module provides extensions to the YANG language to allow
16 OpenConfig specific functionality and meta-data to be defined.
19 <revision date="2017-01-29">
21 <text>Added extension for annotating encrypted values.</text>
27 <revision date="2015-10-09">
29 <text>Initial OpenConfig public release</text>
35 <revision date="2015-10-05">
37 <text>Initial revision</text>
43 <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
44 <extension name="openconfig-version">
45 <argument name="semver">
46 <yin-element value="false"></yin-element>
48 <status value="current"></status>
50 <text>The OpenConfig version number for the module. This is
51 expressed as a semantic version number of the form:
54 * x corresponds to the major version,
55 * y corresponds to a minor version,
56 * z corresponds to a patch version.
57 This version corresponds to the model file within which it is
58 defined, and does not cover the whole set of OpenConfig models.
59 Where several modules are used to build up a single block of
60 functionality, the same module version is specified across each
61 file that makes up the module.
63 A major version number of 0 indicates that this model is still
64 in development (whether within OpenConfig or with industry
65 partners), and is potentially subject to change.
67 Following a release of major version 1, all modules will
68 increment major revision number where backwards incompatible
69 changes to the model are made.
71 The minor version is changed when features are added to the
72 model that do not impact current clients use of the model.
74 The patch-level version is incremented when non-feature changes
75 (such as bugfixes or clarifications to human-readable
76 descriptions that do not impact model functionality) are made
77 that maintain backwards compatibility.
79 The version number is stored in the module meta-data.
83 <extension name="openconfig-encrypted-value">
86 This extension provides an annotation on schema nodes to
87 indicate that the corresponding value should be stored and
88 reported in encrypted form.
89 Clients reading the configuration or applied configuration
90 for the node should expect to receive only the encrypted value.
91 This annotation may be used on nodes such as secure passwords
92 in which the device never reports a cleartext value, even
93 if the input is provided as cleartext.