draft-ietf-netmod-system-mgmt-05.txt   draft-ietf-netmod-system-mgmt-06.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: August 29, 2013 Tail-f Systems Expires: October 23, 2013 Tail-f Systems
February 25, 2013 April 21, 2013
YANG Data Model for System Management YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-05 draft-ietf-netmod-system-mgmt-06
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 the management system of a device.
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.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 August 29, 2013. This Internet-Draft will expire on October 23, 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
skipping to change at page 2, line 23 skipping to change at page 2, line 23
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 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 6
3.1. System Identification . . . . . . . . . . . . . . . . . . 6 3.1. System Identification . . . . . . . . . . . . . . . . . . 6
3.2. System Time Management . . . . . . . . . . . . . . . . . . 6 3.2. System Time Management . . . . . . . . . . . . . . . . . . 6
3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6
3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7
3.5. User Authentication Model . . . . . . . . . . . . . . . . 7 3.5. User Authentication Model . . . . . . . . . . . . . . . . 7
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8
3.5.2. Local User Password Authentication . . . . . . . . . . 8 3.5.2. Local User Password Authentication . . . . . . . . . . 8
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 8 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 9
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8. Normative References . . . . . . . . . . . . . . . . . . . . . 30 7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 8. Normative References . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
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 the management system of a configuration and identification of some common properties within the
device. management system of a device.
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 administrative data configuration
skipping to change at page 5, line 12 skipping to change at page 5, line 12
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 data
and intended to be specific to the device vendor. and the information returned by the server is intended to be 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. Timezone database [RFC6557] also need to be supported. It should be
possible for the server, as well as clients, to configure the system
to use NTP.
2.3. User Authentication 2.3. User Authentication
The authentication mechanism need to support password authentication The authentication mechanism need to support password authentication
over RADIUS, to support deployment scenarios with centralized over RADIUS, to support deployment scenarios with centralized
authentication servers. Additionally, local users need to be authentication servers. Additionally, local users need to be
supported, for scenarios when no centralized authentication server supported, for scenarios when no centralized authentication server
exists, or for situations where the centralized authentication server exists, or for situations where the centralized authentication server
cannot be reached from the device. cannot be reached from the device.
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. or by vendors. It should be possible for the server, as well as
clients, to configure the system authentication properties.
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 name? string +--rw hostname? inet:domain-name
+--rw location? string +--rw location? string
+--ro platform +--ro platform
+--ro os-name? string +--ro os-name? string
+--ro os-release? string +--ro os-release? string
+--ro os-version? string +--ro os-version? string
+--ro machine? string +--ro machine? string
+--ro nodename? string
3.2. System Time Management 3.2. System Time Management
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? string
| +--:(timezone-utc-offset) | +--:(timezone-utc-offset)
| +--rw timezone-utc-offset? int16 | +--rw timezone-utc-offset? int16
+--rw ntp +--rw ntp
+--rw use-ntp? boolean +--rw enabled? boolean
+--rw ntp-server [address] +--rw server [address]
+--rw association-type? enumeration +--rw association-type? enumeration
+--rw address inet:host +--rw address inet:host
+--rw enabled? boolean +--rw enabled? boolean
+--rw iburst? boolean +--rw iburst? boolean
+--rw prefer? 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
+--rw search* inet:host +--rw search* inet:domain-name
+--rw server* inet:ip-address +--rw server* inet:ip-address
+--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 [address]
| +--rw address inet:host | +--rw address inet:host
| +--rw authentication-port? inet:port-number | +--rw (transport)
| +--rw shared-secret? string | | +--:(udp)
| | +--rw udp
| | +--rw authentication-port? inet:port-number
| | +--rw shared-secret string
| +--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
NETCONF: NETCONF:
o publickey for local users over SSH o publickey for local users over SSH
skipping to change at page 10, line 8 skipping to change at page 10, line 8
3.6. System Control 3.6. System Control
Two protocol operations are included to restart or shutdown the Two protocol operations are included to restart or shutdown the
system. The 'system-restart' operation can be used to restart the system. The 'system-restart' operation can be used to restart the
entire system (not just the NETCONF server). The 'system-shutdown' entire system (not just the NETCONF server). The 'system-shutdown'
operation can be used to power off the entire system. operation can be used to power off the entire system.
4. System YANG module 4. System YANG module
This YANG module imports YANG extensions from [RFC6536], and imports This YANG module imports YANG extensions from [RFC6536], and imports
YANG types from [RFC6021] and [I-D.lange-netmod-iana-timezones]. It YANG types from [I-D.ietf-netmod-rfc6021-bis] and
also references [RFC1321], [RFC2865], [RFC3418], [RFC5607], [I-D.ietf-netmod-iana-timezones]. It also references [RFC1321],
[IEEE-1003.1-2008], and [FIPS.180-3.2008]. [RFC2865], [RFC3418], [RFC5607], [IEEE-1003.1-2008], and
[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-02-25.yang" <CODE BEGINS> file "ietf-system@2013-04-21.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 13 skipping to change at page 11, line 13
<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 the management system of a
device. device.
Copyright (c) 2012 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-05.txt // Note: extracted from draft-ietf-netmod-system-mgmt-06.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-02-25" { revision "2013-04-21" {
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
*/ */
typedef crypt-hash { typedef crypt-hash {
type string { type string {
pattern "$0$.*|$(1|5|6)$[a-zA-Z0-9./]{2,16}$.*"; pattern
'$0$.*'
+ '|$1$[a-zA-Z0-9./]{1,8}$[a-zA-Z0-9./]{22}'
+ '|$5$(rounds=\d+$)?[a-zA-Z0-9./]{1,16}$[a-zA-Z0-9./]{43}'
+ '|$6$(rounds=\d+$)?[a-zA-Z0-9./]{1,16}$[a-zA-Z0-9./]{86}';
} }
description description
"The crypt-hash type is used to store passwords using "The crypt-hash type is used to store passwords using
a hash function. This type is implemented in various UNIX a hash function. The algorithms for applying the hash
systems as the function crypt(3). function and encoding the result are implemented in
various UNIX systems as the function crypt(3).
When a clear text value is set to a leaf of this type, the
server calculates a password hash, and stores the result
in the datastore. Thus, the password is never stored in
clear text.
When a leaf of this type is read, the stored password hash is
returned.
A value of this type matches one of the forms: A value of this type matches one of the forms:
$0$<clear text password> $0$<clear text password>
$<id>$<salt>$<password hash> $<id>$<salt>$<password hash>
$<id>$<parameter>$<salt>$<password hash>
The '$0$' prefix signals that the value is clear text. When The '$0$' prefix signals that the value is clear text. When
such a value is received by the server, a hash value is such a value is received by the server, a hash value is
calculated, and the string '$<id>$<salt>$' is prepended to the calculated, and the string '$<id>$<salt>$' or
result, where <salt> is a random 2-16 characters long salt $<id>$<parameter>$<salt>$ is prepended to the result. This
used to generate the digest. This value is stored in the value is stored in the configuration data store.
configuration data store.
If a value starting with '$<id>$<salt>$' is received, the If a value starting with '$<id>$', where <id> is not '0', is
server knows that the value already represents a hashed value, received, the server knows that the value already represents a
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. correct.
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
by advertising the corresponding feature."; by advertising the corresponding feature.";
reference reference
"IEEE Std 1003.1-2008 - crypt() function "IEEE Std 1003.1-2008 - crypt() function
Wikipedia: http://en.wikipedia.org/wiki/Crypt_(Unix) Wikipedia: http://en.wikipedia.org/wiki/Crypt_(C)
RFC 1321: The MD5 Message-Digest Algorithm RFC 1321: The MD5 Message-Digest Algorithm
FIPS.180-3.2008: Secure Hash Standard"; FIPS.180-3.2008: Secure Hash Standard";
} }
/* /*
* Features * Features
*/ */
feature radius { feature radius {
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 "
skipping to change at page 16, line 6 skipping to change at page 16, line 4
leaf contact { leaf contact {
type string { type string {
length "0..255"; length "0..255";
} }
description description
"The administrator contact information for the system."; "The administrator contact information for the system.";
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 name { leaf hostname {
type string { type inet:domain-name;
length "0..255"; description
} "The name of the host. This name can be a single domain
description label, or the fully qualified domain name of the host.";
"The administratively assigned system name.";
reference
"RFC 3418 - Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysName";
} }
leaf location { leaf location {
type string { type string {
length "0..255"; length "0..255";
} }
description description
"The system location"; "The system location.";
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
skipping to change at page 17, line 31 skipping to change at page 17, line 24
leaf machine { leaf machine {
type string; type string;
description description
"A vendor-specific identifier string representing "A vendor-specific identifier string representing
the hardware in use."; the hardware in use.";
reference reference
"IEEE Std 1003.1-2008 - utsname.machine"; "IEEE Std 1003.1-2008 - utsname.machine";
} }
leaf nodename {
type string;
description
"The host name of this system.";
reference
"IEEE Std 1003.1-2008 - utsname.nodename";
}
} }
container clock { container clock {
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;
skipping to change at page 18, line 46 skipping to change at page 18, line 32
} }
} }
} }
container ntp { container ntp {
if-feature ntp; if-feature ntp;
description description
"Configuration of the NTP client."; "Configuration of the NTP client.";
leaf use-ntp { 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 ntp-server { list server {
key address; key address;
description description
"List of NTP servers to use for "List of NTP servers to use for
system clock synchronization. If 'use-ntp' 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 association-type { leaf association-type {
type enumeration { type enumeration {
enum server { enum server {
description description
"Use server association mode. This device "Use client association mode. This device
is not expected to synchronize with the will not provide synchronization to the
configured NTP server."; configured NTP server.";
} }
enum peer { enum peer {
description description
"Use peer association mode. This device "Use symmetric active association mode.
may be expected to synchronize with the This device may provide synchronization
configured NTP server."; to the configured NTP server.";
} }
enum pool { enum pool {
description description
"Use pool association mode. This device "Use client association mode with one or
is not expected to synchronize with the more of the NTP servers found by DNS
configured NTP server."; resolution of the domain name given by
the 'address' leaf. This device will not
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 { leaf address {
type inet:host; type inet:host;
description description
"The IP address or domain name of the NTP server."; "The IP address or domain name of the NTP server.";
skipping to change at page 20, line 26 skipping to change at page 20, line 14
or not."; or not.";
} }
} }
} }
container dns { container dns {
description description
"Configuration of the DNS resolver."; "Configuration of the DNS resolver.";
leaf-list search { leaf-list search {
type inet:host; 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 { leaf-list server {
type inet:ip-address; type inet:ip-address;
ordered-by user; ordered-by user;
description description
"Addresses of the name servers that the resolver should "Addresses of the name servers that the resolver should
skipping to change at page 21, line 41 skipping to change at page 21, line 29
key address; key address;
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 { leaf address {
type inet:host; type inet:host;
description description
"The address of the RADIUS server."; "The address of the RADIUS server.";
} }
leaf authentication-port { choice transport {
type inet:port-number; mandatory true;
default "1812";
description
"The port number of the RADIUS server.";
}
leaf shared-secret {
type string;
nacm:default-deny-all;
description description
"The shared secret which is known to both the RADIUS "The transport protocol specific parameters
client and server."; for this server. It is expected that new
reference case statements will be added over time to
"RFC 2865: Remote Authentication Dial In User Service"; support other transport protocols.";
case udp {
container udp {
description
"Contains UDP specific configuration parameters
for RADIUS.";
leaf authentication-port {
type inet:port-number;
default "1812";
description
"The port number of the RADIUS server.";
}
leaf shared-secret {
type string;
mandatory true;
nacm:default-deny-all;
description
"The shared secret which is known to both the
RADIUS client and server.";
reference
"RFC 2865: Remote Authentication Dial In User
Service";
}
}
}
} }
leaf authentication-type { leaf authentication-type {
type identityref { type identityref {
base radius-authentication-type; base radius-authentication-type;
} }
default radius-pap; default radius-pap;
description description
"The authentication type requested from the RADIUS "The authentication type requested from the RADIUS
server."; server.";
} }
skipping to change at page 23, line 9 skipping to change at page 23, line 13
nacm:default-deny-write; nacm:default-deny-write;
if-feature authentication; if-feature authentication;
description description
"The authentication configuration subtree."; "The authentication configuration subtree.";
leaf-list user-authentication-order { leaf-list user-authentication-order {
type identityref { type identityref {
base authentication-method; base authentication-method;
} }
must '(. = "sys:radius" and ../../radius/server) or' must '(. != "sys:radius" or ../../radius/server)' {
+ '(. != "sys:radius")' {
error-message error-message
"When 'radius' is used, a radius server" "When 'radius' is used, a RADIUS server"
+ " must be configured."; + " must be configured.";
description
"When 'radius' is used as an authentication method,
a RADIUS server must be configured.";
} }
ordered-by user; ordered-by user;
description description
"When the device authenticates a user with "When the device authenticates a user with
a password, it tries the authentication methods in this a password, it tries the authentication methods in this
leaf-list in order. If authentication with one method leaf-list in order. If authentication with one method
fails, the next method is used. If no method succeeds, fails, the next method is used. If no method succeeds,
the user is denied access. the user is denied access.
skipping to change at page 24, line 42 skipping to change at page 24, line 48
} }
} }
} }
rpc set-current-datetime { rpc set-current-datetime {
nacm:default-deny-all; nacm:default-deny-all;
description description
"Set the /system/clock/current-datetime leaf "Set the /system/clock/current-datetime leaf
to the specified value. to the specified value.
If the system is using NTP (e.g., /system/ntp/use-ntp If the system is using NTP (i.e., /system/ntp/enabled
is set to 'true'), then this operation will is set to 'true'), then this operation will
fail with error-tag 'operation-failed', fail with error-tag 'operation-failed',
and error-app-tag value of 'ntp-active'"; and error-app-tag value of 'ntp-active'";
input { input {
leaf current-datetime { leaf current-datetime {
type yang:date-and-time; type yang:date-and-time;
mandatory true; mandatory true;
description description
"The current system date and time."; "The current system date and time.";
} }
} }
} }
rpc system-restart { rpc system-restart {
nacm:default-deny-all; nacm:default-deny-all;
description description
"Request that the entire system be restarted immediately. "Request that the entire system be restarted immediately.
A server SHOULD send an rpc reply to the client before A server SHOULD send an rpc reply to the client before
restarting the system."; restarting the system.";
} }
skipping to change at page 30, line 5 skipping to change at page 30, line 5
o added radius-authentication-type identity, and identities for pap o added radius-authentication-type identity, and identities for pap
and chap, and a leaf to control which authentication type to use and chap, and a leaf to control which authentication type to use
when communicating with the radius server when communicating with the radius server
o made 0 an invalid value for timeouts and attempts o made 0 an invalid value for timeouts and attempts
7.5. 04-05 7.5. 04-05
o updated tree diagram explanation text o updated tree diagram explanation text
7.6. 05-06
o changed ntp/use-ntp to ntp/enabled
o changed ntp/ntp-server to ntp/server
o removed /system/platform/nodename leaf
o changed /system/name to /system/hostname
o simplified must expression in user-authentication-order
o added optional rounds to sha hash definition
o clarified the crypt-hash description
o clarified ntp descriptions
o clarified YANG module description to indicate that some system
properties are supported, not the entire system
o clarified that system identification values are vendor specific,
not the data node objects
o clarified sec. 2.2 and 2.3 to indicate that the server should also
be capable of configuring these properties
o changed /system/dns/search from inet:host to inet:domain-name
o changed RFC6021 reference to 6021-bis
o changed /system/platform/nodename to /system/platform/hostname
o changed /system/radius/server/{leafs} to be within a choice and
'udp' case statement so other transport specific parameters can
augment this list or they can be added by the WG to a future
version of this module. {leafs} are authentication-port and
shared-secret.
o updated YANG tree diagrams for objects added in -05 and -06
8. Normative References 8. 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.lange-netmod-iana-timezones] [I-D.ietf-netmod-iana-timezones]
Lange, J., "IANA Timezone Database YANG Module", Lange, J., "IANA Timezone Database YANG Module",
draft-lange-netmod-iana-timezones-01 (work in progress), draft-ietf-netmod-iana-timezones-00 (work in progress),
June 2012. July 2012.
[I-D.ietf-netmod-rfc6021-bis]
Schoenwaelder, J., "Common YANG Data Types",
draft-ietf-netmod-rfc6021-bis-01 (work in progress),
March 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.
skipping to change at page 31, line 5 skipping to change at page 32, line 9
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.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
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.
 End of changes. 55 change blocks. 
119 lines changed or deleted 179 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/