blob: d5e9442a83c4a440369539329bd9e0578c2526aa [file] [log] [blame]
Khen Nursimuluf8abbc92016-11-04 19:56:45 -04001module openconfig-extensions {
2
3 yang-version "1";
4
5 // namespace
6 namespace "http://openconfig.net/yang/openconfig-ext";
7
8 prefix "ocext";
9
10 // meta
11 organization "OpenConfig working group";
12
13 contact
14 "OpenConfig working group
15 www.openconfig.net";
16
17 description
18 "This module provides extensions to the YANG language to allow
19 OpenConfig specific functionality and meta-data to be defined.";
20
21 revision "2015-10-09" {
22 description
23 "Initial OpenConfig public release";
24 }
25
26 revision "2015-10-05" {
27 description
28 "Initial revision";
29 reference "TBD";
30 }
31
32 // extension statements
33 extension openconfig-version {
34 argument "semver" {
35 yin-element false;
36 }
37 description
38 "The OpenConfig version number for the module. This is
39 expressed as a semantic version number of the form:
40 x.y.z
41 where:
42 * x corresponds to the major version,
43 * y corresponds to a minor version,
44 * z corresponds to a patch version.
45 This version corresponds to the model file within which it is
46 defined, and does not cover the whole set of OpenConfig models.
47 Where several modules are used to build up a single block of
48 functionality, the same module version is specified across each
49 file that makes up the module.
50
51 A major version number of 0 indicates that this model is still
52 in development (whether within OpenConfig or with industry
53 partners), and is potentially subject to change.
54
55 Following a release of major version 1, all modules will
56 increment major revision number where backwards incompatible
57 changes to the model are made.
58
59 The minor version is changed when features are added to the
60 model that do not impact current clients use of the model.
61
62 The patch-level version is incremented when non-feature changes
63 (such as bugfixes or clarifications to human-readable
64 descriptions that do not impact model functionality) are made
65 that maintain backwards compatibility.
66
67 The version number is stored in the module meta-data.";
68 }
69}