draft-ietf-netmod-yang-types-05.txt   draft-ietf-netmod-yang-types-06.txt 
Network Working Group J. Schoenwaelder, Ed. Network Working Group J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Internet-Draft Jacobs University
Intended status: Standards Track December 1, 2009 Intended status: Standards Track February 3, 2010
Expires: June 4, 2010 Expires: August 7, 2010
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-yang-types-05 draft-ietf-netmod-yang-types-06
Abstract
This document introduces a collection of common data types to be used
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 This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 4, 2010. This Internet-Draft will expire on August 7, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
This document introduces a collection of common data types to be used This document may contain material from IETF Documents or IETF
with the YANG data modeling language. Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Core YANG Derived Types . . . . . . . . . . . . . . . . . . . 7 3. Core YANG Derived Types . . . . . . . . . . . . . . . . . . . 6
4. Internet Specific Derived Types . . . . . . . . . . . . . . . 16 4. Internet Specific Derived Types . . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 6. Security Considerations . . . . . . . . . . . . . . . . . . . 25
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 27 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 26
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.1. Normative References . . . . . . . . . . . . . . . . . . . 29 9.1. Normative References . . . . . . . . . . . . . . . . . . . 28
9.2. Informative References . . . . . . . . . . . . . . . . . . 29 9.2. Informative References . . . . . . . . . . . . . . . . . . 28
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 32 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
YANG [YANG] is a data modeling language used to model configuration YANG [YANG] is a data modeling language used to model configuration
and state data manipulated by the NETCONF [RFC4741] protocol. The and state data manipulated by the NETCONF [RFC4741] protocol. The
YANG language supports a small set of built-in data types and YANG language supports a small set of built-in data types and
provides mechanisms to derive other types from the built-in types. 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
skipping to change at page 5, line 8 skipping to change at page 4, line 8
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 over the types defined in This section provides a short overview over the types defined in
subsequent sections and their equivalent SMIv2 data types. Table 1 subsequent sections and their equivalent SMIv2 data types. A YANG
list the types defined in the ietf-yang-types YANG module and the data type is equivalent to an SMIv2 data type if the data types have
corresponding SMIv2 types (if any). the same set of values and the semantics of the values are
equivalent.
Table 1 lists the types defined in the ietf-yang-types YANG module
and the corresponding SMIv2 types (if any).
ietf-yang-types ietf-yang-types
+-----------------------+--------------------------------+ +-----------------------+--------------------------------+
| YANG type | Equivalent SMIv2 type (module) | | YANG type | Equivalent SMIv2 type (module) |
+-----------------------+--------------------------------+ +-----------------------+--------------------------------+
| counter32 | Counter32 (SNMPv2-SMI) | | counter32 | Counter32 (SNMPv2-SMI) |
| zero-based-counter32 | ZeroBasedCounter32 (RMON2-MIB) | | zero-based-counter32 | ZeroBasedCounter32 (RMON2-MIB) |
| counter64 | Counter64 (SNMPv2-SMI) | | counter64 | Counter64 (SNMPv2-SMI) |
| zero-based-counter64 | ZeroBasedCounter64 (HCNUM-TC) | | zero-based-counter64 | ZeroBasedCounter64 (HCNUM-TC) |
skipping to change at page 5, line 35 skipping to change at page 4, line 39
| date-and-time | - | | date-and-time | - |
| timeticks | TimeTicks (SNMPv2-SMI) | | timeticks | TimeTicks (SNMPv2-SMI) |
| timestamp | TimeStamp (SNMPv2-TC) | | timestamp | TimeStamp (SNMPv2-TC) |
| phys-address | PhysAddress (SNMPv2-TC) | | phys-address | PhysAddress (SNMPv2-TC) |
| mac-address | MacAddress (SNMPv2-TC) | | mac-address | MacAddress (SNMPv2-TC) |
| xpath1.0 | - | | xpath1.0 | - |
+-----------------------+--------------------------------+ +-----------------------+--------------------------------+
Table 1 Table 1
Table 2 list the types defined in the ietf-inet-types YANG module and Table 2 lists the types defined in the ietf-inet-types YANG module
the corresponding SMIv2 types (if any). and the corresponding SMIv2 types (if any).
ietf-inet-types ietf-inet-types
+-----------------+-----------------------------------------------+ +-----------------+-----------------------------------------------+
| YANG type | Equivalent SMIv2 type (module) | | YANG type | Equivalent SMIv2 type (module) |
+-----------------+-----------------------------------------------+ +-----------------+-----------------------------------------------+
| ip-version | - | | ip-version | InetVersion (INET-ADDRESS-MIB) |
| dscp | Dscp (DIFFSERV-DSCP-TC) | | dscp | Dscp (DIFFSERV-DSCP-TC) |
| ipv6-flow-label | IPv6FlowLabel (IPV6-FLOW-LABEL-MIB) | | ipv6-flow-label | IPv6FlowLabel (IPV6-FLOW-LABEL-MIB) |
| port-number | InetPortNumber (INET-ADDRESS-MIB) | | port-number | InetPortNumber (INET-ADDRESS-MIB) |
| as-number | InetAutonomousSystemNumber (INET-ADDRESS-MIB) | | as-number | InetAutonomousSystemNumber (INET-ADDRESS-MIB) |
| ip-address | - | | ip-address | - |
| ipv4-address | - | | ipv4-address | - |
| ipv6-address | - | | ipv6-address | - |
| ip-prefix | - | | ip-prefix | - |
| ipv4-prefix | - | | ipv4-prefix | - |
| 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.yang" <CODE BEGINS> file "ietf-yang-types@2010-02-03.yang"
module ietf-yang-types { module ietf-yang-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types-DRAFT-05"; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types-DRAFT-06";
prefix "yang"; prefix "yang";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: David Partain WG Chair: David Partain
<mailto:david.partain@ericsson.com> <mailto:david.partain@ericsson.com>
WG Chair: David Kessens WG Chair: David Kessens
<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) 2009 IETF Trust and the persons identified as Copyright (c) 2010 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. 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 XXXX; 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 // RFC Ed.: replace XXXX with actual RFC number and remove this note
// RFC Ed.: remove this note // RFC Ed.: remove this note
// Note: extracted from draft-ietf-netmod-yang-types-05.txt // Note: extracted from draft-ietf-netmod-yang-types-05.txt
revision 2009-11-10 { revision 2010-02-03 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note // 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 {
skipping to change at page 8, line 25 skipping to change at page 7, line 25
"The counter32 type represents a non-negative integer "The counter32 type represents a non-negative integer
which monotonically increases until it reaches a which 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 an object instance using this type. If description of a schema node using this type. If such
such other times can occur, for example, the creation of other times can occur, for example, the creation of an
an object instance of type counter32 at times other than a schema node of type counter32 at times other than
re-initialization, then a corresponding object should be re-initialization, then a corresponding schema node
defined, with an appropriate type, to indicate the last should be defined, with an appropriate type, to indicate
discontinuity. the last discontinuity.
The counter32 type should not be used for configuration The counter32 type should not be used for configuration
objects. A default statement should not be used for schema nodes. A default statement should not be used for
attributes with a type value of counter32. attributes with a type value of counter32.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics 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. which has the defined `initial' value zero.
Objects of this type will be set to zero(0) on creation Schema nodes of this type will be set to zero(0) on creation
and will thereafter count appropriate events, wrapping and will thereafter increase monotonically until it reaches
back to zero(0) when the value 2^32 is reached. a maximum value of 2^32-1 (4294967295 decimal), when it
wraps around and starts increasing again from zero.
Provided that an application discovers the new object within Provided that an application discovers a new schema node
the minimum time to wrap it can use the initial value as a of this type within the minimum time to wrap it can use the
delta since it last polled the table of which this object is initial value as a delta. It is important for a management
part. It is important for a management station to be aware station to be aware of this minimum time and the actual time
of this minimum time and the actual time between polls, and between polls, and to discard data if the actual time is too
to discard data if the actual time is too long or there is long or there is no defined minimum time.
no defined minimum time.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics equivalent
to the ZeroBasedCounter32 textual convention of the SMIv2."; to the ZeroBasedCounter32 textual convention of the SMIv2.";
reference reference
"RFC 2021: Remote Network Monitoring Management Information "RFC 4502: Remote Network Monitoring Management Information
Base Version 2 using SMIv2"; Base Version 2 using SMIv2";
} }
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 which monotonically increases until it reaches a
maximum value of 2^64-1 (18446744073709551615), when maximum value of 2^64-1 (18446744073709551615 decimal),
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 an object instance using this type. If description of a schema node using this type. If such
such other times can occur, for example, the creation of other times can occur, for example, the creation of
an object instance of type counter64 at times other than a schema node of type counter64 at times other than
re-initialization, then a corresponding object should be re-initialization, then a corresponding schema node
defined, with an appropriate type, to indicate the last should be defined, with an appropriate type, to indicate
discontinuity. the last discontinuity.
The counter64 type should not be used for configuration The counter64 type should not be used for configuration
objects. A default statement should not be used for schema nodes. A default statement should not be used for
attributes with a type value of counter64. attributes with a type value of counter64.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics 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 which
has the defined `initial' value zero. has the defined `initial' value zero.
Objects of this type will be set to zero(0) on creation Schema nodes of this type will be set to zero(0) on creation
and will thereafter count appropriate events, wrapping and will thereafter increase monotonically until it reaches
back to zero(0) when the value 2^64 is reached. a maximum value of 2^64-1 (18446744073709551615 decimal),
when it wraps around and starts increasing again from zero.
Provided that an application discovers the new object within Provided that an application discovers a new schema node
the minimum time to wrap it can use the initial value as a of this type within the minimum time to wrap it can use the
delta since it last polled the table of which this object is initial value as a delta. It is important for a management
part. It is important for a management station to be aware station to be aware of this minimum time and the actual time
of this minimum time and the actual time between polls, and between polls, and to discard data if the actual time is too
to discard data if the actual time is too long or there is long or there is no defined minimum time.
no defined minimum time.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics 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
may increase or decrease, but shall never exceed a maximum may increase or decrease, but shall never exceed a maximum
value, nor fall below a minimum value. The maximum value value, nor fall below a minimum value. The maximum value
can not be greater than 2^32-1 (4294967295 decimal), and cannot be greater than 2^32-1 (4294967295 decimal), and
the minimum value can not 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 This type is in the value set and its semantics equivalent
to the Counter32 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
value, nor fall below a minimum value. The maximum value value, nor fall below a minimum value. The maximum value
can not be greater than 2^64-1 (18446744073709551615), and cannot be greater than 2^64-1 (18446744073709551615), and
the minimum value can not 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 This type is in the value set and its semantics equivalent
to the CounterBasedGauge64 SMIv2 textual convention defined to the CounterBasedGauge64 SMIv2 textual convention defined
skipping to change at page 12, line 10 skipping to change at page 11, line 11
since it is not restricted to 128 sub-identifiers."; since it is not restricted to 128 sub-identifiers.";
reference reference
"ISO/IEC 9834-1: Information technology -- Open Systems "ISO/IEC 9834-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 This type is in the value set and its semantics 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 format is most easily described Gregorian calendar. The format is most easily described
using the following ABFN (replacing double quotes with using the following ABFN (replacing double quotes with
single quotes): single quotes):
date-fullyear = 4DIGIT date-fullyear = 4DIGIT
date-month = 2DIGIT ; 01-12 date-month = 2DIGIT ; 01-12
skipping to change at page 13, line 46 skipping to change at page 12, line 48
RFC 2579: Textual Conventions for SMIv2 RFC 2579: Textual Conventions for SMIv2
W3C REC-xmlschema-2-20041028: XML Schema Part 2: Datatypes W3C REC-xmlschema-2-20041028: 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 which
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 objects hundredths of a second between two epochs. When a schema
are defined which use this type, the description of the node is defined which uses this type, the description of
object 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 This type is in the value set and its semantics 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 object at which a specific occurrence happened. timeticks schema node at which a specific occurrence happened.
The specific occurrence must be defined in the description The specific occurrence must be defined in the description
of any object 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 object must be specified The associated timeticks schema node must be specified
in the description of any object using this type. in the description of any schema node using this type.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics 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 {
skipping to change at page 15, line 21 skipping to change at page 14, line 23
"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
description of the schema node MUST specify the XPath
context in which the XPath expression is evaluated.";
reference reference
"W3C REC-xpath-19991116: XML Path Language (XPath) Version 1.0"; "W3C REC-xpath-19991116: 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.yang" <CODE BEGINS> file "ietf-inet-types@2010-02-03.yang"
module ietf-inet-types { module ietf-inet-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types-DRAFT-05"; namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types-DRAFT-06";
prefix "inet"; prefix "inet";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: David Partain WG Chair: David Partain
skipping to change at page 16, line 34 skipping to change at page 15, line 34
WG Chair: David Kessens WG Chair: David Kessens
<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) 2009 IETF Trust and the persons identified as Copyright (c) 2010 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. 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 XXXX; 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 // RFC Ed.: replace XXXX with actual RFC number and remove this note
// RFC Ed.: remove this note // RFC Ed.: remove this note
// Note: extracted from draft-ietf-netmod-yang-types-05.txt // Note: extracted from draft-ietf-netmod-yang-types-05.txt
revision 2009-11-10 { revision 2010-02-03 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note // 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 {
skipping to change at page 17, line 34 skipping to change at page 16, line 34
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 This type is in the value set and its semantics equivalent
to the InetVersion textual convention of the SMIv2. However, to the InetVersion textual convention of the SMIv2.";
the lexical appearance is different from the InetVersion
textual convention.";
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";
} }
skipping to change at page 18, line 49 skipping to change at page 17, line 47
Note that the value zero is not a valid port number. A union Note that the value zero is not a valid port number. A union
type might be used in situations where the value zero is type might be used in situations where the value zero is
meaningful. meaningful.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics 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 2960: 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
skipping to change at page 20, line 4 skipping to change at page 18, line 50
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 '((0' pattern '(([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}'
+ '|(1[0-9]{0,2})' + '([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])'
+ '|(2(([0-4][0-9]?)|(5[0-5]?)|([6-9]?)))' + '(%[\p{N}\p{L}]+)?';
+ '|([3-9][0-9]?)'
+ ')'
+ '\.){3}'
+ '(0'
+ '|(1[0-9]{0,2})'
+ '|(2(([0-4][0-9]?)|(5[0-5]?)|([6-9]?)))'
+ '|([3-9][0-9]?)'
+ ')(%[\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
skipping to change at page 21, line 11 skipping to change at page 19, line 49
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 normalized all-zero 16-bit chunks are not compressed. The canonical
format uses lower-case characters and leading zeros are format uses lower-case 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"; IDv6TREP: A Recommendation for IPv6 Address Text Representation";
} }
skipping to change at page 22, line 36 skipping to change at page 21, line 27
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 normalized format uses lower-case compressed. The canonical format uses lower-case
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]\.)*'
skipping to change at page 23, line 17 skipping to change at page 22, line 8
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 practise 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
objects using the domain-name type are recommended to adhere schema nodes using the domain-name type are recommended to
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 objects using the domain-name The description clause of schema nodes using the domain-name
type MUST describe how (and when) these names are type MUST describe when and how these names are resolved to
resolved to IP addresses. Note that the resolution of a IP addresses. Note that the resolution of a domain-name value
domain-name value may require to query multiple DNS records may require to query multiple DNS records (e.g., A for IPv4
(e.g., A for IPv4 and AAAA for IPv6). The order of the and AAAA for IPv6). The order of the resolution process and
resolution process and which DNS record takes precedence which DNS record takes precedence can either be defined
depends on the configuration of the resolver. explicitely or it may depend on the configuration of the
resolver.
The canonical format for domain-name values uses the The canonical format for domain-name values uses the
US-ASCII encoding and case-insensitive characters are set US-ASCII encoding and case-insensitive characters are set
to lowercase."; to lowercase.";
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 3490: Internationalizing Domain Names in Applications RFC 3490: Internationalizing Domain Names in Applications
skipping to change at page 24, line 14 skipping to change at page 23, line 6
"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.";
} }
typedef uri { typedef uri {
type string; type string;
description description
"The uri type represents a Uniform Resource Identifier "The uri type represents a Uniform Resource Identifier
(URI) as defined by STD 66. (URI) as defined by STD 66.
Objects using the uri type must be in US-ASCII encoding, Objects using the uri type MUST be in US-ASCII encoding,
and MUST be normalized as described by RFC 3986 Sections and MUST be normalized as described by RFC 3986 Sections
6.2.1, 6.2.2.1, and 6.2.2.2. All unnecessary 6.2.1, 6.2.2.1, and 6.2.2.2. All unnecessary
percent-encoding is removed, and all case-insensitive percent-encoding is removed, and all case-insensitive
characters are set to lowercase except for hexadecimal characters are set to lowercase except for hexadecimal
digits, which are normalized to uppercase as described in digits, which are normalized to uppercase as described in
Section 6.2.2.1. Section 6.2.2.1.
The purpose of this normalization is to help provide The purpose of this normalization is to help provide
unique URIs. Note that this normalization is not unique URIs. Note that this normalization is not
sufficient to provide uniqueness. Two URIs that are sufficient to provide uniqueness. Two URIs that are
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 This type is in the value set and its semantics 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
skipping to change at page 29, line 16 skipping to change at page 28, line 16
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.
[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.
[YANG] Bjorklund, M., Ed., "YANG - A data modeling language for [YANG] Bjorklund, M., Ed., "YANG - A data modeling language for
NETCONF", draft-ietf-netmod-yang-09 (work in progress). NETCONF", draft-ietf-netmod-yang-10 (work in progress).
9.2. Informative References 9.2. Informative References
[IDv6TREP] [IDv6TREP]
Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", Address Text Representation",
draft-ietf-6man-text-addr-representation-03 (work in draft-ietf-6man-text-addr-representation-04 (work in
progress). progress).
[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.
[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.
skipping to change at page 29, line 51 skipping to change at page 28, line 51
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987. STD 13, RFC 1034, November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application [RFC1123] Braden, R., "Requirements for Internet Hosts - Application
and Support", STD 3, RFC 1123, October 1989. 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 (AS)",
BCP 6, RFC 1930, March 1996. BCP 6, RFC 1930, March 1996.
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021,
January 1997.
[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
skipping to change at page 30, line 30 skipping to change at page 29, line 26
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 For
Values In the Internet Protocol and Related Headers", Values In the Internet Protocol and Related Headers",
BCP 37, RFC 2780, March 2000. BCP 37, RFC 2780, March 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.
[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C.,
Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M.,
Zhang, L., and V. Paxson, "Stream Control Transmission
Protocol", RFC 2960, October 2000.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information
Base for the Differentiated Services Architecture", Base for the Differentiated Services Architecture",
RFC 3289, May 2002. 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 W3C/
IETF URI Planning Interest Group: Uniform Resource 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.
skipping to change at page 31, line 29 skipping to change at page 30, line 18
[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.
[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.
[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
Information Base Version 2", RFC 4502, May 2006.
[RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741, [RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741,
December 2006. December 2006.
[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS
Number Space", RFC 4893, May 2007. Number Space", RFC 4893, May 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol",
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.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
Author's Address Author's Address
Juergen Schoenwaelder (editor) Juergen Schoenwaelder (editor)
 End of changes. 58 change blocks. 
145 lines changed or deleted 144 lines changed or added

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