draft-ietf-netmod-rfc6021-bis-03.txt   rfc6991.txt 
Network Working Group J. Schoenwaelder, Ed. Internet Engineering Task Force (IETF) J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Request for Comments: 6991 Jacobs University
Obsoletes: 6021 (if approved) May 16, 2013 Obsoletes: 6021 July 2013
Intended status: Standards Track Category: Standards Track
Expires: November 17, 2013 ISSN: 2070-1721
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-rfc6021-bis-03
Abstract Abstract
This document introduces a collection of common data types to be used This document introduces a collection of common data types to be used
with the YANG data modeling language. This document obsoletes RFC with the YANG data modeling language. This document obsoletes RFC
6021. 6021.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on November 17, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6991.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 14
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Overview ........................................................3
3. Core YANG Derived Types . . . . . . . . . . . . . . . . . . . 6 3. Core YANG Derived Types .........................................4
4. Internet-Specific Derived Types . . . . . . . . . . . . . . . 17 4. Internet-Specific Derived Types ................................14
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 5. IANA Considerations ............................................24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 6. Security Considerations ........................................25
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. Contributors ...................................................25
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 8. Acknowledgments ................................................25
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 9. References .....................................................26
9.1. Normative References . . . . . . . . . . . . . . . . . . . 31 9.1. Normative References ......................................26
9.2. Informative References . . . . . . . . . . . . . . . . . . 31 9.2. Informative References ....................................26
Appendix A. Changes from RFC 6021 . . . . . . . . . . . . . . . . 35 Appendix A. Changes from RFC 6021 ................................30
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
YANG [RFC6020] is a data modeling language used to model YANG [RFC6020] is a data modeling language used to model
configuration and state data manipulated by the Network Configuration configuration and state data manipulated by the Network Configuration
Protocol (NETCONF) [RFC6241]. The YANG language supports a small set Protocol (NETCONF) [RFC6241]. The YANG language supports a small set
of built-in data types and provides mechanisms to derive other types of built-in data types and provides mechanisms to derive other types
from the built-in types. from the built-in types.
This document introduces a collection of common data types derived This document introduces a collection of common data types derived
from the built-in YANG data types. The derived types are designed to from the built-in YANG data types. The derived types are designed to
be applicable for modeling all areas of management information. The be applicable for modeling all areas of management information. The
definitions are organized in several YANG modules. The definitions are organized in several YANG modules. The
"ietf-yang-types" module contains generally useful data types. The "ietf-yang-types" module contains generally useful data types. The
"ietf-inet-types" module contains definitions that are relevant for "ietf-inet-types" module contains definitions that are relevant for
the Internet protocol suite. the Internet protocol suite.
This version of the document adds new type definitions to the YANG This document adds new type definitions to the YANG modules and
modules and obsoletes [RFC6021]. For the further details, see the obsoletes [RFC6021]. For further details, see the revision
revision statement of the YANG modules. statements of the YANG modules in Sections 3 and 4 or the summary in
Appendix A.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119]. 14 [RFC2119].
2. Overview 2. Overview
This section provides a short overview of the types defined in This section provides a short overview of the types defined in
subsequent sections and their equivalent Structure of Management subsequent sections and their equivalent Structure of Management
skipping to change at page 6, line 11 skipping to change at page 4, line 39
+----------------------+--------------------------------------------+ +----------------------+--------------------------------------------+
Table 2: ietf-inet-types Table 2: ietf-inet-types
3. Core YANG Derived Types 3. Core YANG Derived Types
The ietf-yang-types YANG module references [IEEE802], [ISO9834-1], The ietf-yang-types YANG module references [IEEE802], [ISO9834-1],
[RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4122], [RFC4502], [RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4122], [RFC4502],
[RFC6020], [XPATH], and [XSD-TYPES]. [RFC6020], [XPATH], and [XSD-TYPES].
<CODE BEGINS> file "ietf-yang-types@2013-05-16.yang" <CODE BEGINS> file "ietf-yang-types@2013-07-15.yang"
module ietf-yang-types { module ietf-yang-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types";
prefix "yang"; prefix "yang";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
skipping to change at page 6, line 48 skipping to change at page 5, line 27
Copyright (c) 2013 IETF Trust and the persons identified as Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 6991; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2013-05-16 { revision 2013-07-15 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- yang-identifier - yang-identifier
- hex-string - hex-string
- uuid - uuid
- dotted-quad"; - dotted-quad";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
revision 2010-09-24 { revision 2010-09-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 6021: Common YANG Data Types"; "RFC 6021: Common YANG Data Types";
} }
/*** collection of counter and gauge types ***/ /*** collection of counter and gauge types ***/
skipping to change at page 10, line 38 skipping to change at page 9, line 22
gauge64 also decreases (increases). gauge64 also decreases (increases).
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the CounterBasedGauge64 SMIv2 textual convention defined to the CounterBasedGauge64 SMIv2 textual convention defined
in RFC 2856"; in RFC 2856";
reference reference
"RFC 2856: Textual Conventions for Additional High Capacity "RFC 2856: Textual Conventions for Additional High Capacity
Data Types"; Data Types";
} }
/*** collection of identifier related types ***/ /*** collection of identifier-related types ***/
typedef object-identifier { typedef object-identifier {
type string { type string {
pattern '(([0-1](\.[1-3]?[0-9]))|(2\.(0|([1-9]\d*))))' pattern '(([0-1](\.[1-3]?[0-9]))|(2\.(0|([1-9]\d*))))'
+ '(\.(0|([1-9]\d*)))*'; + '(\.(0|([1-9]\d*)))*';
} }
description description
"The object-identifier type represents administratively "The object-identifier type represents administratively
assigned names in a registration-hierarchical-name tree. assigned names in a registration-hierarchical-name tree.
skipping to change at page 11, line 12 skipping to change at page 9, line 44
non-negative sub-identifier values. Each sub-identifier non-negative sub-identifier values. Each sub-identifier
value MUST NOT exceed 2^32-1 (4294967295). Sub-identifiers value MUST NOT exceed 2^32-1 (4294967295). Sub-identifiers
are separated by single dots and without any intermediate are separated by single dots and without any intermediate
whitespace. whitespace.
The ASN.1 standard restricts the value space of the first The ASN.1 standard restricts the value space of the first
sub-identifier to 0, 1, or 2. Furthermore, the value space sub-identifier to 0, 1, or 2. Furthermore, the value space
of the second sub-identifier is restricted to the range of the second sub-identifier is restricted to the range
0 to 39 if the first sub-identifier is 0 or 1. Finally, 0 to 39 if the first sub-identifier is 0 or 1. Finally,
the ASN.1 standard requires that an object identifier the ASN.1 standard requires that an object identifier
has always at least two sub-identifier. The pattern has always at least two sub-identifiers. The pattern
captures these restrictions. captures these restrictions.
Although the number of sub-identifiers is not limited, Although the number of sub-identifiers is not limited,
module designers should realize that there may be module designers should realize that there may be
implementations that stick with the SMIv2 limit of 128 implementations that stick with the SMIv2 limit of 128
sub-identifiers. sub-identifiers.
This type is a superset of the SMIv2 OBJECT IDENTIFIER type This type is a superset of the SMIv2 OBJECT IDENTIFIER type
since it is not restricted to 128 sub-identifiers. Hence, since it is not restricted to 128 sub-identifiers. Hence,
this type SHOULD NOT be used to represent the SMIv2 OBJECT this type SHOULD NOT be used to represent the SMIv2 OBJECT
IDENTIFIER type, the object-identifier-128 type SHOULD be IDENTIFIER type; the object-identifier-128 type SHOULD be
used instead."; used instead.";
reference reference
"ISO9834-1: Information technology -- Open Systems "ISO9834-1: Information technology -- Open Systems
Interconnection -- Procedures for the operation of OSI Interconnection -- Procedures for the operation of OSI
Registration Authorities: General procedures and top Registration Authorities: General procedures and top
arcs of the ASN.1 Object Identifier tree"; arcs of the ASN.1 Object Identifier tree";
} }
typedef object-identifier-128 { typedef object-identifier-128 {
type object-identifier { type object-identifier {
skipping to change at page 12, line 4 skipping to change at page 10, line 37
reference reference
"RFC 2578: Structure of Management Information Version 2 "RFC 2578: Structure of Management Information Version 2
(SMIv2)"; (SMIv2)";
} }
typedef yang-identifier { typedef yang-identifier {
type string { type string {
length "1..max"; length "1..max";
pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*'; pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*';
pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*'; pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*';
} }
description description
"A YANG identifier string as defined in RFC 6020, page 163. "A YANG identifier string as defined by the 'identifier'
An identifier must start with an alphabetic character or rule in Section 12 of RFC 6020. An identifier must
an underscore followed by an arbitrary sequence of start with an alphabetic character or an underscore
alphabetic or numeric characters, underscores, hyphens followed by an arbitrary sequence of alphabetic or
or dots. numeric characters, underscores, hyphens, or dots.
A YANG identifier MUST NOT start with any possible A YANG identifier MUST NOT start with any possible
combination of the lower-case or upper-case character combination of the lowercase or uppercase character
sequence 'xml'."; sequence 'xml'.";
reference reference
"RFC 6020: YANG - A Data Modeling Language for the Network "RFC 6020: YANG - A Data Modeling Language for the Network
Configuration Protocol (NETCONF)"; Configuration Protocol (NETCONF)";
} }
/*** collection of types related to date and time***/
/*** collection of date and time related types ***/
typedef date-and-time { typedef date-and-time {
type string { type string {
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?' pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?'
+ '(Z|[\+\-]\d{2}:\d{2})'; + '(Z|[\+\-]\d{2}:\d{2})';
} }
description description
"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 standard for representation of dates and times using the
Gregorian calendar. The profile is defined by the Gregorian calendar. The profile is defined by the
date-time production in Section 5.6 of RFC 3339. date-time production in Section 5.6 of RFC 3339.
The date-and-time type is compatible with the dateTime XML The date-and-time type is compatible with the dateTime XML
schema type with the following notable exceptions: schema type with the following notable exceptions:
(a) The date-and-time type does not allow negative years. (a) The date-and-time type does not allow negative years.
(b) The date-and-time time-offset -00:00 indicates an unknown (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 time zone (see RFC 3339) while -00:00 and +00:00 and Z
represent the same time zone in dateTime. all represent the same time zone in dateTime.
(c) The canonical format (see below) of data-and-time values (c) The canonical format (see below) of data-and-time values
differs from the canonical format used by the dateTime XML differs from the canonical format used by the dateTime XML
schema type, which requires all times to be in UTC using schema type, which requires all times to be in UTC using
the time-offset 'Z'. the time-offset 'Z'.
This type is not equivalent to the DateAndTime textual This type is not equivalent to the DateAndTime textual
convention of the SMIv2 since RFC 3339 uses a different convention of the SMIv2 since RFC 3339 uses a different
separator between full-date and full-time and provides separator between full-date and full-time and provides
higher resolution of time-secfrac. higher resolution of time-secfrac.
skipping to change at page 13, line 42 skipping to change at page 12, line 25
reference reference
"RFC 2578: Structure of Management Information Version 2 "RFC 2578: Structure of Management Information Version 2
(SMIv2)"; (SMIv2)";
} }
typedef timestamp { typedef timestamp {
type yang:timeticks; type yang:timeticks;
description description
"The timestamp type represents the value of an associated "The timestamp type represents the value of an associated
timeticks schema node at which a specific occurrence timeticks schema node at which a specific occurrence
happened. The specific occurrence must be defined in the happened. The specific occurrence must be defined in the
description of any schema node defined using this type. When description of any schema node defined using this type. When
the specific occurrence occurred prior to the last time the the specific occurrence occurred prior to the last time the
associated timeticks attribute was zero, then the timestamp associated timeticks attribute was zero, then the timestamp
value is zero. Note that this requires all timestamp values value is zero. Note that this requires all timestamp values
to be reset to zero when the value of the associated timeticks to be reset to zero when the value of the associated timeticks
attribute reaches 497+ days and wraps around to zero. attribute reaches 497+ days and wraps around to zero.
The associated timeticks schema node must be specified The associated timeticks schema node must be specified
in the description of any schema node using this type. in the description of any schema node using this type.
skipping to change at page 14, line 45 skipping to change at page 13, line 32
The canonical representation uses lowercase characters. The canonical representation uses lowercase characters.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the MacAddress textual convention of the SMIv2."; to the MacAddress textual convention of the SMIv2.";
reference reference
"IEEE 802: IEEE Standard for Local and Metropolitan Area "IEEE 802: IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture Networks: Overview and Architecture
RFC 2579: Textual Conventions for SMIv2"; RFC 2579: Textual Conventions for SMIv2";
} }
/*** collection of XML specific types ***/ /*** collection of XML-specific types ***/
typedef xpath1.0 { typedef xpath1.0 {
type string; type string;
description description
"This type represents an XPATH 1.0 expression. "This type represents an XPATH 1.0 expression.
When a schema node is defined that uses this type, the When a schema node is defined that uses this type, the
description of the schema node MUST specify the XPath description of the schema node MUST specify the XPath
context in which the XPath expression is evaluated."; context in which the XPath expression is evaluated.";
reference reference
skipping to change at page 17, line 13 skipping to change at page 15, line 5
<CODE ENDS> <CODE ENDS>
4. Internet-Specific Derived Types 4. Internet-Specific Derived Types
The ietf-inet-types YANG module references [RFC0768], [RFC0791], The ietf-inet-types YANG module references [RFC0768], [RFC0791],
[RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460], [RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460],
[RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3595], [RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3595],
[RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC4340], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC4340],
[RFC4960], [RFC5017], [RFC5890], [RFC5952], and [RFC6793]. [RFC4960], [RFC5017], [RFC5890], [RFC5952], and [RFC6793].
<CODE BEGINS> file "ietf-inet-types@2013-05-16.yang" <CODE BEGINS> file "ietf-inet-types@2013-07-15.yang"
module ietf-inet-types { module ietf-inet-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types";
prefix "inet"; prefix "inet";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
skipping to change at page 17, line 50 skipping to change at page 15, line 42
Copyright (c) 2013 IETF Trust and the persons identified as Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 6991; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2013-05-16 { revision 2013-07-15 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- ip-address-no-zone - ip-address-no-zone
- ipv4-address-no-zone - ipv4-address-no-zone
- ipv6-address-no-zone"; - ipv6-address-no-zone";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
revision 2010-09-24 { revision 2010-09-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 6021: Common YANG Data Types"; "RFC 6021: Common YANG Data Types";
} }
/*** collection of protocol field related types ***/ /*** collection of types related to protocol fields ***/
typedef ip-version { typedef ip-version {
type enumeration { type enumeration {
enum unknown { enum unknown {
value "0"; value "0";
description description
"An unknown or unspecified version of the Internet "An unknown or unspecified version of the Internet
protocol."; protocol.";
} }
enum ipv4 { enum ipv4 {
skipping to change at page 19, line 4 skipping to change at page 16, line 45
description description
"This value represents the version of the IP protocol. "This value represents the version of the IP protocol.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the InetVersion textual convention of the SMIv2."; to the InetVersion textual convention of the SMIv2.";
reference reference
"RFC 791: Internet Protocol "RFC 791: Internet Protocol
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
RFC 4001: Textual Conventions for Internet Network Addresses"; RFC 4001: Textual Conventions for Internet Network Addresses";
} }
typedef dscp { typedef dscp {
type uint8 { type uint8 {
range "0..63"; range "0..63";
} }
description description
"The dscp type represents a Differentiated Services Code-Point "The dscp type represents a Differentiated Services Code Point
that may be used for marking packets in a traffic stream. that may be used for marking packets in a traffic stream.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the Dscp textual convention of the SMIv2."; to the Dscp textual convention of the SMIv2.";
reference reference
"RFC 3289: Management Information Base for the Differentiated "RFC 3289: Management Information Base for the Differentiated
Services Architecture Services Architecture
RFC 2474: Definition of the Differentiated Services Field RFC 2474: Definition of the Differentiated Services Field
(DS Field) in the IPv4 and IPv6 Headers (DS Field) in the IPv4 and IPv6 Headers
RFC 2780: IANA Allocation Guidelines For Values In RFC 2780: IANA Allocation Guidelines For Values In
the Internet Protocol and Related Headers"; the Internet Protocol and Related Headers";
} }
typedef ipv6-flow-label { typedef ipv6-flow-label {
type uint32 { type uint32 {
range "0..1048575"; range "0..1048575";
} }
description description
"The flow-label type represents flow identifier or Flow Label "The ipv6-flow-label type represents the flow identifier or Flow
in an IPv6 packet header that may be used to discriminate Label in an IPv6 packet header that may be used to
traffic flows. discriminate traffic flows.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the IPv6FlowLabel textual convention of the SMIv2."; to the IPv6FlowLabel textual convention of the SMIv2.";
reference reference
"RFC 3595: Textual Conventions for IPv6 Flow Label "RFC 3595: Textual Conventions for IPv6 Flow Label
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification"; RFC 2460: Internet Protocol, Version 6 (IPv6) Specification";
} }
typedef port-number { typedef port-number {
type uint16 { type uint16 {
range "0..65535"; range "0..65535";
} }
description description
"The port-number type represents a 16-bit port number of an "The port-number type represents a 16-bit port number of an
Internet transport layer protocol such as UDP, TCP, DCCP, or Internet transport-layer protocol such as UDP, TCP, DCCP, or
SCTP. Port numbers are assigned by IANA. A current list of SCTP. Port numbers are assigned by IANA. A current list of
all assignments is available from <http://www.iana.org/>. all assignments is available from <http://www.iana.org/>.
Note that the port number value zero is reserved by IANA. In Note that the port number value zero is reserved by IANA. In
situations where the value zero does not make sense, it can situations where the value zero does not make sense, it can
be excluded by subtyping the port-number type. be excluded by subtyping the port-number type.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the InetPortNumber textual convention of the SMIv2."; to the InetPortNumber textual convention of the SMIv2.";
reference reference
"RFC 768: User Datagram Protocol "RFC 768: User Datagram Protocol
RFC 793: Transmission Control Protocol RFC 793: Transmission Control Protocol
RFC 4960: Stream Control Transmission Protocol RFC 4960: Stream Control Transmission Protocol
RFC 4340: Datagram Congestion Control Protocol (DCCP) RFC 4340: Datagram Congestion Control Protocol (DCCP)
RFC 4001: Textual Conventions for Internet Network Addresses"; RFC 4001: Textual Conventions for Internet Network Addresses";
} }
/*** collection of autonomous system related types ***/ /*** collection of types related to autonomous systems ***/
typedef as-number { typedef as-number {
type uint32; type uint32;
description description
"The as-number type represents autonomous system numbers "The as-number type represents autonomous system numbers
which identify an Autonomous System (AS). An AS is a set which identify an Autonomous System (AS). An AS is a set
of routers under a single technical administration, using of routers under a single technical administration, using
an interior gateway protocol and common metrics to route an interior gateway protocol and common metrics to route
packets within the AS, and using an exterior gateway packets within the AS, and using an exterior gateway
protocol to route packets to other ASs'. IANA maintains protocol to route packets to other ASes. IANA maintains
the AS number space and has delegated large parts to the the AS number space and has delegated large parts to the
regional registries. regional registries.
Autonomous system numbers were originally limited to 16 Autonomous system numbers were originally limited to 16
bits. BGP extensions have enlarged the autonomous system bits. BGP extensions have enlarged the autonomous system
number space to 32 bits. This type therefore uses an uint32 number space to 32 bits. This type therefore uses an uint32
base type without a range restriction in order to support base type without a range restriction in order to support
a larger autonomous system number space. a larger autonomous system number space.
In the value set and its semantics, this type is equivalent In the value set and its semantics, this type is equivalent
to the InetAutonomousSystemNumber textual convention of to the InetAutonomousSystemNumber textual convention of
the SMIv2."; the SMIv2.";
reference reference
"RFC 1930: Guidelines for creation, selection, and registration "RFC 1930: Guidelines for creation, selection, and registration
of an Autonomous System (AS) of an Autonomous System (AS)
RFC 4271: A Border Gateway Protocol 4 (BGP-4) RFC 4271: A Border Gateway Protocol 4 (BGP-4)
RFC 4001: Textual Conventions for Internet Network Addresses RFC 4001: Textual Conventions for Internet Network Addresses
RFC 6793: BGP Support for Four-octet AS Number Space"; RFC 6793: BGP Support for Four-Octet Autonomous System (AS)
Number Space";
} }
/*** collection of IP address and hostname related types ***/ /*** collection of types related to IP addresses and hostnames ***/
typedef ip-address { typedef ip-address {
type union { type union {
type inet:ipv4-address; type inet:ipv4-address;
type inet:ipv6-address; type inet:ipv6-address;
} }
description description
"The ip-address type represents an IP address and is IP "The ip-address type represents an IP address and is IP
version neutral. The format of the textual representation version neutral. The format of the textual representation
implies the IP version. This type supports scoped addresses implies the IP version. This type supports scoped addresses
skipping to change at page 22, line 10 skipping to change at page 20, line 6
mixed, shortened, and shortened-mixed notation. The IPv6 mixed, shortened, and shortened-mixed notation. The IPv6
address may include a zone index, separated by a % sign. address may include a zone index, separated by a % sign.
The zone index is used to disambiguate identical address The zone index is used to disambiguate identical address
values. For link-local addresses, the zone index will values. For link-local addresses, the zone index will
typically be the interface index number or the name of an typically be the interface index number or the name of an
interface. If the zone index is not present, the default interface. If the zone index is not present, the default
zone of the device will be used. zone of the device will be used.
The canonical format of IPv6 addresses uses the textual The canonical format of IPv6 addresses uses the textual
representation defined in Section 4 of RFC 5952. The representation defined in Section 4 of RFC 5952. The
canonical format for the zone index is the numerical canonical format for the zone index is the numerical
format as described in Section 11.2 of RFC 4007."; format as described in Section 11.2 of RFC 4007.";
reference reference
"RFC 4291: IP Version 6 Addressing Architecture "RFC 4291: IP Version 6 Addressing Architecture
RFC 4007: IPv6 Scoped Address Architecture RFC 4007: IPv6 Scoped Address Architecture
RFC 5952: A Recommendation for IPv6 Address Text RFC 5952: A Recommendation for IPv6 Address Text
Representation"; Representation";
} }
typedef ip-address-no-zone { typedef ip-address-no-zone {
skipping to change at page 22, line 40 skipping to change at page 20, line 36
address format."; address format.";
reference reference
"RFC 4007: IPv6 Scoped Address Architecture"; "RFC 4007: IPv6 Scoped Address Architecture";
} }
typedef ipv4-address-no-zone { typedef ipv4-address-no-zone {
type inet:ipv4-address { type inet:ipv4-address {
pattern '[0-9\.]*'; pattern '[0-9\.]*';
} }
description description
"An IPv4 address without a zone index. This type derived from "An IPv4 address without a zone index. This type, derived from
ipv4-address may be used in situations where the zone is known ipv4-address, may be used in situations where the zone is
from the context and hence no zone index is needed."; known from the context and hence no zone index is needed.";
} }
typedef ipv6-address-no-zone { typedef ipv6-address-no-zone {
type inet:ipv6-address { type inet:ipv6-address {
pattern '[0-9a-fA-F:\.]*'; pattern '[0-9a-fA-F:\.]*';
} }
description description
"An IPv6 address without a zone index. This type derived from "An IPv6 address without a zone index. This type, derived from
ipv6-address may be used in situations where the zone is known ipv6-address, may be used in situations where the zone is
from the context and hence no zone index is needed."; known from the context and hence no zone index is needed.";
reference reference
"RFC 4291: IP Version 6 Addressing Architecture "RFC 4291: IP Version 6 Addressing Architecture
RFC 4007: IPv6 Scoped Address Architecture RFC 4007: IPv6 Scoped Address Architecture
RFC 5952: A Recommendation for IPv6 Address Text RFC 5952: A Recommendation for IPv6 Address Text
Representation"; Representation";
} }
typedef ip-prefix { typedef ip-prefix {
type union { type union {
type inet:ipv4-prefix; type inet:ipv4-prefix;
skipping to change at page 24, line 10 skipping to change at page 22, line 7
+ '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}' + '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}'
+ '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))' + '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))'
+ '(/(([0-9])|([0-9]{2})|(1[0-1][0-9])|(12[0-8])))'; + '(/(([0-9])|([0-9]{2})|(1[0-1][0-9])|(12[0-8])))';
pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|' pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|'
+ '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)' + '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)'
+ '(/.+)'; + '(/.+)';
} }
description description
"The ipv6-prefix type represents an IPv6 address prefix. "The ipv6-prefix type represents an IPv6 address prefix.
The prefix length is given by the number following the The prefix length is given by the number following the
slash character and must be less than or equal 128. slash character and must be less than or equal to 128.
A prefix length value of n corresponds to an IP address A prefix length value of n corresponds to an IP address
mask that has n contiguous 1-bits from the most mask that has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0. significant bit (MSB) and all other bits set to 0.
The IPv6 address should have all bits that do not belong The IPv6 address should have all bits that do not belong
to the prefix set to zero. to the prefix set to zero.
The canonical format of an IPv6 prefix has all bits of The canonical format of an IPv6 prefix has all bits of
the IPv6 address set to zero that are not part of the the IPv6 address set to zero that are not part of the
skipping to change at page 25, line 19 skipping to change at page 23, line 17
prefixed by a length bytes and there is a trailing NULL prefixed by a length bytes and there is a trailing NULL
byte, only 253 characters can appear in the textual dotted byte, only 253 characters can appear in the textual dotted
notation. notation.
The description clause of schema nodes using the domain-name The description clause of schema nodes using the domain-name
type MUST describe when and how these names are resolved to type MUST describe when and how these names are resolved to
IP addresses. Note that the resolution of a domain-name value IP addresses. Note that the resolution of a domain-name value
may require to query multiple DNS records (e.g., A for IPv4 may require to query multiple DNS records (e.g., A for IPv4
and AAAA for IPv6). The order of the resolution process and and AAAA for IPv6). The order of the resolution process and
which DNS record takes precedence can either be defined which DNS record takes precedence can either be defined
explicitely or it may depend on the configuration of the explicitly or may depend on the configuration of the
resolver. resolver.
Domain-name values use the US-ASCII encoding. Their canonical Domain-name values use the US-ASCII encoding. Their canonical
format uses lowercase US-ASCII characters. Internationalized format uses lowercase US-ASCII characters. Internationalized
domain names MUST be A-labels as per RFC 5890."; domain names MUST be A-labels as per RFC 5890.";
reference reference
"RFC 952: DoD Internet Host Table Specification "RFC 952: DoD Internet Host Table Specification
RFC 1034: Domain Names - Concepts and Facilities RFC 1034: Domain Names - Concepts and Facilities
RFC 1123: Requirements for Internet Hosts -- Application RFC 1123: Requirements for Internet Hosts -- Application
and Support and Support
RFC 2782: A DNS RR for specifying the location of services RFC 2782: A DNS RR for specifying the location of services
(DNS SRV) (DNS SRV)
RFC 5890: Internationalizing Domain Names in Applications RFC 5890: Internationalized Domain Names in Applications
(IDNA): Definitions and Document Framework"; (IDNA): Definitions and Document Framework";
} }
typedef host { typedef host {
type union { type union {
type inet:ip-address; type inet:ip-address;
type inet:domain-name; type inet:domain-name;
} }
description description
"The host type represents either an IP address or a DNS "The host type represents either an IP address or a DNS
skipping to change at page 27, line 25 skipping to change at page 25, line 11
URI: urn:ietf:params:xml:ns:yang:ietf-inet-types URI: urn:ietf:params:xml:ns:yang:ietf-inet-types
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers two YANG modules in the YANG Module Names This document registers two YANG modules in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-yang-types name: ietf-yang-types
namespace: urn:ietf:params:xml:ns:yang:ietf-yang-types namespace: urn:ietf:params:xml:ns:yang:ietf-yang-types
prefix: yang prefix: yang
reference: RFC XXXX reference: RFC 6991
name: ietf-inet-types name: ietf-inet-types
namespace: urn:ietf:params:xml:ns:yang:ietf-inet-types namespace: urn:ietf:params:xml:ns:yang:ietf-inet-types
prefix: inet prefix: inet
reference: RFC XXXX reference: RFC 6991
6. Security Considerations 6. Security Considerations
This document defines common data types using the YANG data modeling This document defines common data types using the YANG data modeling
language. The definitions themselves have no security impact on the language. The definitions themselves have no security impact on the
Internet but the usage of these definitions in concrete YANG modules Internet, but the usage of these definitions in concrete YANG modules
might have. The security considerations spelled out in the YANG might have. The security considerations spelled out in the YANG
specification [RFC6020] apply for this document as well. specification [RFC6020] apply for this document as well.
7. Contributors 7. Contributors
The following people contributed significantly to the initial version The following people contributed significantly to the initial version
of this document: of this document:
- Andy Bierman (Brocade) - Andy Bierman (Brocade)
- Martin Bjorklund (Tail-f Systems) - Martin Bjorklund (Tail-f Systems)
skipping to change at page 31, line 9 skipping to change at page 26, line 9
Lars-Johan Liman, and Dan Romascanu. Lars-Johan Liman, and Dan Romascanu.
Juergen Schoenwaelder was partly funded by Flamingo, a Network of Juergen Schoenwaelder was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme. under its Seventh Framework Programme.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002. Internet: Timestamps", RFC 3339, July 2002.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005. March 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
July 2005. July 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)
Version 1.0", World Wide Web Consortium Version 1.0", World Wide Web Consortium
Recommendation REC-xpath-19991116, November 1999, Recommendation REC-xpath-19991116, November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>. <http://www.w3.org/TR/1999/REC-xpath-19991116>.
9.2. Informative References 9.2. Informative References
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area [IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE Std. 802-2001. Networks: Overview and Architecture", IEEE Std. 802-
2001, 2001.
[ISO9834-1] [ISO9834-1] ISO/IEC, "Information technology -- Open Systems
ISO/IEC, "Information technology -- Open Systems Interconnection -- Procedures for the operation of OSI
Interconnection -- Procedures for the operation of OSI Registration Authorities: General procedures and top
Registration Authorities: General procedures and top arcs arcs of the ASN.1 Object Identifier tree", ISO/
of the ASN.1 Object Identifier tree", ISO/IEC 9834-1:2008, IEC 9834-1:2008, 2008.
2008.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, September 1981. RFC 793, September 1981.
[RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet [RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD
host table specification", RFC 952, October 1985. Internet host table specification", RFC 952,
October 1985.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and
STD 13, RFC 1034, November 1987. facilities", STD 13, RFC 1034, November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application [RFC1123] Braden, R., "Requirements for Internet Hosts -
and Support", STD 3, RFC 1123, October 1989. Application and Support", STD 3, RFC 1123, October 1989.
[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,
selection, and registration of an Autonomous System (AS)", selection, and registration of an Autonomous System
BCP 6, RFC 1930, March 1996. (AS)", BCP 6, RFC 1930, March 1996.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
December 1998. December 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines
Values In the Internet Protocol and Related Headers", For Values In the Internet Protocol and Related
BCP 37, RFC 2780, March 2000. Headers", BCP 37, RFC 2780, March 2000.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)",
February 2000. RFC 2782, February 2000.
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types", Conventions for Additional High Capacity Data Types",
RFC 2856, June 2000. RFC 2856, June 2000.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information [RFC3289] Baker, F., Chan, K., and A. Smith, "Management
Base for the Differentiated Services Architecture", Information Base for the Differentiated Services
RFC 3289, May 2002. Architecture", RFC 3289, May 2002.
[RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint W3C/ [RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint
IETF URI Planning Interest Group: Uniform Resource W3C/IETF URI Planning Interest Group: Uniform Resource
Identifiers (URIs), URLs, and Uniform Resource Names Identifiers (URIs), URLs, and Uniform Resource Names
(URNs): Clarifications and Recommendations", RFC 3305, (URNs): Clarifications and Recommendations", RFC 3305,
August 2002. August 2002.
[RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label", [RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label",
RFC 3595, September 2003. RFC 3595, September 2003.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Congestion Control Protocol (DCCP)", RFC 4340,
March 2006.
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management [RFC4502] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2", RFC 4502, May 2006. Information Base Version 2", RFC 4502, May 2006.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC5017] McWalter, D., "MIB Textual Conventions for Uniform [RFC5017] McWalter, D., "MIB Textual Conventions for Uniform
Resource Identifiers (URIs)", RFC 5017, September 2007. Resource Identifiers (URIs)", RFC 5017, September 2007.
[RFC5890] Klensin, J., "Internationalizing Domain Names in [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document
RFC 5890, August 2010. Framework", RFC 5890, August 2010.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for
Address Text Representation", RFC 5952, August 2010. IPv6 Address Text Representation", RFC 5952,
August 2010.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010. October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.,
and A. Bierman, Ed., "NETCONF Configuration Protocol Ed., and A. Bierman, Ed., "Network Configuration
(NETCONF)", RFC 6241, June 2011. Protocol (NETCONF)", RFC 6241, June 2011.
[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
Autonomous System (AS) Number Space", RFC 6793, Autonomous System (AS) Number Space", RFC 6793,
December 2012. December 2012.
[XSD-TYPES] [XSD-TYPES] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium
Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004,
Recommendation REC-xmlschema-2-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
Appendix A. Changes from RFC 6021 Appendix A. Changes from RFC 6021
This version adds new type definitions to the YANG modules. The This version adds new type definitions to the YANG modules. The
following new data types have been added to the ietf-yang-types following new data types have been added to the ietf-yang-types
module: module:
o yang-identifier o yang-identifier
o hex-string o hex-string
skipping to change at page 36, line 10 skipping to change at page 30, line 33
o ipv4-address-no-zone o ipv4-address-no-zone
o ipv6-address-no-zone o ipv6-address-no-zone
Author's Address Author's Address
Juergen Schoenwaelder (editor) Juergen Schoenwaelder (editor)
Jacobs University Jacobs University
Email: j.schoenwaelder@jacobs-university.de EMail: j.schoenwaelder@jacobs-university.de
 End of changes. 87 change blocks. 
192 lines changed or deleted 191 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/