draft-ietf-netmod-yang-types-09.txt   rfc6021.txt 
Network Working Group J. Schoenwaelder, Ed. Internet Engineering Task Force (IETF) J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Request for Comments: 6021 Jacobs University
Intended status: Standards Track April 26, 2010 Category: Standards Track October 2010
Expires: October 28, 2010 ISSN: 2070-1721
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-yang-types-09
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. with the YANG data modeling language.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
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 This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on October 28, 2010. 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/rfc6021.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 22 skipping to change at page 2, line 19
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 . . . . . . . . . . . . . . . 15 4. Internet-Specific Derived Types ................................13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 5. IANA Considerations ............................................22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 25 6. Security Considerations ........................................23
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 26 7. Contributors ...................................................23
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 8. Acknowledgments ................................................23
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. References .....................................................23
9.1. Normative References . . . . . . . . . . . . . . . . . . . 28 9.1. Normative References ......................................23
9.2. Informative References . . . . . . . . . . . . . . . . . . 28 9.2. Informative References ....................................24
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
YANG [YANG] is a data modeling language used to model configuration YANG [RFC6020] is a data modeling language used to model
and state data manipulated by the NETCONF [RFC4741] protocol. The configuration and state data manipulated by the Network Configuration
YANG language supports a small set of built-in data types and Protocol (NETCONF) [RFC4741]. The YANG language supports a small set
provides mechanisms to derive other types from the built-in types. of built-in data types and provides mechanisms to derive other 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 definitions are organized in from the built-in YANG data types. The definitions are organized in
several YANG modules. The "ietf-yang-types" module contains several YANG modules. The "ietf-yang-types" module contains
generally useful data types. The "ietf-inet-types" module contains generally useful data types. The "ietf-inet-types" module contains
definitions that are relevant for the Internet protocol suite. definitions that are relevant for the Internet protocol suite.
The derived types are generally designed to be applicable for The derived types are generally designed to be applicable for
modeling all areas of management information. modeling all areas of management information.
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
Information Version 2 (SMIv2) [RFC2578][RFC2579] data types. A YANG Information Version 2 (SMIv2) [RFC2578][RFC2579] data types. A YANG
data type is equivalent to an SMIv2 data type if the data types have 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 the same set of values and the semantics of the values are
equivalent. equivalent.
skipping to change at page 6, line 7 skipping to change at page 4, line 33
| ipv6-prefix | - | | ipv6-prefix | - |
| domain-name | - | | domain-name | - |
| host | - | | host | - |
| uri | Uri (URI-TC-MIB) | | uri | Uri (URI-TC-MIB) |
+-----------------+-----------------------------------------------+ +-----------------+-----------------------------------------------+
Table 2 Table 2
3. Core YANG Derived Types 3. Core YANG Derived Types
<CODE BEGINS> file "ietf-yang-types@2010-04-24.yang" The ietf-yang-types YANG module references [IEEE802], [ISO9834-1],
[RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4502], [XPATH], and
[XSD-TYPES].
<CODE BEGINS> file "ietf-yang-types@2010-09-24.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 35 skipping to change at page 5, line 16
<mailto:david.kessens@nsn.com> <mailto:david.kessens@nsn.com>
Editor: Juergen Schoenwaelder Editor: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>"; <mailto:j.schoenwaelder@jacobs-university.de>";
description description
"This module contains a collection of generally useful derived "This module contains a collection of generally useful derived
YANG data types. YANG data types.
Copyright (c) 2010 IETF Trust and the persons identified as Copyright (c) 2010 IETF Trust and the persons identified as
the document authors. 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
without modification, is permitted pursuant to, and subject modification, is permitted pursuant to, and subject to the license
to the license terms contained in, the Simplified BSD License terms contained in, the Simplified BSD License set forth in Section
set forth in Section 4.c of the IETF Trust's Legal Provisions 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 6021; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this note
revision 2010-04-24 { revision 2010-09-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC 6021: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note
/*** collection of counter and gauge types ***/ /*** collection of counter and gauge types ***/
typedef counter32 { typedef counter32 {
type uint32; type uint32;
description description
"The counter32 type represents a non-negative integer "The counter32 type represents a non-negative integer
which monotonically increases until it reaches a that monotonically increases until it reaches a
maximum value of 2^32-1 (4294967295 decimal), when it maximum value of 2^32-1 (4294967295 decimal), when it
wraps around and starts increasing again from zero. wraps around and starts increasing again from zero.
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 single value of a counter has (in general) no information
content. Discontinuities in the monotonically increasing content. Discontinuities in the monotonically increasing
value normally occur at re-initialization of the value normally occur at re-initialization of the
management system, and at other times as specified in the management system, and at other times as specified in the
description of a schema node using this type. If such description of a schema node using this type. If such
other times can occur, for example, the creation of an other times can occur, for example, the creation of
a schema node of type counter32 at times other than a schema node of type counter32 at times other than
re-initialization, then a corresponding schema node re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate should be defined, with an appropriate type, to indicate
the last discontinuity. the last discontinuity.
The counter32 type should not be used for configuration The counter32 type should not be used for configuration
schema nodes. A default statement SHOULD NOT be used in schema nodes. A default statement SHOULD NOT be used in
combination with the type counter32. combination with the type counter32.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the Counter32 type of the SMIv2."; to the Counter32 type of the SMIv2.";
reference reference
"RFC 2578: Structure of Management Information Version 2 (SMIv2)"; "RFC 2578: Structure of Management Information Version 2 (SMIv2)";
} }
typedef zero-based-counter32 { typedef zero-based-counter32 {
type yang:counter32; type yang:counter32;
default "0"; default "0";
description description
"The zero-based-counter32 type represents a counter32 "The zero-based-counter32 type represents a counter32
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 A schema node of this type will be set to zero (0) on creation
and will thereafter increase monotonically until it reaches and will thereafter increase monotonically until it reaches
a maximum value of 2^32-1 (4294967295 decimal), when it a maximum value of 2^32-1 (4294967295 decimal), when it
wraps around and starts increasing again from zero. wraps around and starts increasing again from zero.
Provided that an application discovers a new schema node 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 'initial' value as a delta. It is important for a management
station to be aware of this minimum time and the actual time station to be aware of this minimum time and the actual time
between polls, and to discard data if the actual time is too between polls, and to discard data if the actual time is too
long or there is no defined minimum time. long or there is no defined minimum time.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the ZeroBasedCounter32 textual convention of the SMIv2."; to the ZeroBasedCounter32 textual convention of the SMIv2.";
reference reference
"RFC 4502: Remote Network Monitoring Management Information "RFC 4502: Remote Network Monitoring Management Information
Base Version 2 using SMIv2"; Base Version 2";
} }
typedef counter64 { typedef counter64 {
type uint64; type uint64;
description description
"The counter64 type represents a non-negative integer "The counter64 type represents a non-negative integer
which monotonically increases until it reaches a that monotonically increases until it reaches a
maximum value of 2^64-1 (18446744073709551615 decimal), maximum value of 2^64-1 (18446744073709551615 decimal),
when it wraps around and starts increasing again from zero. when it wraps around and starts increasing again from zero.
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 single value of a counter has (in general) no information
content. Discontinuities in the monotonically increasing content. Discontinuities in the monotonically increasing
value normally occur at re-initialization of the value normally occur at re-initialization of the
management system, and at other times as specified in the management system, and at other times as specified in the
description of a schema node using this type. If such description of a schema node using this type. If such
other times can occur, for example, the creation of other times can occur, for example, the creation of
a schema node of type counter64 at times other than a schema node of type counter64 at times other than
re-initialization, then a corresponding schema node re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate should be defined, with an appropriate type, to indicate
the last discontinuity. the last discontinuity.
The counter64 type should not be used for configuration The counter64 type should not be used for configuration
schema nodes. A default statement SHOULD NOT be used in schema nodes. A default statement SHOULD NOT be used in
combination with the type counter64. combination with the type counter64.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the Counter64 type of the SMIv2."; to the Counter64 type of the SMIv2.";
reference reference
"RFC 2578: Structure of Management Information Version 2 (SMIv2)"; "RFC 2578: Structure of Management Information Version 2 (SMIv2)";
} }
typedef zero-based-counter64 { typedef zero-based-counter64 {
type yang:counter64; type yang:counter64;
default "0"; default "0";
description description
"The zero-based-counter64 type represents a counter64 which "The zero-based-counter64 type represents a counter64 that
has the defined `initial' value zero. has the defined 'initial' value zero.
A schema node 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 and will thereafter increase monotonically until it reaches
a maximum value of 2^64-1 (18446744073709551615 decimal), a maximum value of 2^64-1 (18446744073709551615 decimal),
when it wraps around and starts increasing again from zero. when it wraps around and starts increasing again from zero.
Provided that an application discovers a new schema node 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 'initial' value as a delta. It is important for a management
station to be aware of this minimum time and the actual time station to be aware of this minimum time and the actual time
between polls, and to discard data if the actual time is too between polls, and to discard data if the actual time is too
long or there is no defined minimum time. long or there is no defined minimum time.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the ZeroBasedCounter64 textual convention of the SMIv2."; to the ZeroBasedCounter64 textual convention of the SMIv2.";
reference reference
"RFC 2856: Textual Conventions for Additional High Capacity "RFC 2856: Textual Conventions for Additional High Capacity
Data Types"; Data Types";
} }
typedef gauge32 { typedef gauge32 {
type uint32; type uint32;
description description
"The gauge32 type represents a non-negative integer, which "The gauge32 type represents a non-negative integer, which
skipping to change at page 9, line 41 skipping to change at page 8, line 19
cannot be greater than 2^32-1 (4294967295 decimal), and cannot be greater than 2^32-1 (4294967295 decimal), and
the minimum value cannot be smaller than 0. The value of the minimum value cannot be smaller than 0. The value of
a gauge32 has its maximum value whenever the information a gauge32 has its maximum value whenever the information
being modeled is greater than or equal to its maximum being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value. being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the below (increases above) the maximum (minimum) value, the
gauge32 also decreases (increases). gauge32 also decreases (increases).
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the Gauge32 type of the SMIv2."; to the Gauge32 type of the SMIv2.";
reference reference
"RFC 2578: Structure of Management Information Version 2 (SMIv2)"; "RFC 2578: Structure of Management Information Version 2 (SMIv2)";
} }
typedef gauge64 { typedef gauge64 {
type uint64; type uint64;
description description
"The gauge64 type represents a non-negative integer, which "The gauge64 type represents a non-negative integer, which
may increase or decrease, but shall never exceed a maximum may increase or decrease, but shall never exceed a maximum
skipping to change at page 10, line 15 skipping to change at page 8, line 41
cannot be greater than 2^64-1 (18446744073709551615), and cannot be greater than 2^64-1 (18446744073709551615), and
the minimum value cannot be smaller than 0. The value of the minimum value cannot be smaller than 0. The value of
a gauge64 has its maximum value whenever the information a gauge64 has its maximum value whenever the information
being modeled is greater than or equal to its maximum being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value. being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the below (increases above) the maximum (minimum) value, the
gauge64 also decreases (increases). gauge64 also decreases (increases).
This type is in the value set and its semantics 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 10, line 35 skipping to change at page 9, line 16
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.
Values of this type are denoted as a sequence of numerical Values of this type are denoted as a sequence of numerical
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
white space. 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-identifier. 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
"ISO/IEC 9834-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 {
pattern '\d*(\.\d*){1,127}'; pattern '\d*(\.\d*){1,127}';
} }
description description
"This type represents object-identifiers restricted to 128 "This type represents object-identifiers restricted to 128
sub-identifiers. sub-identifiers.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the OBJECT IDENTIFIER type of the SMIv2."; to the OBJECT IDENTIFIER type of the SMIv2.";
reference reference
"RFC 2578: Structure of Management Information Version 2 (SMIv2)"; "RFC 2578: Structure of Management Information Version 2 (SMIv2)";
} }
/*** collection of date and time related types ***/ /*** 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 all
represent the same time zone in dateTime. represent the same time zone in dateTime.
skipping to change at page 12, line 17 skipping to change at page 11, line 7
schema type, which requires all times to be in UTC using the schema type, which requires all times to be in UTC using the
time-offset 'Z'. 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.
The canonical format for date-and-time values with a known time The canonical format for date-and-time values with a known time
zone uses a numeric time zone offset that is calculated using 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 configured known offset to UTC time. A change of
the device's offset to UTC time will cause date-and-time values the device's offset to UTC time will cause date-and-time values
to change accordingly. Such changes might happen periodically to change accordingly. Such changes might happen periodically
in case a server follows automatically daylight saving time in case a server follows automatically daylight saving time
(DST) time zone offset changes. The canonical format for (DST) time zone offset changes. The canonical format for
date-and-time values with an unknown time zone (usually refering date-and-time values with an unknown time zone (usually referring
to the notion of local time) uses the time-offset -00:00."; to the notion of local time) uses the time-offset -00:00.";
reference reference
"RFC 3339: Date and Time on the Internet: Timestamps "RFC 3339: Date and Time on the Internet: Timestamps
RFC 2579: Textual Conventions for SMIv2 RFC 2579: Textual Conventions for SMIv2
W3C REC-xmlschema-2-20041028: XML Schema Part 2: Datatypes XSD-TYPES: XML Schema Part 2: Datatypes Second Edition";
Second Edition";
} }
typedef timeticks { typedef timeticks {
type uint32; type uint32;
description description
"The timeticks type represents a non-negative integer which "The timeticks type represents a non-negative integer that
represents the time, modulo 2^32 (4294967296 decimal), in represents the time, modulo 2^32 (4294967296 decimal), in
hundredths of a second between two epochs. When a schema hundredths of a second between two epochs. When a schema
node is defined which uses this type, the description of node is defined that uses this type, the description of
the schema node identifies both of the reference epochs. the schema node identifies both of the reference epochs.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the TimeTicks type of the SMIv2."; to the TimeTicks type of the SMIv2.";
reference reference
"RFC 2578: Structure of Management Information Version 2 (SMIv2)"; "RFC 2578: Structure of Management Information Version 2 (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 happened. timeticks schema node at which a specific occurrence happened.
skipping to change at page 13, line 13 skipping to change at page 11, line 51
of any schema node defined using this type. When the specific of any schema node defined using this type. When the specific
occurrence occurred prior to the last time the associated occurrence occurred prior to the last time the associated
timeticks attribute was zero, then the timestamp value is timeticks attribute was zero, then the timestamp value is
zero. Note that this requires all timestamp values to be zero. Note that this requires all timestamp values to be
reset to zero when the value of the associated timeticks 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.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the TimeStamp textual convention of the SMIv2."; to the TimeStamp textual convention of the SMIv2.";
reference reference
"RFC 2579: Textual Conventions for SMIv2"; "RFC 2579: Textual Conventions for SMIv2";
} }
/*** collection of generic address types ***/ /*** collection of generic address types ***/
typedef phys-address { typedef phys-address {
type string { type string {
pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?'; pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?';
} }
skipping to change at page 13, line 28 skipping to change at page 12, line 18
/*** collection of generic address types ***/ /*** collection of generic address types ***/
typedef phys-address { typedef phys-address {
type string { type string {
pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?'; pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?';
} }
description description
"Represents media- or physical-level addresses represented "Represents media- or physical-level addresses represented
as a sequence octets, each octet represented by two hexadecimal as a sequence octets, each octet represented by two hexadecimal
numbers. Octets are separated by colons. The canonical numbers. Octets are separated by colons. The canonical
representation uses lower-case characters. representation uses lowercase characters.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the PhysAddress textual convention of the SMIv2."; to the PhysAddress textual convention of the SMIv2.";
reference reference
"RFC 2579: Textual Conventions for SMIv2"; "RFC 2579: Textual Conventions for SMIv2";
} }
typedef mac-address { typedef mac-address {
type string { type string {
pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}'; pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}';
} }
description description
"The mac-address type represents an IEEE 802 MAC address. "The mac-address type represents an IEEE 802 MAC address.
The canonical representation uses lower-case characters. The canonical representation uses lowercase characters.
This type is in the value set and its semantics equivalent to In the value set and its semantics, this type is equivalent
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 which 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
"XPATH: XML Path Language (XPath) Version 1.0"; "XPATH: XML Path Language (XPath) Version 1.0";
} }
} }
<CODE ENDS> <CODE ENDS>
4. Internet Specific Derived Types 4. Internet-Specific Derived Types
<CODE BEGINS> file "ietf-inet-types@2010-04-24.yang" The ietf-inet-types YANG module references [RFC0768], [RFC0791],
[RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460],
[RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3492],
[RFC3595], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291],
[RFC4340], [RFC4893], [RFC4960], [RFC5017], [RFC5891], and [RFC5952].
<CODE BEGINS> file "ietf-inet-types@2010-09-24.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 15, line 35 skipping to change at page 13, line 49
<mailto:david.kessens@nsn.com> <mailto:david.kessens@nsn.com>
Editor: Juergen Schoenwaelder Editor: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>"; <mailto:j.schoenwaelder@jacobs-university.de>";
description description
"This module contains a collection of generally useful derived "This module contains a collection of generally useful derived
YANG data types for Internet addresses and related things. YANG data types for Internet addresses and related things.
Copyright (c) 2010 IETF Trust and the persons identified as Copyright (c) 2010 IETF Trust and the persons identified as
the document authors. 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
without modification, is permitted pursuant to, and subject modification, is permitted pursuant to, and subject to the license
to the license terms contained in, the Simplified BSD License terms contained in, the Simplified BSD License set forth in Section
set forth in Section 4.c of the IETF Trust's Legal Provisions 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 6021; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this note
revision 2010-04-24 { revision 2010-09-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC 6021: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note
/*** collection of protocol field related types ***/ /*** collection of protocol field related types ***/
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 protocol."; "An unknown or unspecified version of the Internet protocol.";
} }
skipping to change at page 16, line 31 skipping to change at page 14, line 44
} }
enum ipv6 { enum ipv6 {
value "2"; value "2";
description description
"The IPv6 protocol as defined in RFC 2460."; "The IPv6 protocol as defined in RFC 2460.";
} }
} }
description description
"This value represents the version of the IP protocol. "This value represents the version of the IP protocol.
This type is in the value set and its semantics 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.
This type is in the value set and its semantics 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 flow-label type represents flow identifier or Flow Label
in an IPv6 packet header that may be used to discriminate in an IPv6 packet header that may be used to discriminate
traffic flows. traffic flows.
This type is in the value set and its semantics 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.
This type is in the value set and its semantics 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 autonomous system related types ***/
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 ASs'. 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.
This type is in the value set and its semantics 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 4893: BGP Support for Four-octet AS Number Space RFC 4893: BGP Support for Four-octet AS Number Space
RFC 4001: Textual Conventions for Internet Network Addresses"; RFC 4001: Textual Conventions for Internet Network Addresses";
} }
/*** collection of IP address and hostname related types ***/ /*** collection of IP address and hostname related types ***/
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 representations version neutral. The format of the textual representations
implies the IP version."; implies the IP version.";
} }
typedef ipv4-address { typedef ipv4-address {
type string { type string {
pattern pattern
'(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}' '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
+ '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])' + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
+ '(%[\p{N}\p{L}]+)?'; + '(%[\p{N}\p{L}]+)?';
} }
description description
"The ipv4-address type represents an IPv4 address in "The ipv4-address type represents an IPv4 address in
dotted-quad notation. The IPv4 address may include a zone dotted-quad notation. The IPv4 address may include a zone
index, separated by a % sign. 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 for the zone index is the numerical The canonical format for the zone index is the numerical
format"; format";
} }
typedef ipv6-address { typedef ipv6-address {
type string { type string {
pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}' pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
+ '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|' + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|'
+ '(((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])))'
+ '(%[\p{N}\p{L}]+)?'; + '(%[\p{N}\p{L}]+)?';
pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|' pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|'
+ '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)' + '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)'
+ '(%.+)?'; + '(%.+)?';
} }
description description
"The ipv6-address type represents an IPv6 address in full, "The ipv6-address type represents an IPv6 address in full,
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 compressed The canonical format of IPv6 addresses uses the compressed
format described in RFC 4291 section 2.2 item 2 with the format described in RFC 4291, Section 2.2, item 2 with the
following additional rules: The :: substitution must be following additional rules: the :: substitution must be
applied to the longest sequence of all-zero 16-bit chunks applied to the longest sequence of all-zero 16-bit chunks
in an IPv6 address. If there is a tie, the first sequence in an IPv6 address. If there is a tie, the first sequence
of all-zero 16-bit chunks is replaced by ::. Single of all-zero 16-bit chunks is replaced by ::. Single
all-zero 16-bit chunks are not compressed. The canonical all-zero 16-bit chunks are not compressed. The canonical
format uses lower-case characters and leading zeros are format uses lowercase characters and leading zeros are
not allowed. The canonical format for the zone index is not allowed. The canonical format for the zone index is
the numerical format as described in RFC 4007 section the numerical format as described in RFC 4007, Section
11.2."; 11.2.";
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
IDv6TREP: A Recommendation for IPv6 Address Text Representation"; RFC 5952: A Recommendation for IPv6 Address Text Representation";
} }
typedef ip-prefix { typedef ip-prefix {
type union { type union {
type inet:ipv4-prefix; type inet:ipv4-prefix;
type inet:ipv6-prefix; type inet:ipv6-prefix;
} }
description description
"The ip-prefix type represents an IP prefix and is IP "The ip-prefix type represents an IP prefix and is IP
version neutral. The format of the textual representations version neutral. The format of the textual representations
implies the IP version."; implies the IP version.";
} }
typedef ipv4-prefix { typedef ipv4-prefix {
type string { type string {
pattern pattern
'(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}' '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
+ '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])' + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
+ '/(([0-9])|([1-2][0-9])|(3[0-2]))'; + '/(([0-9])|([1-2][0-9])|(3[0-2]))';
} }
description description
"The ipv4-prefix type represents an IPv4 address prefix. "The ipv4-prefix type represents an IPv4 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 to 32. slash character and must be less than or equal to 32.
A prefix length value of n corresponds to an IP address A prefix length value of n corresponds to an IP address
mask which 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 canonical format of an IPv4 prefix has all bits of The canonical format of an IPv4 prefix has all bits of
the IPv4 address set to zero that are not part of the the IPv4 address set to zero that are not part of the
IPv4 prefix."; IPv4 prefix.";
} }
typedef ipv6-prefix { typedef ipv6-prefix {
type string { type string {
pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}' pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
skipping to change at page 21, line 4 skipping to change at page 19, line 24
typedef ipv6-prefix { typedef ipv6-prefix {
type string { type string {
pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}' pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
+ '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|' + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|'
+ '(((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 128.
A prefix length value of n corresponds to an IP address A prefix length value of n corresponds to an IP address
mask which 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
IPv6 prefix. Furthermore, IPv6 address is represented IPv6 prefix. Furthermore, IPv6 address is represented
in the compressed format described in RFC 4291 section in the compressed format described in RFC 4291, Section
2.2 item 2 with the following additional rules: The :: 2.2, item 2 with the following additional rules: the ::
substitution must be applied to the longest sequence of substitution must be applied to the longest sequence of
all-zero 16-bit chunks in an IPv6 address. If there is all-zero 16-bit chunks in an IPv6 address. If there is
a tie, the first sequence of all-zero 16-bit chunks is a tie, the first sequence of all-zero 16-bit chunks is
replaced by ::. Single all-zero 16-bit chunks are not replaced by ::. Single all-zero 16-bit chunks are not
compressed. The canonical format uses lower-case compressed. The canonical format uses lowercase
characters and leading zeros are not allowed."; characters and leading zeros are not allowed.";
reference reference
"RFC 4291: IP Version 6 Addressing Architecture"; "RFC 4291: IP Version 6 Addressing Architecture";
} }
/*** collection of domain name and URI types ***/ /*** collection of domain name and URI types ***/
typedef domain-name { typedef domain-name {
type string { type string {
pattern '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.)*' pattern '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.)*'
+ '([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.?)' + '([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.?)'
+ '|\.'; + '|\.';
length "1..253"; length "1..253";
} }
description description
skipping to change at page 21, line 43 skipping to change at page 20, line 14
/*** collection of domain name and URI types ***/ /*** collection of domain name and URI types ***/
typedef domain-name { typedef domain-name {
type string { type string {
pattern '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.)*' pattern '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.)*'
+ '([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.?)' + '([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.?)'
+ '|\.'; + '|\.';
length "1..253"; length "1..253";
} }
description description
"The domain-name type represents a DNS domain name. The "The domain-name type represents a DNS domain name. The
name SHOULD be fully qualified whenever possible. name SHOULD be fully qualified whenever possible.
Internet domain names are only loosely specified. Section Internet domain names are only loosely specified. Section
3.5 of RFC 1034 recommends a syntax (modified in section 3.5 of RFC 1034 recommends a syntax (modified in Section
2.1 of RFC 1123). The pattern above is intended to allow 2.1 of RFC 1123). The pattern above is intended to allow
for current practise in domain name use, and some possible for current practice in domain name use, and some possible
future expansion. It is designed to hold various types of future expansion. It is designed to hold various types of
domain names, including names used for A or AAAA records domain names, including names used for A or AAAA records
(host names) and other records, such as SRV records. Note (host names) and other records, such as SRV records. Note
that Internet host names have a stricter syntax (described that Internet host names have a stricter syntax (described
in RFC 952) than the DNS recommendations in RFCs 1034 and in RFC 952) than the DNS recommendations in RFCs 1034 and
1123, and that systems that want to store host names in 1123, and that systems that want to store host names in
schema nodes using the domain-name type are recommended to schema nodes using the domain-name type are recommended to
adhere to this stricter standard to ensure interoperability. adhere to this stricter standard to ensure interoperability.
The encoding of DNS names in the DNS protocol is limited The encoding of DNS names in the DNS protocol is limited
to 255 characters. Since the encoding consists of labels to 255 characters. Since the encoding consists of labels
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 explicitely or it 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 encoded in punycode as described in RFC domain names MUST be encoded in punycode as described in RFC
3492"; 3492";
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 3490: Internationalizing Domain Names in Applications
(IDNA)
RFC 3492: Punycode: A Bootstring encoding of Unicode for RFC 3492: Punycode: A Bootstring encoding of Unicode for
Internationalized Domain Names in Applications Internationalized Domain Names in Applications
(IDNA)"; (IDNA)
RFC 5891: Internationalizing Domain Names in Applications
(IDNA): Protocol";
} }
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
domain name."; domain name.";
skipping to change at page 23, line 31 skipping to change at page 22, line 5
textually distinct after this normalization may still be textually distinct after this normalization may still be
equivalent. equivalent.
Objects using the uri type may restrict the schemes that Objects using the uri type may restrict the schemes that
they permit. For example, 'data:' and 'urn:' schemes they permit. For example, 'data:' and 'urn:' schemes
might not be appropriate. might not be appropriate.
A zero-length URI is not a valid URI. This can be used to A zero-length URI is not a valid URI. This can be used to
express 'URI absent' where required. express 'URI absent' where required.
This type is in the value set and its semantics equivalent In the value set and its semantics, this type is equivalent
to the Uri SMIv2 textual convention defined in RFC 5017."; to the Uri SMIv2 textual convention defined in RFC 5017.";
reference reference
"RFC 3986: Uniform Resource Identifier (URI): Generic Syntax "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
RFC 3305: Report from the Joint W3C/IETF URI Planning Interest RFC 3305: Report from the Joint W3C/IETF URI Planning Interest
Group: Uniform Resource Identifiers (URIs), URLs, Group: Uniform Resource Identifiers (URIs), URLs,
and Uniform Resource Names (URNs): Clarifications and Uniform Resource Names (URNs): Clarifications
and Recommendations and Recommendations
RFC 5017: MIB Textual Conventions for Uniform Resource RFC 5017: MIB Textual Conventions for Uniform Resource
Identifiers (URIs)"; Identifiers (URIs)";
} }
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
This document registers two URIs in the IETF XML registry [RFC3688]. This document registers two URIs in the IETF XML registry [RFC3688].
Following the format in RFC 3688, the following registration is Following the format in RFC 3688, the following registrations have
requested. been made.
URI: urn:ietf:params:xml:ns:yang:ietf-yang-types URI: urn:ietf:params:xml:ns:yang:ietf-yang-types
Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
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 [YANG]. 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: RFCXXXX reference: RFC 6021
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: RFCXXXX reference: RFC 6021
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 [YANG] 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 draft: of this document:
- Andy Bierman (Netconf Central) - Andy Bierman (Brocade)
- Martin Bjorklund (Tail-f Systems) - Martin Bjorklund (Tail-f Systems)
- Balazs Lengyel (Ericsson) - Balazs Lengyel (Ericsson)
- David Partain (Ericsson) - David Partain (Ericsson)
- Phil Shafer (Juniper Networks) - Phil Shafer (Juniper Networks)
8. Acknowledgments 8. Acknowledgments
The editor wishes to thank the following individuals for providing The editor wishes to thank the following individuals for providing
helpful comments on various versions of this document: Ladislav helpful comments on various versions of this document: Ladislav
Lhotka, Lars-Johan Liman, Dan Romascanu. Lhotka, Lars-Johan Liman, and Dan Romascanu.
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.
[RFC3492] Costello, A., "Punycode: A Bootstring encoding of Unicode [RFC3492] Costello, A., "Punycode: A Bootstring encoding of
for Internationalized Domain Names in Applications Unicode for Internationalized Domain Names in
(IDNA)", RFC 3492, March 2003. Applications (IDNA)", RFC 3492, March 2003.
[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.
[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.
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Version 1.0", World Wide Web Consortium Network Configuration Protocol (NETCONF)", RFC 6020,
Recommendation REC-xpath-19991116, November 1999, October 2010.
<http://www.w3.org/TR/1999/REC-xpath-19991116>.
[YANG] Bjorklund, M., Ed., "YANG - A data modeling language for [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)
NETCONF", draft-ietf-netmod-yang-12 (work in progress). Version 1.0", World Wide Web Consortium
Recommendation REC-xpath-19991116, November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>.
9.2. Informative References 9.2. Informative References
[IDv6TREP] [IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area
Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 Networks: Overview and Architecture", IEEE Std. 802-
Address Text Representation", 2001.
draft-ietf-6man-text-addr-representation-07 (work in
progress).
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area [ISO9834-1] ISO/IEC, "Information technology -- Open Systems
Networks: Overview and Architecture", IEEE Std. 802-2001. Interconnection -- Procedures for the operation of OSI
Registration Authorities: General procedures and top
arcs of the ASN.1 Object Identifier tree", ISO/
IEC 9834-1: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.
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, [RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label",
"Internationalizing Domain Names in Applications (IDNA)", RFC 3595, September 2003.
RFC 3490, March 2003.
[RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label", [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
RFC 3595, September 2003. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Schoenwaelder, "Textual Conventions for Internet Network Protocol 4 (BGP-4)", RFC 4271, January 2006.
Addresses", RFC 4001, February 2005.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Protocol 4 (BGP-4)", RFC 4271, January 2006. Congestion Control Protocol (DCCP)", RFC 4340,
March 2006.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4502] Waldbusser, S., "Remote Network Monitoring Management
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Information Base Version 2", RFC 4502, May 2006.
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management [RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741,
Information Base Version 2", RFC 4502, May 2006. December 2006.
[RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741, [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS
December 2006. Number Space", RFC 4893, May 2007.
[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
Number Space", RFC 4893, May 2007. RFC 4960, September 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC5017] McWalter, D., "MIB Textual Conventions for Uniform
RFC 4960, September 2007. Resource Identifiers (URIs)", RFC 5017, September 2007.
[RFC5017] McWalter, D., "MIB Textual Conventions for Uniform [RFC5891] Klensin, J., "Internationalizing Domain Names in
Resource Identifiers (URIs)", RFC 5017, September 2007. Applications (IDNA): Protocol", RFC 5891, August 2010.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IPv6 Address Text Representation", RFC 5952,
May 2008. August 2010.
[XSD-TYPES] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium
Recommendation REC-xmlschema-2-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
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. 157 change blocks. 
293 lines changed or deleted 295 lines changed or added

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