Converted from YANG file 'yuma-types.yang' by yangdump version 2.2.1737 Module: yuma-types Organization: Netconf Central Version: 2011-12-18 Contact: Andy Bierman <andy at netconfcentral.org> Yuma Common Data Types /usr/share/yuma/modules/netconfcentral/yuma-types.yang Netconf Central Andy Bierman <andy at netconfcentral.org> 2011-12-18 Added TransactionId data type. 2010-11-28 Change default indent from 3 to 2. 2010-01-25 Adjust name lengths in ranges and patterns. 2008-11-21 Renamed ncxtypes to yuma-types. 2008-07-20 Converted from ncxtypes.ncx. Changed int base type to int32 for YANG Changed uint base type to uint32 for YANG Changed long base type to int64 for YANG Changed ulong base type to uint64 for YANG Changed ustring base type to binary for YANG General Purpose NCX Name string. Qualified Name: module-name:NcxName OR owner-name:NcxName. Union of all the Identifier types. NCX Session ID number Requested Maximum Line Length NCX User Name string. NCX Group Name string. NCX System access control mode. strict no access control checking enforced 0 any RPC method in the netconf namespace can be invoked; read-only data allowed for all 1 RPC entry must be present to invoke an RPC method; ncxacl Data entry must be present to access any data. (Except for user == 'root'.) 2 NCX RPC Type Classifications 0 1 2 3 4 NCX Session debug logging control enumeration. Each successive value includes all the previous messages from lower value enumeration values, plus the messages for the specified value. off == no logging is done error == log error messages warn == log warning messages info == log info messages debug == log debug level 1 messages debug2 == log debug level 2 messages debug3 == log debug level 3 messages debug4 == log debug level 4 messages info 0 1 2 3 4 5 6 7 Transport layer port number. Non-negative index value PATHSPEC formatted string indicating the machine-dependent search path for the NCX programs to use. Parameters with this data type can be used to override the default search order, and insert special work directories in the search path. Each component in the string is an absolute or relative directory path specification. The colon char ':' is used to separate the path strings. Whitespace is not allowed in the string at all. For example, the following string contains 3 paths that would be used in the order given: /home/users/testbed1/yang:/home/users/yang:/usr/share/yang A string which specifies a module name, or a filespec which represents a module, with an optional revision date. If this string represents a filespec, containing any path separation characters, and/or ending with the '.yang' or '.yin' extension, then only that file location will be checked. If this string represents a module name, then the module search path will be checked for a file with the module name and the '.yang' or '.yin.' extension. If this string contains a module name followed by an 'at sign' character (@), followed by a revision string (e.g., foo@2010-01-01), then that specific version of the module will be used. If this string begins with a '~' character, then a username is expected to follow or a directory separator character. If it begins with a '$' character, then an environment variable name is expected to follow. ~/some/path ==> <my-home-dir>/some/path ~fred/some/path ==> <fred-home-dir>/some/path $workdir/some/path ==> <workdir-env-var>/some/path A string which specifies a directory name. Requested indent amount. Only a limited range of line indent values are allowed. 2 Number of seconds to wait for a response from the NETCONF peer before declaring a timeout. Zero means no timeout at all. seconds 30 Represents a specific date in YYYY-MM-DD format. Represents a feature specifier, which consists of a module-name, colon character ':' and then a feature name (e.g., 'foo:bar') Database edit transaction identifier. This is not a permanent identifier, and should only be used for 'equal or not-equal' comparison tests. The value will wrap after the maximum value is reached.