draft-ietf-netmod-system-mgmt-06.txt   draft-ietf-netmod-system-mgmt-07.txt 
Network Working Group A. Bierman Network Working Group A. Bierman
Internet-Draft YumaWorks Internet-Draft YumaWorks
Intended status: Standards Track M. Bjorklund Intended status: Standards Track M. Bjorklund
Expires: October 23, 2013 Tail-f Systems Expires: December 19, 2013 Tail-f Systems
April 21, 2013 June 17, 2013
YANG Data Model for System Management YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-06 draft-ietf-netmod-system-mgmt-07
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
identification of the management system of a device. identification of some common system properties within a device
containing a NETCONF server. This includes data node definitions for
system identification, time-of-day management, user management, DNS
resolver configuration, and some protocol operations for system
management.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on October 23, 2013. This Internet-Draft will expire on December 19, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. System Identification . . . . . . . . . . . . . . . . . . 5 2.1. System Identification . . . . . . . . . . . . . . . . . . 5
2.2. System Time Management . . . . . . . . . . . . . . . . . . 5 2.2. System Time Management . . . . . . . . . . . . . . . . . . 5
2.3. User Authentication . . . . . . . . . . . . . . . . . . . 5 2.3. User Authentication . . . . . . . . . . . . . . . . . . . 5
3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 6 2.4. DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. System Identification . . . . . . . . . . . . . . . . . . 6 2.5. System Control . . . . . . . . . . . . . . . . . . . . . . 6
3.2. System Time Management . . . . . . . . . . . . . . . . . . 6 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 7
3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6 3.1. System Identification . . . . . . . . . . . . . . . . . . 7
3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7 3.2. System Time Management . . . . . . . . . . . . . . . . . . 7
3.5. User Authentication Model . . . . . . . . . . . . . . . . 7 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 7
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 8
3.5.2. Local User Password Authentication . . . . . . . . . . 8 3.5. User Authentication Model . . . . . . . . . . . . . . . . 8
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 9 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 9
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9 3.5.2. Local User Password Authentication . . . . . . . . . . 9
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 11
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8. Normative References . . . . . . . . . . . . . . . . . . . . . 31 7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.7. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Normative References . . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for the This document defines a YANG [RFC6020] data model for the
configuration and identification of some common properties within the configuration and identification of some common properties within a
management system of a device. device containing a NETCONF server.
Devices that are managed by NETCONF and perhaps other mechanisms have Devices that are managed by NETCONF and perhaps other mechanisms have
common properties that need to be configured and monitored in a common properties that need to be configured and monitored in a
standard way. standard way.
The "ietf-system" YANG module defined in this document provides the The "ietf-system" YANG module defined in this document provides the
following features: following features:
o system administrative data configuration o system identification configuration and monitoring
o system identification monitoring
o system time-of-day configuration and monitoring o system time-of-day configuration and monitoring
o user authentication configuration o user authentication configuration
o local users configuration o local users configuration
o DNS resolver configuration
o system control operations (shutdown, restart, setting time)
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "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].
1.1.1. Terms
The following terms are used within this document:
o system: This term refers to the embodiment of the entire set of
management interfaces that a single NETCONF server is supporting
at a given moment. The set of physical entities managed by a
single NETCONF server can be static or it can change dynamically.
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write) and "ro" state data (read-only). (read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node and "*" o Symbols after data node names: "?" means an optional node and "*"
denotes a "leaf-list". denotes a "list" and "leaf-list".
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Objectives 2. Objectives
2.1. System Identification 2.1. System Identification
There are many common properties used to identify devices, operating There are many common properties used to identify devices, operating
systems, software versions, etc. that need to be supported in the systems, software versions, etc. that need to be supported in the
system data module. These objects are defined as operational data system data module. These objects are defined as operational state
and the information returned by the server is intended to be specific data and the information returned by the server is intended to be
to the device vendor. specific to the device vendor.
Some user-configurable administrative strings are also provided, such Some user-configurable administrative strings are also provided, such
as the system location and description. as the system location and description.
2.2. System Time Management 2.2. System Time Management
The management of the date and time used by the system need to be The management of the date and time used by the system need to be
supported. Use of one or more NTP servers to automatically set the supported. Use of one or more NTP servers to automatically set the
system date and time need to be possible. Utilization of the system date and time need to be possible. Utilization of the
Timezone database [RFC6557] also need to be supported. It should be Timezone database [RFC6557] also need to be supported. It should be
skipping to change at page 6, line 5 skipping to change at page 5, line 45
Since the mandatory transport protocol for NETCONF is SSH [RFC6242] Since the mandatory transport protocol for NETCONF is SSH [RFC6242]
the authentication model need to support SSH's "publickey" and the authentication model need to support SSH's "publickey" and
"password" authentication methods [RFC4252]. "password" authentication methods [RFC4252].
The model for authentication configuration should be flexible enough The model for authentication configuration should be flexible enough
to support authentication methods defined by other standard documents to support authentication methods defined by other standard documents
or by vendors. It should be possible for the server, as well as or by vendors. It should be possible for the server, as well as
clients, to configure the system authentication properties. clients, to configure the system authentication properties.
2.4. DNS Resolver
The configuration of the DNS resolver within the system containing
the NETCONF server is required to control how domain names are
resolved. An order list of DNS servers and some common parameters
such as the list of domains to search when resolving a host name.
2.5. System Control
A few operations are needed to support common tasks such as
restarting the device or setting the system date and time.
3. System Data Model 3. System Data Model
3.1. System Identification 3.1. System Identification
The data model for system identification has the following structure: The data model for system identification has the following structure:
+--rw system +--rw system
+--rw contact? string +--rw contact? string
+--rw hostname? inet:domain-name +--rw hostname? inet:domain-name
+--rw location? string +--rw location? string
skipping to change at page 6, line 32 skipping to change at page 7, line 32
The data model for system time management has the following The data model for system time management has the following
structure: structure:
+--rw system +--rw system
+--rw clock +--rw clock
| +--ro current-datetime? yang:date-and-time | +--ro current-datetime? yang:date-and-time
| +--ro boot-datetime? yang:date-and-time | +--ro boot-datetime? yang:date-and-time
| +--rw (timezone)? | +--rw (timezone)?
| +--:(timezone-location) | +--:(timezone-location)
| | +--rw timezone-location? string | | +--rw timezone-location? ianatz:iana-timezone
| +--:(timezone-utc-offset) | +--:(timezone-utc-offset)
| +--rw timezone-utc-offset? int16 | +--rw timezone-utc-offset? int16
+--rw ntp +--rw ntp
+--rw enabled? boolean +--rw enabled? boolean
+--rw server [address] +--rw server* [name]
+--rw association-type? enumeration +--rw name string
+--rw address inet:host +--rw (transport)
+--rw enabled? boolean | +--:(udp)
+--rw iburst? boolean | +--rw udp
+--rw prefer? boolean | +--rw address inet:host
| +--rw port? inet:port-number
+--rw association-type? enumeration
+--rw iburst? boolean
+--rw prefer? boolean
3.3. DNS Resolver Model 3.3. DNS Resolver Model
The data model for configuration of the DNS resolver has the The data model for configuration of the DNS resolver has the
following structure: following structure:
+--rw system +--rw system
+--rw dns +--rw dns-resolver
+--rw search* inet:domain-name +--rw search* inet:domain-name
+--rw server* inet:ip-address +--rw server* [name]
| +--rw name string
| +--rw (transport)
| +--:(udp)
| +--rw udp
| +--rw address inet:ip-address
| +--rw port? inet:port-number
+--rw options +--rw options
+--rw timeout? uint8 +--rw timeout? uint8
+--rw attempts? uint8 +--rw attempts? uint8
3.4. RADIUS Client Model 3.4. RADIUS Client Model
The data model for configuration of the RADIUS client has the The data model for configuration of the RADIUS client has the
following structure: following structure:
+--rw system +--rw system
+--rw radius +--rw radius
+--rw server [address] +--rw server* [name]
| +--rw address inet:host | +--rw name string
| +--rw (transport) | +--rw (transport)
| | +--:(udp) | | +--:(udp)
| | +--rw udp | | +--rw udp
| | +--rw address inet:host
| | +--rw authentication-port? inet:port-number | | +--rw authentication-port? inet:port-number
| | +--rw shared-secret string | | +--rw shared-secret string
| +--rw authentication-type? identityref | +--rw authentication-type? identityref
+--rw options +--rw options
+--rw timeout? uint8 +--rw timeout? uint8
+--rw attempts? uint8 +--rw attempts? uint8
3.5. User Authentication Model 3.5. User Authentication Model
This document defines three authentication methods for use with This document defines three authentication methods for use with
skipping to change at page 8, line 12 skipping to change at page 9, line 20
The authentication parameters defined in this document are primarily The authentication parameters defined in this document are primarily
used to configure authentication of NETCONF users, but MAY also be used to configure authentication of NETCONF users, but MAY also be
used by other interfaces, e.g., a Command Line Interface or a Web- used by other interfaces, e.g., a Command Line Interface or a Web-
based User Interface. based User Interface.
The data model for user authentication has the following structure: The data model for user authentication has the following structure:
+--rw system +--rw system
+--rw authentication +--rw authentication
+--rw user-authentication-order* identityref +--rw user-authentication-order* identityref
+--rw user [name] +--rw user* [name]
+--rw name string +--rw name string
+--rw password? crypt-hash +--rw password? crypt-hash
+--rw ssh-key [name] +--rw ssh-key* [name]
+--rw name string +--rw name string
+--rw algorithm? string +--rw algorithm string
+--rw key-data? binary +--rw key-data binary
3.5.1. SSH Public Key Authentication 3.5.1. SSH Public Key Authentication
If the NETCONF server advertises the "local-users" feature, If the NETCONF server advertises the "local-users" feature,
configuration of local users and their SSH public keys is supported configuration of local users and their SSH public keys is supported
in the /system/authentication/user list. in the /system/authentication/user list.
Public key authentication is requested by the SSH client. If the Public key authentication is requested by the SSH client. If the
"local-users" feature is supported, then when a NETCONF client starts "local-users" feature is supported, then when a NETCONF client starts
an SSH session towards the server using the "publickey" an SSH session towards the server using the "publickey"
skipping to change at page 8, line 49 skipping to change at page 10, line 8
For NETCONF transport protocols that support password authentication, For NETCONF transport protocols that support password authentication,
the leaf-list "user-authentication-order" is used to control if local the leaf-list "user-authentication-order" is used to control if local
user password authentication should be used. user password authentication should be used.
In SSH, password authentication is requested by the client. Other In SSH, password authentication is requested by the client. Other
NETCONF transport protocols MAY also support password authentication. NETCONF transport protocols MAY also support password authentication.
When local user password authentication is requested, the NETCONF When local user password authentication is requested, the NETCONF
transport looks up the user name provided by the client in the transport looks up the user name provided by the client in the
/system/ authentication/user list, and verifies the password. /system/authentication/user list, and verifies the password.
3.5.3. RADIUS Password Authentication 3.5.3. RADIUS Password Authentication
If the NETCONF server advertises the "radius-authentication" feature, If the NETCONF server advertises the "radius-authentication" feature,
the device supports user authentication using RADIUS. the device supports user authentication using RADIUS.
For NETCONF transport protocols that support password authentication, For NETCONF transport protocols that support password authentication,
the leaf-list "user-authentication-order" is used to control if the leaf-list "user-authentication-order" is used to control if
RADIUS password authentication should be used. RADIUS password authentication should be used.
skipping to change at page 10, line 16 skipping to change at page 11, line 16
This YANG module imports YANG extensions from [RFC6536], and imports This YANG module imports YANG extensions from [RFC6536], and imports
YANG types from [I-D.ietf-netmod-rfc6021-bis] and YANG types from [I-D.ietf-netmod-rfc6021-bis] and
[I-D.ietf-netmod-iana-timezones]. It also references [RFC1321], [I-D.ietf-netmod-iana-timezones]. It also references [RFC1321],
[RFC2865], [RFC3418], [RFC5607], [IEEE-1003.1-2008], and [RFC2865], [RFC3418], [RFC5607], [IEEE-1003.1-2008], and
[FIPS.180-3.2008]. [FIPS.180-3.2008].
RFC Ed.: update the date below with the date of RFC publication and RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-system@2013-04-21.yang" <CODE BEGINS> file "ietf-system@2013-06-17.yang"
module ietf-system { module ietf-system {
namespace "urn:ietf:params:xml:ns:yang:ietf-system"; namespace "urn:ietf:params:xml:ns:yang:ietf-system";
prefix "sys"; prefix "sys";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-inet-types { import ietf-inet-types {
skipping to change at page 11, line 10 skipping to change at page 12, line 10
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
Editor: Andy Bierman Editor: Andy Bierman
<mailto:andy@yumaworks.com> <mailto:andy@yumaworks.com>
Editor: Martin Bjorklund Editor: Martin Bjorklund
<mailto:mbj@tail-f.com>"; <mailto:mbj@tail-f.com>";
description description
"This module contains a collection of YANG definitions for the "This module contains a collection of YANG definitions for the
configuration and identification of the management system of a configuration and identification of some common system
device. properties within a device containing a NETCONF server. This
includes data node definitions for system identification,
time-of-day management, user management, DNS resolver
configuration, and some protocol operations for system
management.
Copyright (c) 2013 IETF Trust and the persons identified as Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 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 // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: remove this note // RFC Ed.: remove this note
// Note: extracted from draft-ietf-netmod-system-mgmt-06.txt // Note: extracted from draft-ietf-netmod-system-mgmt-07.txt
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2013-04-21" { revision "2013-06-17" {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for System Management"; "RFC XXXX: A YANG Data Model for System Management";
} }
/* /*
* Typedefs * Typedefs
*/ */
skipping to change at page 12, line 31 skipping to change at page 13, line 36
If a value starting with '$<id>$', where <id> is not '0', is If a value starting with '$<id>$', where <id> is not '0', is
received, the server knows that the value already represents a received, the server knows that the value already represents a
hashed value, and stores it as is in the data store. hashed value, and stores it as is in the data store.
When a server needs to verify a password given by a user, it When a server needs to verify a password given by a user, it
finds the stored password hash string for that user, extracts finds the stored password hash string for that user, extracts
the salt, and calculates the hash with the salt and given the salt, and calculates the hash with the salt and given
password as input. If the calculated hash value is the same password as input. If the calculated hash value is the same
as the stored value, the password given by the client is as the stored value, the password given by the client is
correct. accepted.
This type defines the following hash functions: This type defines the following hash functions:
id | hash function | feature id | hash function | feature
---+---------------+------------------- ---+---------------+-------------------
1 | MD5 | crypt-hash-md5 1 | MD5 | crypt-hash-md5
5 | SHA-256 | crypt-hash-sha-256 5 | SHA-256 | crypt-hash-sha-256
6 | SHA-512 | crypt-hash-sha-512 6 | SHA-512 | crypt-hash-sha-512
The server indicates support for the different hash functions The server indicates support for the different hash functions
skipping to change at page 13, line 17 skipping to change at page 14, line 22
description description
"Indicates that the device can be configured as a RADIUS "Indicates that the device can be configured as a RADIUS
client."; client.";
reference reference
"RFC 2865: Remote Authentication Dial In User Service " "RFC 2865: Remote Authentication Dial In User Service "
+ "(RADIUS)"; + "(RADIUS)";
} }
feature authentication { feature authentication {
description description
"Indicates that the device can be configured "Indicates that the device supports configuration
to do authentication of users."; for user authentication.";
} }
feature local-users { feature local-users {
if-feature authentication; if-feature authentication;
description description
"Indicates that the device supports "Indicates that the device supports configuration of
local user authentication."; local user authentication.";
} }
feature radius-authentication { feature radius-authentication {
if-feature radius; if-feature radius;
if-feature authentication; if-feature authentication;
description description
"Indicates that the device supports user authentication over "Indicates that the device supports configuration of user
RADIUS."; authentication over RADIUS.";
reference reference
"RFC 2865: Remote Authentication Dial In User Service (RADIUS) "RFC 2865: Remote Authentication Dial In User Service (RADIUS)
RFC 5607: Remote Authentication Dial-In User Service (RADIUS) RFC 5607: Remote Authentication Dial-In User Service (RADIUS)
Authorization for Network Access Server (NAS) Authorization for Network Access Server (NAS)
Management"; Management";
} }
feature crypt-hash-md5 { feature crypt-hash-md5 {
description description
"Indicates that the device supports the MD5 "Indicates that the device supports the MD5
skipping to change at page 14, line 22 skipping to change at page 15, line 25
reference "FIPS.180-3.2008: Secure Hash Standard"; reference "FIPS.180-3.2008: Secure Hash Standard";
} }
feature ntp { feature ntp {
description description
"Indicates that the device can be configured "Indicates that the device can be configured
to use one or more NTP servers to set the to use one or more NTP servers to set the
system date and time."; system date and time.";
} }
feature ntp-udp-port {
description
"Indicates that the device supports the configuration of
the UDP port for NTP servers.
This is a 'feature' since many implementations do not support
any other port than the default port.";
}
feature timezone-location { feature timezone-location {
description description
"Indicates that the local timezone on the device "Indicates that the local timezone on the device
can be configured to use the TZ database can be configured to use the TZ database
to set the timezone and manage daylight savings time."; to set the timezone and manage daylight savings time.";
reference reference
"TZ Database http://www.twinsun.com/tz/tz-link.htm "TZ Database http://www.twinsun.com/tz/tz-link.htm
Maintaining the Timezone Database Maintaining the Timezone Database
RFC 6557 (BCP 175)"; RFC 6557 (BCP 175)";
} }
feature dns-udp-port {
description
"Indicates that the device supports the configuration of
the UDP port for DNS servers.
This is a 'feature' since many implementations do not support
any other port than the default port.";
}
/* /*
* Identities * Identities
*/ */
identity authentication-method { identity authentication-method {
description description
"Base identity for user authentication methods."; "Base identity for user authentication methods.";
} }
identity radius { identity radius {
skipping to change at page 15, line 43 skipping to change at page 17, line 18
/* /*
* Top-level container * Top-level container
*/ */
container system { container system {
description description
"System group configuration."; "System group configuration.";
leaf contact { leaf contact {
type string { type string;
length "0..255";
}
description description
"The administrator contact information for the system."; "The administrator contact information for the system.
The server MAY restrict the size and characters in
order to maintain compatibility with the sysContact
MIB object.";
reference reference
"RFC 3418 - Management Information Base (MIB) for the "RFC 3418 - Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP) Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysContact"; SNMPv2-MIB.sysContact";
} }
leaf hostname { leaf hostname {
type inet:domain-name; type inet:domain-name;
description description
"The name of the host. This name can be a single domain "The name of the host. This name can be a single domain
label, or the fully qualified domain name of the host."; label, or the fully qualified domain name of the host.";
} }
leaf location { leaf location {
type string { type string;
length "0..255";
}
description description
"The system location."; "The system location. The server MAY restrict the size
and characters in order to maintain compatibility with
the sysLocation MIB object.";
reference reference
"RFC 3418 - Management Information Base (MIB) for the "RFC 3418 - Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP) Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysLocation"; SNMPv2-MIB.sysLocation";
} }
container platform { container platform {
config false; config false;
description description
"Contains vendor-specific information for "Contains vendor-specific information for
identifying the system platform and operating system."; identifying the system platform and operating system.";
reference reference
"IEEE Std 1003.1-2008 - sys/utsname.h"; "IEEE Std 1003.1-2008 - sys/utsname.h";
leaf os-name { leaf os-name {
type string; type string;
skipping to change at page 17, line 37 skipping to change at page 18, line 52
description description
"Configuration and monitoring of the system "Configuration and monitoring of the system
date and time properties."; date and time properties.";
leaf current-datetime { leaf current-datetime {
type yang:date-and-time; type yang:date-and-time;
config false; config false;
description description
"The current system date and time."; "The current system date and time.";
} }
leaf boot-datetime { leaf boot-datetime {
type yang:date-and-time; type yang:date-and-time;
config false; config false;
description description
"The system date and time when the NETCONF "The system date and time when the system last restarted.";
server last restarted.";
} }
choice timezone { choice timezone {
description description
"The system timezone information."; "The system timezone information.";
leaf timezone-location { case timezone-location {
if-feature timezone-location; if-feature timezone-location;
type ianatz:iana-timezone; leaf timezone-location {
description type ianatz:iana-timezone;
"The TZ database location identifier string description
to use for the system, such as 'Europe/Stockholm'."; "The TZ database location identifier string
to use for the system, such as 'Europe/Stockholm'.";
}
} }
case timezone-utc-offset {
leaf timezone-utc-offset { leaf timezone-utc-offset {
type int16 { type int16 {
range "-1500 .. 1500"; range "-1500 .. 1500";
}
units "minutes";
description
"The number of minutes to add to UTC time to
identify the timezone for this system. For example,
'UTC - 8:00 hours' would be represented as '-480'.
Note that automatic daylight savings time adjustment
is not provided, if this object is used.";
} }
units "minutes";
description
"The number of minutes to add to UTC time to
identify the timezone for this system.
For example, 'UTC - 8:00 hours' would be
represented as '-480'. Note that automatic
daylight savings time adjustment is not provided,
if this object is used.";
} }
} }
} }
container ntp { container ntp {
if-feature ntp; if-feature ntp;
description description
"Configuration of the NTP client."; "Configuration of the NTP client.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default true;
description description
"Indicates that the system should attempt "Indicates that the system should attempt
to synchronize the system clock with an to synchronize the system clock with an
NTP server from the 'ntp/server' list."; NTP server from the 'ntp/server' list.";
skipping to change at page 18, line 40 skipping to change at page 20, line 4
"Configuration of the NTP client."; "Configuration of the NTP client.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default true;
description description
"Indicates that the system should attempt "Indicates that the system should attempt
to synchronize the system clock with an to synchronize the system clock with an
NTP server from the 'ntp/server' list."; NTP server from the 'ntp/server' list.";
} }
list server { list server {
key address; key name;
description description
"List of NTP servers to use for "List of NTP servers to use for
system clock synchronization. If '/system/ntp/enabled' system clock synchronization. If '/system/ntp/enabled'
is 'true', then the system will attempt to is 'true', then the system will attempt to
contact and utilize the specified NTP servers."; contact and utilize the specified NTP servers.";
leaf name {
type string;
description
"An arbitrary name for the NTP server.";
}
choice transport {
mandatory true;
description
"The transport protocol specific parameters for this
server.
It is expected that new case statements will be added
over time to support other transport protocols.";
case udp {
container udp {
description
"Contains UDP specific configuration parameters
for NTP.";
leaf address {
type inet:host;
mandatory true;
description
"The address of the NTP server.";
}
leaf port {
if-feature ntp-udp-port;
type inet:port-number;
default 123;
description
"The port number of the NTP server.";
}
}
}
}
leaf association-type { leaf association-type {
type enumeration { type enumeration {
enum server { enum server {
description description
"Use client association mode. This device "Use client association mode. This device
will not provide synchronization to the will not provide synchronization to the
configured NTP server."; configured NTP server.";
} }
enum peer { enum peer {
description description
skipping to change at page 19, line 28 skipping to change at page 21, line 25
more of the NTP servers found by DNS more of the NTP servers found by DNS
resolution of the domain name given by resolution of the domain name given by
the 'address' leaf. This device will not the 'address' leaf. This device will not
provide synchronization to the servers."; provide synchronization to the servers.";
} }
} }
default server; default server;
description description
"The desired association type for this NTP server."; "The desired association type for this NTP server.";
} }
leaf address {
type inet:host;
description
"The IP address or domain name of the NTP server.";
}
leaf enabled {
type boolean;
default true;
description
"Indicates whether this server is enabled for use or
not.";
}
leaf iburst { leaf iburst {
type boolean; type boolean;
default false; default false;
description description
"Indicates whether this server should enable burst "Indicates whether this server should enable burst
synchronization or not."; synchronization or not.";
} }
leaf prefer { leaf prefer {
type boolean; type boolean;
default false; default false;
description description
"Indicates whether this server should be preferred "Indicates whether this server should be preferred
or not."; or not.";
} }
} }
} }
container dns { container dns-resolver {
description description
"Configuration of the DNS resolver."; "Configuration of the DNS resolver.";
leaf-list search { leaf-list search {
type inet:domain-name; type inet:domain-name;
ordered-by user; ordered-by user;
description description
"An ordered list of domains to search when resolving "An ordered list of domains to search when resolving
a host name."; a host name.";
} }
leaf-list server { list server {
type inet:ip-address; key name;
ordered-by user; ordered-by user;
description description
"Addresses of the name servers that the resolver should "List of the DNS servers that the resolver should query.
query.
When the resolver is invoked by a calling application, it
sends the query to the first name server in this list. If
no response has been received within 'timeout' seconds,
the resolver continues with the next server in the list.
If no response is received from any server, the resolver
continues with the first server again. When the resolver
has traversed the list 'attempts' times without receiving
any response, it gives up and returns an error to the
calling application.
Implementations MAY limit the number of entries in this Implementations MAY limit the number of entries in this
leaf list."; list.";
leaf name {
type string;
description
"An arbitrary name for the DNS server.";
}
choice transport {
mandatory true;
description
"The transport protocol specific parameters for this
server.
It is expected that new case statements will be added
over time to support other transport protocols.";
case udp {
container udp {
description
"Contains UDP specific configuration parameters
for DNS.";
leaf address {
type inet:ip-address;
mandatory true;
description
"The address of the DNS server.";
}
leaf port {
if-feature dns-udp-port;
type inet:port-number;
default 53;
description
"The port number of the DNS server.";
}
}
}
}
} }
container options { container options {
description description
"Resolver options. The set of available options has been "Resolver options. The set of available options has been
limited to those that are generally available across limited to those that are generally available across
different resolver implementations, and generally different resolver implementations, and generally
useful."; useful.";
leaf timeout { leaf timeout {
type uint8 { type uint8 {
range "1..max"; range "1..max";
} }
units "seconds"; units "seconds";
default "5"; default "5";
description description
"The amount of time the resolver will wait for a "The amount of time the resolver will wait for a
response from a remote name server before response from each remote name server before
retrying the query via a different name server."; retrying the query via a different name server.";
} }
leaf attempts { leaf attempts {
type uint8 { type uint8 {
range "1..max"; range "1..max";
} }
default "2"; default "2";
description description
"The number of times the resolver will send a query to "The number of times the resolver will send a query to
its name servers before giving up and returning an all its name servers before giving up and returning an
error to the calling application."; error to the calling application.";
} }
} }
} }
container radius { container radius {
if-feature radius; if-feature radius;
description description
"Configuration of the RADIUS client."; "Configuration of the RADIUS client.";
list server { list server {
key address; key name;
ordered-by user; ordered-by user;
description description
"List of RADIUS servers used by the device."; "List of RADIUS servers used by the device.
leaf address { When the RADIUS client is invoked by a calling
type inet:host; application, it sends the query to the first server in
this list. If no response has been received within
'timeout' seconds, the client continues with the next
server in the list. If no response is received from any
server, the client continues with the first server again.
When the client has traversed the list 'attempts' times
without receiving any response, it gives up and returns an
error to the calling application.";
leaf name {
type string;
description description
"The address of the RADIUS server."; "An arbitrary name for the RADIUS server.";
} }
choice transport { choice transport {
mandatory true; mandatory true;
description description
"The transport protocol specific parameters "The transport protocol specific parameters
for this server. It is expected that new for this server. It is expected that new
case statements will be added over time to case statements will be added over time to
support other transport protocols."; support other transport protocols.";
case udp { case udp {
container udp { container udp {
description description
"Contains UDP specific configuration parameters "Contains UDP specific configuration parameters
for RADIUS."; for RADIUS.";
leaf address {
type inet:host;
mandatory true;
description
"The address of the RADIUS server.";
}
leaf authentication-port { leaf authentication-port {
type inet:port-number; type inet:port-number;
default "1812"; default "1812";
description description
"The port number of the RADIUS server."; "The port number of the RADIUS server.";
} }
leaf shared-secret { leaf shared-secret {
type string; type string;
mandatory true; mandatory true;
nacm:default-deny-all; nacm:default-deny-all;
skipping to change at page 22, line 35 skipping to change at page 25, line 31
"RADIUS client options."; "RADIUS client options.";
leaf timeout { leaf timeout {
type uint8 { type uint8 {
range "1..max"; range "1..max";
} }
units "seconds"; units "seconds";
default "5"; default "5";
description description
"The number of seconds the device will wait for a "The number of seconds the device will wait for a
response from a RADIUS server before trying with a response from each RADIUS server before trying with a
different server."; different server.";
} }
leaf attempts { leaf attempts {
type uint8 { type uint8 {
range "1..max"; range "1..max";
} }
default "2"; default "2";
description description
"The number of times the device will send a query to "The number of times the device will send a query to
the RADIUS servers before giving up."; all its RADIUS servers before giving up.";
} }
} }
} }
container authentication { container authentication {
nacm:default-deny-write; nacm:default-deny-write;
if-feature authentication; if-feature authentication;
description description
"The authentication configuration subtree."; "The authentication configuration subtree.";
skipping to change at page 24, line 22 skipping to change at page 27, line 17
"RFC 4253: The Secure Shell (SSH) Transport Layer "RFC 4253: The Secure Shell (SSH) Transport Layer
Protocol"; Protocol";
leaf name { leaf name {
type string; type string;
description description
"An arbitrary name for the ssh key."; "An arbitrary name for the ssh key.";
} }
leaf algorithm { leaf algorithm {
type string; type string;
mandatory true;
description description
"The public key algorithm name for this ssh key. "The public key algorithm name for this ssh key.
Valid values are the values in the IANA Secure Shell Valid values are the values in the IANA Secure Shell
(SSH) Protocol Parameters registry, Public Key (SSH) Protocol Parameters registry, Public Key
Algorithm Names"; Algorithm Names";
reference reference
"IANA Secure Shell (SSH) Protocol Parameters registry, "IANA Secure Shell (SSH) Protocol Parameters registry,
Public Key Algorithm Names"; Public Key Algorithm Names";
} }
leaf key-data { leaf key-data {
type binary; type binary;
mandatory true;
description description
"The binary key data for this ssh key."; "The binary key data for this ssh key.";
} }
} }
} }
} }
} }
rpc set-current-datetime { rpc set-current-datetime {
nacm:default-deny-all; nacm:default-deny-all;
skipping to change at page 27, line 10 skipping to change at page 30, line 10
name: ietf-system name: ietf-system
namespace: urn:ietf:params:xml:ns:yang:ietf-system namespace: urn:ietf:params:xml:ns:yang:ietf-system
prefix: sys prefix: sys
reference: RFC XXXX reference: RFC XXXX
6. Security Considerations 6. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. transport is SSH [RFC6242]. Authorization for access to specific
portions of conceptual data and operations within this module is
provided by the NETCONF access control model (NACM) [RFC6536].
There are a number of data nodes defined in this YANG module which There are a number of data nodes defined in this YANG module which
are writable/creatable/deletable (i.e., config true, which is the are writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
o /system/clock/timezone: This choice contains the objects used to o /system/clock/timezone: This choice contains the objects used to
control the timezone used by the device. control the timezone used by the device.
o /system/ntp: This container contains the objects used to control o /system/ntp: This container contains the objects used to control
the Network Time Protocol servers used by the device. the Network Time Protocol servers used by the device.
o /system/dns: This container contains the objects used to control o /system/dns-resolver: This container contains the objects used to
the Domain Name System servers used by the device. control the Domain Name System servers used by the device.
o /system/radius: This container contains the objects used to o /system/radius: This container contains the objects used to
control the Remote Authentication Dial-In User Service servers control the Remote Authentication Dial-In User Service servers
used by the device. used by the device.
o /system/authentication/user-authentication-order: This leaf o /system/authentication/user-authentication-order: This leaf
controls how user login attempts are authenticated by the device. controls how user login attempts are authenticated by the device.
o /system/authentication/user: This list contains the local users o /system/authentication/user: This list contains the local users
enabled on the system. enabled on the system.
skipping to change at page 27, line 49 skipping to change at page 30, line 51
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
o /system/platform: This container has objects which may help o /system/platform: This container has objects which may help
identify the specific NETCONF server and/or operating system identify the specific NETCONF server and/or operating system
implementation used on the device. implementation used on the device.
o /system/authentication/user: This list has objects that may help
identify the specific user names and password information in use
on the device.
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the important to control access to these operations. These are the
operations and their sensitivity/vulnerability: operations and their sensitivity/vulnerability:
o set-current-datetime: Changes the current date and time on the o set-current-datetime: Changes the current date and time on the
device. device.
o system-restart: Reboots the device. o system-restart: Reboots the device.
skipping to change at page 31, line 5 skipping to change at page 33, line 46
o changed /system/platform/nodename to /system/platform/hostname o changed /system/platform/nodename to /system/platform/hostname
o changed /system/radius/server/{leafs} to be within a choice and o changed /system/radius/server/{leafs} to be within a choice and
'udp' case statement so other transport specific parameters can 'udp' case statement so other transport specific parameters can
augment this list or they can be added by the WG to a future augment this list or they can be added by the WG to a future
version of this module. {leafs} are authentication-port and version of this module. {leafs} are authentication-port and
shared-secret. shared-secret.
o updated YANG tree diagrams for objects added in -05 and -06 o updated YANG tree diagrams for objects added in -05 and -06
8. Normative References 7.7. 06-07
o updated the Abstract and Introduction
o updated Tree diagram notation
o identify all external servers (dns, ntp, radius) by name instead
of address, in order to make the data model extensible for
additional transport protocol.
o updated the Security Considerations section with a reference to
NACM.
8. References
8.1. Normative References
[FIPS.180-3.2008] [FIPS.180-3.2008]
National Institute of Standards and Technology, "Secure National Institute of Standards and Technology, "Secure
Hash Standard", FIPS PUB 180-3, October 2008, <http:// Hash Standard", FIPS PUB 180-3, October 2008, <http://
csrc.nist.gov/publications/fips/fips180-3/ csrc.nist.gov/publications/fips/fips180-3/
fips180-3_final.pdf>. fips180-3_final.pdf>.
[I-D.ietf-netmod-iana-timezones] [I-D.ietf-netmod-iana-timezones]
Lange, J., "IANA Timezone Database YANG Module", Lange, J., "IANA Timezone Database YANG Module",
draft-ietf-netmod-iana-timezones-00 (work in progress), draft-ietf-netmod-iana-timezones-00 (work in progress),
July 2012. July 2012.
[I-D.ietf-netmod-rfc6021-bis] [I-D.ietf-netmod-rfc6021-bis]
Schoenwaelder, J., "Common YANG Data Types", Schoenwaelder, J., "Common YANG Data Types",
draft-ietf-netmod-rfc6021-bis-01 (work in progress), draft-ietf-netmod-rfc6021-bis-02 (work in progress),
March 2013. May 2013.
[IEEE-1003.1-2008] [IEEE-1003.1-2008]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
"POSIX.1-2008", IEEE Standard 1003.1, March 2008. "POSIX.1-2008", IEEE Standard 1003.1, March 2008.
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
[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.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, December 2002.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC4252] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) [RFC4252] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
Authentication Protocol", RFC 4252, January 2006. Authentication Protocol", RFC 4252, January 2006.
[RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) [RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
Transport Layer Protocol", RFC 4253, January 2006. Transport Layer Protocol", RFC 4253, January 2006.
[RFC5607] Nelson, D. and G. Weber, "Remote Authentication Dial-In [RFC5607] Nelson, D. and G. Weber, "Remote Authentication Dial-In
User Service (RADIUS) Authorization for Network Access User Service (RADIUS) Authorization for Network Access
Server (NAS) Management", RFC 5607, July 2009. Server (NAS) Management", RFC 5607, July 2009.
skipping to change at page 32, line 20 skipping to change at page 36, line 20
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, June 2011. (NETCONF)", RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, June 2011.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
March 2012. March 2012.
8.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC6557] Lear, E. and P. Eggert, "Procedures for Maintaining the [RFC6557] Lear, E. and P. Eggert, "Procedures for Maintaining the
Time Zone Database", BCP 175, RFC 6557, February 2012. Time Zone Database", BCP 175, RFC 6557, February 2012.
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
YumaWorks YumaWorks
Email: andy@yumaworks.com Email: andy@yumaworks.com
 End of changes. 76 change blocks. 
146 lines changed or deleted 294 lines changed or added

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