Difference: YangTypesHtml (1 vs. 2)

Revision 22011-02-15 - MartinBjoerklund

Line: 1 to 1
 
META TOPICPARENT name="YangExamples"
Changed:
<
<
module yang-types {

>
>
module ietf-yang-types {

 
Changed:
<
<
// XXX namespace to be allocated by IANA

namespace "urn:ietf:params:xml:ns:yang:yang-types";

>
>
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types";
  prefix "yang";

organization

Changed:
<
<
"YANG Language Design Team";
>
>
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
  contact
Changed:
<
<
"Martin Bjorklund (Editor) <mbj@tail-f.com>";
>
>
"WG Web: <http://tools.ietf.org/wg/netmod/> WG List: <mailto:netmod@ietf.org>

WG Chair: David Partain <mailto:david.partain@ericsson.com>

WG Chair: David Kessens <mailto:david.kessens@nsn.com>

Editor: Juergen Schoenwaelder <mailto:j.schoenwaelder@jacobs-university.de>";

  description
Changed:
<
<
"This module contains standard derived YANG types.";
>
>
"This module contains a collection of generally useful derived YANG data types.

Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC 6021; see the RFC itself for full legal notices.";

 
Changed:
<
<
revision 2007-10-02 { description "Initial revision.";
>
>
revision 2010-09-24 { description "Initial revision."; reference "RFC 6021: Common YANG Data Types";
  }
Changed:
<
<
/* * collection of counter and gauge types */
>
>
/*** collection of counter and gauge types ***/
  typedef counter32 { type uint32; description "The counter32 type represents a non-negative integer
Changed:
<
<
which monotonically increases until it reaches a
>
>
that monotonically increases until it reaches a
  maximum value of 2^32-1 (4294967295 decimal), when it wraps around and starts increasing again from zero.
Changed:
<
<
Counters have no defined `initial' value, and thus, a
>
>
Counters have no defined 'initial' value, and thus, a
  single value of a counter has (in general) no information content. Discontinuities in the monotonically increasing value normally occur at re-initialization of the management system, and at other times as specified in the
Changed:
<
<
description of an object instance using this type. If such other times can occur, for example, the creation of an object instance of type counter32 at times other than re-initialization, then a corresponding object should be defined, with an appropriate type, to indicate the last discontinuity.
>
>
description of a schema node using this type. If such other times can occur, for example, the creation of a schema node of type counter32 at times other than re-initialization, then a corresponding schema node should be defined, with an appropriate type, to indicate the last discontinuity.
  The counter32 type should not be used for configuration
Changed:
<
<
objects. A default statement should not be used for attributes with a type value of counter32.";
>
>
schema nodes. A default statement SHOULD NOT be used in combination with the type counter32.

In the value set and its semantics, this type is equivalent to the Counter32 type of the SMIv2.";

  reference
Changed:
<
<
"RFC 2578 (STD 58)";
>
>
"RFC 2578: Structure of Management Information Version 2 (SMIv2)";
  }

typedef zero-based-counter32 {

Line: 57 to 81
  default "0"; description "The zero-based-counter32 type represents a counter32
Changed:
<
<
which has the defined `initial' value zero.";
>
>
that has the defined 'initial' value zero.

A schema node of this type will be set to zero (0) on creation and will thereafter increase monotonically until it reaches a maximum value of 2^32-1 (4294967295 decimal), when it wraps around and starts increasing again from zero.

Provided that an application discovers a new schema node of this type within the minimum time to wrap, it can use the 'initial' value as a delta. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.

In the value set and its semantics, this type is equivalent to the ZeroBasedCounter32? textual convention of the SMIv2.";

  reference
Changed:
<
<
"RFC 2021";
>
>
"RFC 4502: Remote Network Monitoring Management Information Base Version 2";
  }

typedef counter64 { type uint64; description "The counter64 type represents a non-negative integer

Changed:
<
<
which monotonically increases until it reaches a maximum value of 2^64-1 (18446744073709551615), when it wraps around and starts increasing again from zero.
>
>
that monotonically increases until it reaches a maximum value of 2^64-1 (18446744073709551615 decimal), when it wraps around and starts increasing again from zero.
 
Changed:
<
<
Counters have no defined `initial' value, and thus, a
>
>
Counters have no defined 'initial' value, and thus, a
  single value of a counter has (in general) no information content. Discontinuities in the monotonically increasing value normally occur at re-initialization of the management system, and at other times as specified in the
Changed:
<
<
description of an object instance using this type. If such other times can occur, for example, the creation of an object instance of type counter64 at times other than re-initialization, then a corresponding object should be defined, with an appropriate type, to indicate the last discontinuity.
>
>
description of a schema node using this type. If such other times can occur, for example, the creation of a schema node of type counter64 at times other than re-initialization, then a corresponding schema node should be defined, with an appropriate type, to indicate the last discontinuity.
  The counter64 type should not be used for configuration
Changed:
<
<
objects. A default statement should not be used for attributes with a type value of counter64.";
>
>
schema nodes. A default statement SHOULD NOT be used in combination with the type counter64.

In the value set and its semantics, this type is equivalent to the Counter64 type of the SMIv2.";

  reference
Changed:
<
<
"RFC 2578 (STD 58)";
>
>
"RFC 2578: Structure of Management Information Version 2 (SMIv2)";
  }

typedef zero-based-counter64 { type yang:counter64; default "0"; description

Changed:
<
<
"The zero-based-counter64 type represents a counter64 which has the defined `initial' value zero.";
>
>
"The zero-based-counter64 type represents a counter64 that has the defined 'initial' value zero.

A schema node of this type will be set to zero (0) on creation and will thereafter increase monotonically until it reaches a maximum value of 2^64-1 (18446744073709551615 decimal), when it wraps around and starts increasing again from zero.

Provided that an application discovers a new schema node of this type within the minimum time to wrap, it can use the 'initial' value as a delta. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.

In the value set and its semantics, this type is equivalent to the ZeroBasedCounter64? textual convention of the SMIv2.";

  reference
Changed:
<
<
"RFC 2856";
>
>
"RFC 2856: Textual Conventions for Additional High Capacity Data Types";
  }

typedef gauge32 { type uint32; description

Changed:
<
<
"The gauge32 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than
        1. ^32-1 (4294967295 decimal), and the minimum value can not be smaller than 0. The value of a gauge32 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the gauge32 also decreases (increases).";
>
>
"The gauge32 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value cannot be greater than 2^32-1 (4294967295 decimal), and the minimum value cannot be smaller than 0. The value of a gauge32 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the gauge32 also decreases (increases).

In the value set and its semantics, this type is equivalent to the Gauge32 type of the SMIv2.";

  reference
Changed:
<
<
"RFC 2578 (STD 58)";
>
>
"RFC 2578: Structure of Management Information Version 2 (SMIv2)";
  }

typedef gauge64 { type uint64; description

Changed:
<
<
"The gauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than
        1. ^64-1 (18446744073709551615), and the minimum value can not be smaller than 0. The value of a gauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the gauge64 also decreases (increases)."; reference "RFC 2856"; }

/* * collection of identifier related types */

typedef uri { type string; description "A uri type represents Uniform Resource Identifier (URI) as defined by STD 66.

Objects using this type MUST be in US-ASCII encoding, and MUST be normalized as described by RFC 3986 Sections

        1. 2.1, 6.2.2.1, and 6.2.2.2. All unnecessary percent-encoding is removed, and all case-insensitive characters are set to lowercase except for hexadecimal digits, which are normalized to uppercase as described in Section 6.2.2.1.

The purpose of this normalization is to help provide unique URIs. Note that this normalization is not sufficient to provide uniqueness. Two URIs that are textually distinct after this normalization may still be equivalent.

Objects using this type MAY restrict the schemes that they permit. For example, 'data:' and 'urn:' schemes might not be appropriate.

A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required, for example when used as an index field.";

>
>
"The gauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value cannot be greater than 2^64-1 (18446744073709551615), and the minimum value cannot be smaller than 0. The value of a gauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the gauge64 also decreases (increases).

In the value set and its semantics, this type is equivalent to the CounterBasedGauge64? SMIv2 textual convention defined in RFC 2856";

  reference
Changed:
<
<
"RFC 3986 (STD 66), RFC 3305, and RFC 5017";
>
>
"RFC 2856: Textual Conventions for Additional High Capacity Data Types";
  }
Added:
>
>
/*** collection of identifier related types ***/
  typedef object-identifier { type string {
Changed:
<
<
pattern '[0-2](\.\d+)+';
>
>
pattern '(([0-1](\.[1-3]?[0-9]))|(2\.(0|([1-9]\d*))))' + '(\.(0|([1-9]\d*)))*';
  } description "The object-identifier type represents administratively
Line: 189 to 221
  are separated by single dots and without any intermediate white space.
Added:
>
>
The ASN.1 standard restricts the value space of the first sub-identifier to 0, 1, or 2. Furthermore, the value space of the second sub-identifier is restricted to the range
    1. to 39 if the first sub-identifier is 0 or 1. Finally, the ASN.1 standard requires that an object identifier has always at least two sub-identifier. The pattern captures these restrictions.
  Although the number of sub-identifiers is not limited, module designers should realize that there may be
Changed:
<
<
implementations that stick with the SMIv1/v2 limit of 128 sub-identifiers.";
>
>
implementations that stick with the SMIv2 limit of 128 sub-identifiers.

This type is a superset of the SMIv2 OBJECT IDENTIFIER type since it is not restricted to 128 sub-identifiers. Hence, this type SHOULD NOT be used to represent the SMIv2 OBJECT IDENTIFIER type, the object-identifier-128 type SHOULD be used instead.";

  reference
Changed:
<
<
"ITU-T Recommendation X.660 / ISO/IEC 9834-1";
>
>
"ISO9834-1: Information technology -- Open Systems Interconnection -- Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree";
  }
Changed:
<
<
/* * collection of date and time related types */
>
>
typedef object-identifier-128 { type object-identifier { pattern '\d*(\.\d*){1,127}'; } description "This type represents object-identifiers restricted to 128 sub-identifiers.

In the value set and its semantics, this type is equivalent to the OBJECT IDENTIFIER type of the SMIv2."; reference "RFC 2578: Structure of Management Information Version 2 (SMIv2)"; }

/*** collection of date and time related types ***/

  typedef date-and-time { type string {
Changed:
<
<
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.d*)?' + '(Z|(\+|-)\d{2}:\d{2})';
>
>
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?' + '(Z|[\+\-]\d{2}:\d{2})';
  } description
Changed:
<
<
'The date-and-time type is a profile of the ISO 8601
>
>
"The date-and-time type is a profile of the ISO 8601
  standard for representation of dates and times using the
Changed:
<
<
Gregorian calendar. The format is most easily described using the following ABFN (see RFC 3339):
>
>
Gregorian calendar. The profile is defined by the date-time production in Section 5.6 of RFC 3339.

The date-and-time type is compatible with the dateTime XML schema type with the following notable exceptions:

 
Changed:
<
<
date-fullyear = 4DIGIT date-month = 2DIGIT ; 01-12 date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31 time-hour = 2DIGIT ; 00-23 time-minute = 2DIGIT ; 00-59 time-second = 2DIGIT ; 00-58, 00-59, 00-60 time-secfrac = "." 1*DIGIT time-numoffset = ("+" / "-") time-hour ":" time-minute time-offset = "Z" / time-numoffset

partial-time = time-hour ":" time-minute ":" time-second [time-secfrac] full-date = date-fullyear "-" date-month "-" date-mday full-time = partial-time time-offset

>
>
(a) The date-and-time type does not allow negative years.
 
Changed:
<
<
date-time = full-date "T" full-time'; reference "RFC 3339";
>
>
(b) The date-and-time time-offset -00:00 indicates an unknown time zone (see RFC 3339) while -00:00 and +00:00 and Z all represent the same time zone in dateTime.

(c) The canonical format (see below) of data-and-time values differs from the canonical format used by the dateTime XML schema type, which requires all times to be in UTC using the time-offset 'Z'.

This type is not equivalent to the DateAndTime? textual convention of the SMIv2 since RFC 3339 uses a different separator between full-date and full-time and provides higher resolution of time-secfrac.

The canonical format for date-and-time values with a known time zone uses a numeric time zone offset that is calculated using the device's configured known offset to UTC time. A change of the device's offset to UTC time will cause date-and-time values to change accordingly. Such changes might happen periodically in case a server follows automatically daylight saving time (DST) time zone offset changes. The canonical format for date-and-time values with an unknown time zone (usually referring to the notion of local time) uses the time-offset -00:00."; reference "RFC 3339: Date and Time on the Internet: Timestamps RFC 2579: Textual Conventions for SMIv2

XSD-TYPES
XML Schema Part 2: Datatypes Second Edition";
  }

typedef timeticks { type uint32; description

Changed:
<
<
"The timeticks type represents a non-negative integer which represents the time, modulo 2^32 (4294967296 decimal), in hundredths of a second between two epochs. When objects are defined which use this type, the description of the object identifies both of the reference epochs.";
>
>
"The timeticks type represents a non-negative integer that represents the time, modulo 2^32 (4294967296 decimal), in hundredths of a second between two epochs. When a schema node is defined that uses this type, the description of the schema node identifies both of the reference epochs.

In the value set and its semantics, this type is equivalent to the TimeTicks? type of the SMIv2.";

  reference
Changed:
<
<
"RFC 2578 (STD 58)";
>
>
"RFC 2578: Structure of Management Information Version 2 (SMIv2)";
  }

typedef timestamp { type yang:timeticks; description "The timestamp type represents the value of an associated

Changed:
<
<
timeticks object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. When the specific occurrence occurred prior to the last time the associated timeticks attribute was zero, then the timestamp value is zero. Note that this requires all timestamp values to be reset to zero when the value of the associated timeticks attribute reaches 497+ days and wraps around to zero.

The associated timeticks object must be specified in the description of any object using this type."; reference "RFC 2579 (STD 58)"; }

/* * collection of generic address types */

>
>
timeticks schema node at which a specific occurrence happened. The specific occurrence must be defined in the description of any schema node defined using this type. When the specific occurrence occurred prior to the last time the associated timeticks attribute was zero, then the timestamp value is zero. Note that this requires all timestamp values to be reset to zero when the value of the associated timeticks attribute reaches 497+ days and wraps around to zero.

The associated timeticks schema node must be specified in the description of any schema node using this type.

In the value set and its semantics, this type is equivalent to the TimeStamp? textual convention of the SMIv2."; reference "RFC 2579: Textual Conventions for SMIv2"; }

/*** collection of generic address types ***/

  typedef phys-address {
Added:
>
>
type string { pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?'; } description "Represents media- or physical-level addresses represented as a sequence octets, each octet represented by two hexadecimal numbers. Octets are separated by colons. The canonical representation uses lowercase characters.

In the value set and its semantics, this type is equivalent to the PhysAddress? textual convention of the SMIv2."; reference "RFC 2579: Textual Conventions for SMIv2"; }

typedef mac-address { type string { pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}'; } description "The mac-address type represents an IEEE 802 MAC address. The canonical representation uses lowercase characters.

In the value set and its semantics, this type is equivalent to the MacAddress? textual convention of the SMIv2."; reference "IEEE 802: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture RFC 2579: Textual Conventions for SMIv2"; }

/*** collection of XML specific types ***/

typedef xpath1.0 {

  type string; description
Changed:
<
<
"Represents media- or physical-level addresses.";
>
>
"This type represents an XPATH 1.0 expression.

When a schema node is defined that uses this type, the description of the schema node MUST specify the XPath context in which the XPath expression is evaluated.";

  reference
Changed:
<
<
"RFC 2579 (STD 58)";
>
>
"XPATH: XML Path Language (XPath) Version 1.0";
  }
Added:
>
>
 } \ No newline at end of file

Revision 12007-11-15 - MartinBjoerklund

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="YangExamples"
module yang-types {

    // XXX namespace to be allocated by IANA

    namespace "urn:ietf:params:xml:ns:yang:yang-types";
    prefix "yang";

    organization
        "YANG Language Design Team";

    contact
        "Martin Bjorklund (Editor) ";

    description
        "This module contains standard derived YANG types.";

    revision 2007-10-02 {
        description "Initial revision.";
    }

    /*
     * collection of counter and gauge types
     */

    typedef counter32 {
        type uint32;
        description
           "The counter32 type represents a non-negative integer
            which monotonically increases until it reaches a
            maximum value of 2^32-1 (4294967295 decimal), when it
            wraps around and starts increasing again from zero.

            Counters have no defined `initial' value, and thus, a
            single value of a counter has (in general) no information
            content.  Discontinuities in the monotonically increasing
            value normally occur at re-initialization of the
            management system, and at other times as specified in the
            description of an object instance using this type.  If
            such other times can occur, for example, the creation of
            an object instance of type counter32 at times other than
            re-initialization, then a corresponding object should be
            defined, with an appropriate type, to indicate the last
            discontinuity.

            The counter32 type should not be used for configuration
            objects. A default statement should not be used for
            attributes with a type value of counter32.";
        reference
           "RFC 2578 (STD 58)";
    }

    typedef zero-based-counter32 {
        type yang:counter32;
        default "0";
        description
            "The zero-based-counter32 type represents a counter32
             which has the defined `initial' value zero.";
        reference
           "RFC 2021";
    }

    typedef counter64 {
        type uint64;
        description
           "The counter64 type represents a non-negative integer
            which monotonically increases until it reaches a
            maximum value of 2^64-1 (18446744073709551615), when
            it wraps around and starts increasing again from zero.

            Counters have no defined `initial' value, and thus, a
            single value of a counter has (in general) no information
            content.  Discontinuities in the monotonically increasing
            value normally occur at re-initialization of the
            management system, and at other times as specified in the
            description of an object instance using this type.  If
            such other times can occur, for example, the creation of
            an object instance of type counter64 at times other than
            re-initialization, then a corresponding object should be
            defined, with an appropriate type, to indicate the last
            discontinuity.

            The counter64 type should not be used for configuration
            objects. A default statement should not be used for
            attributes with a type value of counter64.";
        reference
           "RFC 2578 (STD 58)";
    }

    typedef zero-based-counter64 {
        type yang:counter64;
        default "0";
        description
            "The zero-based-counter64 type represents a counter64
             which has the defined `initial' value zero.";
        reference
           "RFC 2856";
    }

    typedef gauge32 {
        type uint32;
        description
           "The gauge32 type represents a non-negative integer,
            which may increase or decrease, but shall never
            exceed a maximum value, nor fall below a minimum
            value.  The maximum value can not be greater than
            2^32-1 (4294967295 decimal), and the minimum value
            can not be smaller than 0.  The value of a gauge32
            has its maximum value whenever the information
            being modeled is greater than or equal to its
            maximum value, and has its minimum value whenever
            the information being modeled is smaller than or
            equal to its minimum value.  If the information
            being modeled subsequently decreases below
            (increases above) the maximum (minimum) value, the
            gauge32 also decreases (increases).";
        reference
           "RFC 2578 (STD 58)";
    }

    typedef gauge64 {
        type uint64;
        description
           "The gauge64 type represents a non-negative integer,
            which may increase or decrease, but shall never
            exceed a maximum value, nor fall below a minimum
            value.  The maximum value can not be greater than
            2^64-1 (18446744073709551615), and the minimum value
            can not be smaller than 0.  The value of a gauge64
            has its maximum value whenever the information
            being modeled is greater than or equal to its
            maximum value, and has its minimum value whenever
            the information being modeled is smaller than or
            equal to its minimum value.  If the information
            being modeled subsequently decreases below
            (increases above) the maximum (minimum) value, the
            gauge64 also decreases (increases).";
        reference
           "RFC 2856";
    }

    /*
     * collection of identifier related types
     */

    typedef uri {
        type string;
        description
           "A uri type represents Uniform Resource Identifier (URI) 
            as defined by STD 66.

            Objects using this type MUST be in US-ASCII encoding, and
            MUST be normalized as described by RFC 3986 Sections
            6.2.1, 6.2.2.1, and 6.2.2.2.  All unnecessary
            percent-encoding is removed, and all case-insensitive
            characters are set to lowercase except for hexadecimal
            digits, which are normalized to uppercase as described in
            Section 6.2.2.1.

            The purpose of this normalization is to help provide unique
            URIs.  Note that this normalization is not sufficient to
            provide uniqueness.  Two URIs that are textually distinct
            after this normalization may still be equivalent.

            Objects using this type MAY restrict the schemes that they
            permit.  For example, 'data:' and 'urn:' schemes might not
            be appropriate.

            A zero-length URI is not a valid URI.  This can be used to
            express 'URI absent' where required, for example when used
            as an index field.";
        reference
           "RFC 3986 (STD 66), RFC 3305, and RFC 5017";
    }

    typedef object-identifier {
        type string {
            pattern '[0-2](\.\d+)+';
        }
        description
           "The object-identifier type represents administratively
            assigned names in a registration-hierarchical-name tree.
  
            Values of this type are denoted as a sequence of numerical
            non-negative sub-identifier values. Each sub-identifier
            value MUST NOT exceed 2^32-1 (4294967295). Sub-identifiers
            are separated by single dots and without any intermediate
            white space.

            Although the number of sub-identifiers is not limited,
            module designers should realize that there may be
            implementations that stick with the SMIv1/v2 limit of 128
            sub-identifiers.";
        reference
           "ITU-T Recommendation X.660 / ISO/IEC 9834-1";
    }

    /*
     * collection of date and time related types
     */

    typedef date-and-time {
        type string {
            pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.d*)?'
                  + '(Z|(\+|-)\d{2}:\d{2})';
        }
        description
           'The date-and-time type is a profile of the ISO 8601
            standard for representation of dates and times using the
            Gregorian calendar. The format is most easily described
            using the following ABFN (see RFC 3339):

            date-fullyear   = 4DIGIT
            date-month      = 2DIGIT  ; 01-12
            date-mday       = 2DIGIT  ; 01-28, 01-29, 01-30, 01-31
            time-hour       = 2DIGIT  ; 00-23
            time-minute     = 2DIGIT  ; 00-59
            time-second     = 2DIGIT  ; 00-58, 00-59, 00-60
            time-secfrac    = "." 1*DIGIT
            time-numoffset  = ("+" / "-") time-hour ":" time-minute
            time-offset     = "Z" / time-numoffset

            partial-time    = time-hour ":" time-minute ":" time-second
                              [time-secfrac]
            full-date       = date-fullyear "-" date-month "-" date-mday
            full-time       = partial-time time-offset

            date-time       = full-date "T" full-time';
        reference "RFC 3339";
    }
    
    typedef timeticks {
        type uint32;
        description
           "The timeticks type represents a non-negative integer
            which represents the time, modulo 2^32 (4294967296
            decimal), in hundredths of a second between two epochs.
            When objects are defined which use this type, the
            description of the object identifies both of the reference
            epochs.";
        reference
           "RFC 2578 (STD 58)";
    }

    typedef timestamp {
        type yang:timeticks;
        description
           "The timestamp type represents the value of an associated
            timeticks object at which a specific occurrence
            happened.  The specific occurrence must be defined in the
            description of any object defined using this type.  When
            the specific occurrence occurred prior to the last time
            the associated timeticks attribute was zero, then the
            timestamp value is zero.  Note that this requires all
            timestamp values to be reset to zero when the value of
            the associated timeticks attribute reaches 497+ days and
            wraps around to zero.

            The associated timeticks object must be specified
            in the description of any object using this type.";
        reference
           "RFC 2579 (STD 58)";
    }

    /*
     * collection of generic address types
     */

    typedef phys-address {
        type string;
        description
           "Represents media- or physical-level addresses.";
        reference 
           "RFC 2579 (STD 58)";
    }
}
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback