--- 1/draft-ietf-netmod-yang-types-07.txt 2010-04-14 15:11:25.000000000 +0200 +++ 2/draft-ietf-netmod-yang-types-08.txt 2010-04-14 15:11:25.000000000 +0200 @@ -1,18 +1,18 @@ Network Working Group J. Schoenwaelder, Ed. Internet-Draft Jacobs University -Intended status: Standards Track February 24, 2010 -Expires: August 28, 2010 +Intended status: Standards Track April 14, 2010 +Expires: October 16, 2010 Common YANG Data Types - draft-ietf-netmod-yang-types-07 + draft-ietf-netmod-yang-types-08 Abstract This document introduces a collection of common data types to be used with the YANG data modeling language. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. @@ -26,21 +26,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on August 28, 2010. + This Internet-Draft will expire on October 16, 2010. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -94,21 +94,22 @@ modeling all areas of management information. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119]. 2. Overview This section provides a short overview over the types defined in - subsequent sections and their equivalent SMIv2 data types. A YANG + subsequent sections and their equivalent Structure of Management + Information Version 2 (SMIv2) [RFC2578][RFC2579] data types. A YANG data type is equivalent to an SMIv2 data type if the data types have the same set of values and the semantics of the values are equivalent. Table 1 lists the types defined in the ietf-yang-types YANG module and the corresponding SMIv2 types (if any). ietf-yang-types +-----------------------+--------------------------------+ @@ -153,25 +154,25 @@ | ipv6-prefix | - | | domain-name | - | | host | - | | uri | Uri (URI-TC-MIB) | +-----------------+-----------------------------------------------+ Table 2 3. Core YANG Derived Types - file "ietf-yang-types@2010-02-03.yang" + file "ietf-yang-types@2010-04-14.yang" module ietf-yang-types { - namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types-DRAFT-06"; + namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types"; prefix "yang"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: WG Chair: David Partain @@ -194,28 +195,26 @@ 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 XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this note - // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netmod-yang-types-05.txt - - revision 2010-02-03 { + revision 2010-04-14 { description "Initial revision."; reference "RFC XXXX: Common YANG Data Types"; + } // RFC Ed.: replace XXXX with actual RFC number and remove this note /*** 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 @@ -228,43 +227,43 @@ value normally occur at re-initialization of the management system, and at other times as specified in the description of a schema node using this type. If such other times can occur, for example, the creation of an 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 - schema nodes. 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. This type is in the value set and its semantics equivalent to the Counter32 type of the SMIv2."; reference "RFC 2578: Structure of Management Information Version 2 (SMIv2)"; } 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. - Schema nodes of this type will be set to zero(0) on creation + 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 + 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. This type is in the value set and its semantics equivalent to the ZeroBasedCounter32 textual convention of the SMIv2."; reference "RFC 4502: Remote Network Monitoring Management Information Base Version 2 using SMIv2"; @@ -284,43 +283,43 @@ value normally occur at re-initialization of the management system, and at other times as specified in the 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 - schema nodes. 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. This type is in the value set and its semantics equivalent to the Counter64 type of the SMIv2."; reference "RFC 2578: Structure of Management Information Version 2 (SMIv2)"; } 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. - Schema nodes of this type will be set to zero(0) on creation + 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 + 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. This type is in the value set and its semantics equivalent to the ZeroBasedCounter64 textual convention of the SMIv2."; reference "RFC 2856: Textual Conventions for Additional High Capacity Data Types"; @@ -388,21 +387,24 @@ 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 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."; + 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 "ISO/IEC 9834-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"; } typedef object-identifier-128 { type object-identifier { pattern '\d*(\.\d*){1,127}'; @@ -568,25 +570,25 @@ reference "W3C REC-xpath-19991116: XML Path Language (XPath) Version 1.0"; } } 4. Internet Specific Derived Types - file "ietf-inet-types@2010-02-03.yang" + file "ietf-inet-types@2010-04-14.yang" module ietf-inet-types { - namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types-DRAFT-06"; + namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types"; prefix "inet"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: WG Chair: David Partain @@ -609,28 +611,26 @@ 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 XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this note - // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netmod-yang-types-05.txt - - revision 2010-02-03 { + revision 2010-04-14 { description "Initial revision."; reference "RFC XXXX: Common YANG Data Types"; + } // RFC Ed.: replace XXXX with actual RFC number and remove this note /*** collection of protocol field related types ***/ typedef ip-version { type enumeration { enum unknown { value "0"; description @@ -1050,21 +1051,21 @@ 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [YANG] Bjorklund, M., Ed., "YANG - A data modeling language for - NETCONF", draft-ietf-netmod-yang-10 (work in progress). + NETCONF", draft-ietf-netmod-yang-12 (work in progress). 9.2. Informative References [IDv6TREP] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 Address Text Representation", draft-ietf-6man-text-addr-representation-06 (work in progress). [IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area