netconfcentral logo

openconfig-extensions

HTML

openconfig-extensions@2017-04-11



  module openconfig-extensions {

    yang-version 1;

    namespace
      "http://openconfig.net/yang/openconfig-ext";

    prefix oc-ext;

    organization "OpenConfig working group";

    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-04-11" {
      description
        "rename password type to 'hashed' and clarify description";
      reference
        "0.3.0";

    }

    revision "2017-01-29" {
      description
        "Added extension for annotating encrypted values.";
      reference
        "0.2.0";

    }

    revision "2015-10-09" {
      description
        "Initial OpenConfig public release";
      reference
        "0.1.0";

    }


    extension openconfig-version {
      argument "semver" {
        yin-element false;
      }
      description
        "The OpenConfig version number for the module. This is
       expressed as a semantic version number of the form:
        x.y.z
       where:
        * x corresponds to the major version,
        * y corresponds to a minor version,
        * z corresponds to a patch version.
       This version corresponds to the model file within which it is
       defined, and does not cover the whole set of OpenConfig models.
       Where several modules are used to build up a single block of
       functionality, the same module version is specified across each
       file that makes up the module.

       A major version number of 0 indicates that this model is still
       in development (whether within OpenConfig or with industry
       partners), and is potentially subject to change.

       Following a release of major version 1, all modules will
       increment major revision number where backwards incompatible
       changes to the model are made.

       The minor version is changed when features are added to the
       model that do not impact current clients use of the model.

       The patch-level version is incremented when non-feature changes
       (such as bugfixes or clarifications to human-readable
       descriptions that do not impact model functionality) are made
       that maintain backwards compatibility.

       The version number is stored in the module meta-data.";
    }

    extension openconfig-hashed-value {
      description
        "This extension provides an annotation on schema nodes to
       indicate that the corresponding value should be stored and
       reported in hashed form.

       Hash algorithms are by definition not reversible. Clients
       reading the configuration or applied configuration for the node
       should expect to receive only the hashed value. Values written
       in cleartext will be hashed. 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.";
    }
  }  // module openconfig-extensions

Summary

  
openconfig-extensions  
  
Organization OpenConfig working group
  
Module openconfig-extensions
Version 2017-01-29
File openconfig-extensions@2017-01-29.yang
  
Prefix oc-ext
Namespace http://openconfig.net/yang/openconfig-ext
  
Cooked /cookedmodules/openconfig-extensions/2017-01-29
YANG /src/openconfig-extensions@2017-01-29.yang
XSD /xsd/openconfig-extensions@2017-01-29.xsd
  
Abstract This module provides extensions to the YANG language to allow OpenConfig specific functionality and meta-data to be defined.
  
Contact
OpenConfig working group
www.openconfig.net
  
openconfig-extensions  
  
Organization OpenConfig working group
  
Module openconfig-extensions
Version 2020-06-16
File openconfig-extensions.yang
  
Prefix oc-ext
Namespace http://openconfig.net/yang/openconfig-ext
  
Cooked /cookedmodules/openconfig-extensions/2020-06-16
YANG /src/openconfig-extensions@2020-06-16.yang
XSD /xsd/openconfig-extensions@2020-06-16.xsd
  
Abstract This module provides extensions to the YANG language to allow OpenConfig specific functionality and meta-data to be defined.
  
Contact
OpenConfig working group
www.openconfig.net
  
openconfig-extensions  
  
Organization OpenConfig working group
  
Module openconfig-extensions
Version 2017-04-11
File openconfig-extensions.yang
  
Prefix oc-ext
Namespace http://openconfig.net/yang/openconfig-ext
  
Cooked /cookedmodules/openconfig-extensions/2017-04-11
YANG /src/openconfig-extensions@2017-04-11.yang
XSD /xsd/openconfig-extensions@2017-04-11.xsd
  
Abstract This module provides extensions to the YANG language to allow OpenConfig specific functionality and meta-data to be defined.
  
Contact
OpenConfig working group
www.openconfig.net

Description

 
openconfig-extensions
This module provides extensions to the YANG language to allow
OpenConfig specific functionality and meta-data to be defined.
 
openconfig-extensions
This module provides extensions to the YANG language to allow
OpenConfig specific functionality and meta-data to be defined.
 
openconfig-extensions
This module provides extensions to the YANG language to allow
OpenConfig specific functionality and meta-data to be defined.

Extensions

Extension Argument Abstract
catalog-organization org This extension specifies the organization name that should be used within the module catalogue on the device for the specified YANG module. It stores a pithy string where the YANG organization statement may contain more details.
openconfig-encrypted-value   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 encr...
openconfig-hashed-value   This extension provides an annotation on schema nodes to indicate that the corresponding value should be stored and reported in hashed form. Hash algorithms are by definition not reversible. Clients reading the configuration or applied configuration for ...
openconfig-hashed-value   This extension provides an annotation on schema nodes to indicate that the corresponding value should be stored and reported in hashed form. Hash algorithms are by definition not reversible. Clients reading the configuration or applied configuration for ...
openconfig-version semver The OpenConfig version number for the module. This is expressed as a semantic version number of the form: x.y.z where: * x corresponds to the major version, * y corresponds to a minor version, * z corresponds to a patch version. This version correspon...
openconfig-version semver The OpenConfig version number for the module. This is expressed as a semantic version number of the form: x.y.z where: * x corresponds to the major version, * y corresponds to a minor version, * z corresponds to a patch version. This version correspon...
openconfig-version semver The OpenConfig version number for the module. This is expressed as a semantic version number of the form: x.y.z where: * x corresponds to the major version, * y corresponds to a minor version, * z corresponds to a patch version. This version correspon...
operational   The operational annotation is specified in the context of a grouping, leaf, or leaf-list within a YANG module. It indicates that the nodes within the context are derived state on the device. OpenConfig data models divide nodes into the following three ca...
origin origin This extension specifies the name of the origin that the YANG module falls within. This allows multiple overlapping schema trees to be used on a single network element without requiring module based prefixing of paths.
posix-pattern pattern Provides a POSIX ERE regular expression pattern statement as an alternative to YANG regular expresssions based on XML Schema Datatypes. It is used the same way as the standard YANG pattern statement defined in RFC6020 and RFC7950, but takes an argument th...
regexp-posix   This extension indicates that the regular expressions included within the YANG module specified are conformant with the POSIX regular expression format rather than the W3C standard that is specified by RFC6020 and RFC7950.
telemetry-atomic   The telemetry-atomic annotation is specified in the context of a subtree (containre, or list), and indicates that all nodes within the subtree are always updated together within the data model. For example, all elements under the subtree may be updated as...
telemetry-on-change   The telemetry-on-change annotation is specified in the context of a particular subtree (container, or list) or leaf within the YANG schema. Where specified, it indicates that the value stored by the nodes within the context change their value only in resp...