--- 1/draft-ietf-netmod-system-mgmt-06.txt 2013-06-17 22:14:22.129562952 +0100 +++ 2/draft-ietf-netmod-system-mgmt-07.txt 2013-06-17 22:14:22.189564365 +0100 @@ -1,158 +1,159 @@ Network Working Group A. Bierman Internet-Draft YumaWorks Intended status: Standards Track M. Bjorklund -Expires: October 23, 2013 Tail-f Systems - April 21, 2013 +Expires: December 19, 2013 Tail-f Systems + June 17, 2013 YANG Data Model for System Management - draft-ietf-netmod-system-mgmt-06 + draft-ietf-netmod-system-mgmt-07 Abstract 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 This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on October 23, 2013. + This Internet-Draft will expire on December 19, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 - 1.1.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. System Identification . . . . . . . . . . . . . . . . . . 5 2.2. System Time Management . . . . . . . . . . . . . . . . . . 5 2.3. User Authentication . . . . . . . . . . . . . . . . . . . 5 - 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 6 - 3.1. System Identification . . . . . . . . . . . . . . . . . . 6 - 3.2. System Time Management . . . . . . . . . . . . . . . . . . 6 - 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6 - 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7 - 3.5. User Authentication Model . . . . . . . . . . . . . . . . 7 - 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8 - 3.5.2. Local User Password Authentication . . . . . . . . . . 8 - 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 9 - 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9 - 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 - 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 - 8. Normative References . . . . . . . . . . . . . . . . . . . . . 31 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 + 2.4. DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . 5 + 2.5. System Control . . . . . . . . . . . . . . . . . . . . . . 6 + 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 7 + 3.1. System Identification . . . . . . . . . . . . . . . . . . 7 + 3.2. System Time Management . . . . . . . . . . . . . . . . . . 7 + 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 7 + 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 8 + 3.5. User Authentication Model . . . . . . . . . . . . . . . . 8 + 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 9 + 3.5.2. Local User Password Authentication . . . . . . . . . . 9 + 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 10 + 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 10 + 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 11 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 + 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 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 This document defines a YANG [RFC6020] data model for the - configuration and identification of some common properties within the - management system of a device. + configuration and identification of some common properties within a + device containing a NETCONF server. Devices that are managed by NETCONF and perhaps other mechanisms have common properties that need to be configured and monitored in a standard way. The "ietf-system" YANG module defined in this document provides the following features: - o system administrative data configuration - - o system identification monitoring + o system identification configuration and monitoring o system time-of-day configuration and monitoring o user authentication configuration o local users configuration + o DNS resolver configuration + + o system control operations (shutdown, restart, setting time) + 1.1. Terminology The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 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 A simplified graphical representation of the data model is used in this document. The meaning of the symbols in these diagrams is as follows: o Brackets "[" and "]" enclose list keys. o Abbreviations before data node names: "rw" means configuration (read-write) and "ro" state data (read-only). 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 marked with a colon (":"). o Ellipsis ("...") stands for contents of subtrees that are not shown. 2. Objectives 2.1. System Identification There are many common properties used to identify devices, operating systems, software versions, etc. that need to be supported in the - system data module. These objects are defined as operational data - and the information returned by the server is intended to be specific - to the device vendor. + system data module. These objects are defined as operational state + data 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 as the system location and description. 2.2. System Time Management 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 system date and time need to be possible. Utilization of the Timezone database [RFC6557] also need to be supported. It should be @@ -170,20 +171,32 @@ Since the mandatory transport protocol for NETCONF is SSH [RFC6242] the authentication model need to support SSH's "publickey" and "password" authentication methods [RFC4252]. The model for authentication configuration should be flexible enough to support authentication methods defined by other standard documents or by vendors. It should be possible for the server, as well as 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.1. System Identification The data model for system identification has the following structure: +--rw system +--rw contact? string +--rw hostname? inet:domain-name +--rw location? string @@ -197,57 +210,68 @@ The data model for system time management has the following structure: +--rw system +--rw clock | +--ro current-datetime? yang:date-and-time | +--ro boot-datetime? yang:date-and-time | +--rw (timezone)? | +--:(timezone-location) - | | +--rw timezone-location? string + | | +--rw timezone-location? ianatz:iana-timezone | +--:(timezone-utc-offset) | +--rw timezone-utc-offset? int16 +--rw ntp +--rw enabled? boolean - +--rw server [address] + +--rw server* [name] + +--rw name string + +--rw (transport) + | +--:(udp) + | +--rw udp + | +--rw address inet:host + | +--rw port? inet:port-number +--rw association-type? enumeration - +--rw address inet:host - +--rw enabled? boolean +--rw iburst? boolean +--rw prefer? boolean 3.3. DNS Resolver Model The data model for configuration of the DNS resolver has the following structure: +--rw system - +--rw dns + +--rw dns-resolver +--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 timeout? uint8 +--rw attempts? uint8 3.4. RADIUS Client Model The data model for configuration of the RADIUS client has the following structure: +--rw system +--rw radius - +--rw server [address] - | +--rw address inet:host + +--rw server* [name] + | +--rw name string | +--rw (transport) | | +--:(udp) | | +--rw udp + | | +--rw address inet:host | | +--rw authentication-port? inet:port-number | | +--rw shared-secret string | +--rw authentication-type? identityref +--rw options +--rw timeout? uint8 +--rw attempts? uint8 3.5. User Authentication Model This document defines three authentication methods for use with @@ -270,27 +294,27 @@ The authentication parameters defined in this document are primarily used to configure authentication of NETCONF users, but MAY also be used by other interfaces, e.g., a Command Line Interface or a Web- based User Interface. The data model for user authentication has the following structure: +--rw system +--rw authentication +--rw user-authentication-order* identityref - +--rw user [name] + +--rw user* [name] +--rw name string +--rw password? crypt-hash - +--rw ssh-key [name] + +--rw ssh-key* [name] +--rw name string - +--rw algorithm? string - +--rw key-data? binary + +--rw algorithm string + +--rw key-data binary 3.5.1. SSH Public Key Authentication If the NETCONF server advertises the "local-users" feature, configuration of local users and their SSH public keys is supported in the /system/authentication/user list. Public key authentication is requested by the SSH client. If the "local-users" feature is supported, then when a NETCONF client starts an SSH session towards the server using the "publickey" @@ -339,21 +363,21 @@ This YANG module imports YANG extensions from [RFC6536], and imports YANG types from [I-D.ietf-netmod-rfc6021-bis] and [I-D.ietf-netmod-iana-timezones]. It also references [RFC1321], [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 remove this note. - file "ietf-system@2013-04-21.yang" + file "ietf-system@2013-06-17.yang" module ietf-system { namespace "urn:ietf:params:xml:ns:yang:ietf-system"; prefix "sys"; import ietf-yang-types { prefix yang; } import ietf-inet-types { @@ -382,45 +406,49 @@ Editor: Andy Bierman Editor: Martin Bjorklund "; description "This module contains a collection of YANG definitions for the - configuration and identification of the management system of a - device. + configuration and 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. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and 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 // and remove this note. - revision "2013-04-21" { + revision "2013-06-17" { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for System Management"; } /* * Typedefs */ @@ -452,21 +481,21 @@ If a value starting with '$$', where is not '0', is received, the server knows that the value already represents a hashed value, and stores it as is in the data store. When a server needs to verify a password given by a user, it finds the stored password hash string for that user, extracts the salt, and calculates the hash with the salt and given password as input. If the calculated hash value is the same as the stored value, the password given by the client is - correct. + accepted. This type defines the following hash functions: id | hash function | feature ---+---------------+------------------- 1 | MD5 | crypt-hash-md5 5 | SHA-256 | crypt-hash-sha-256 6 | SHA-512 | crypt-hash-sha-512 The server indicates support for the different hash functions @@ -486,37 +516,37 @@ description "Indicates that the device can be configured as a RADIUS client."; reference "RFC 2865: Remote Authentication Dial In User Service " + "(RADIUS)"; } feature authentication { description - "Indicates that the device can be configured - to do authentication of users."; + "Indicates that the device supports configuration + for user authentication."; } feature local-users { if-feature authentication; description - "Indicates that the device supports + "Indicates that the device supports configuration of local user authentication."; } feature radius-authentication { if-feature radius; if-feature authentication; description - "Indicates that the device supports user authentication over - RADIUS."; + "Indicates that the device supports configuration of user + authentication over RADIUS."; reference "RFC 2865: Remote Authentication Dial In User Service (RADIUS) RFC 5607: Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management"; } feature crypt-hash-md5 { description "Indicates that the device supports the MD5 @@ -539,31 +567,50 @@ reference "FIPS.180-3.2008: Secure Hash Standard"; } feature ntp { description "Indicates that the device can be configured to use one or more NTP servers to set the 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 { description "Indicates that the local timezone on the device can be configured to use the TZ database to set the timezone and manage daylight savings time."; reference "TZ Database http://www.twinsun.com/tz/tz-link.htm Maintaining the Timezone Database 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 */ identity authentication-method { description "Base identity for user authentication methods."; } identity radius { @@ -608,51 +657,48 @@ /* * Top-level container */ container system { description "System group configuration."; leaf contact { - type string { - length "0..255"; - } + type string; 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 "RFC 3418 - Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) SNMPv2-MIB.sysContact"; - } - leaf hostname { type inet:domain-name; description "The name of the host. This name can be a single domain label, or the fully qualified domain name of the host."; } - leaf location { - type string { - length "0..255"; - } + type string; 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 "RFC 3418 - Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) SNMPv2-MIB.sysLocation"; } - container platform { config false; description "Contains vendor-specific information for identifying the system platform and operating system."; reference "IEEE Std 1003.1-2008 - sys/utsname.h"; leaf os-name { type string; @@ -698,60 +740,58 @@ description "Configuration and monitoring of the system date and time properties."; leaf current-datetime { type yang:date-and-time; config false; description "The current system date and time."; } - leaf boot-datetime { type yang:date-and-time; config false; description - "The system date and time when the NETCONF - server last restarted."; + "The system date and time when the system last restarted."; } - choice timezone { description "The system timezone information."; - leaf timezone-location { + case timezone-location { if-feature timezone-location; + leaf timezone-location { type ianatz:iana-timezone; description "The TZ database location identifier string to use for the system, such as 'Europe/Stockholm'."; } - + } + case timezone-utc-offset { leaf timezone-utc-offset { type int16 { 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."; + 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 { if-feature ntp; - description "Configuration of the NTP client."; leaf enabled { type boolean; default true; description "Indicates that the system should attempt to synchronize the system clock with an NTP server from the 'ntp/server' list."; @@ -749,29 +789,62 @@ "Configuration of the NTP client."; leaf enabled { type boolean; default true; description "Indicates that the system should attempt to synchronize the system clock with an NTP server from the 'ntp/server' list."; } - list server { - key address; + key name; description "List of NTP servers to use for system clock synchronization. If '/system/ntp/enabled' is 'true', then the system will attempt to 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 { type enumeration { enum server { description "Use client association mode. This device will not provide synchronization to the configured NTP server."; } enum peer { description @@ -785,129 +858,178 @@ more of the NTP servers found by DNS resolution of the domain name given by the 'address' leaf. This device will not provide synchronization to the servers."; } } default server; description "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 { type boolean; default false; description "Indicates whether this server should enable burst synchronization or not."; } leaf prefer { type boolean; default false; description "Indicates whether this server should be preferred or not."; } } } - container dns { + container dns-resolver { description "Configuration of the DNS resolver."; leaf-list search { type inet:domain-name; ordered-by user; description "An ordered list of domains to search when resolving a host name."; + } - leaf-list server { - type inet:ip-address; + list server { + key name; ordered-by user; description - "Addresses of the name servers that the resolver should - query. + "List of the DNS servers that the resolver should 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 - 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 { description "Resolver options. The set of available options has been limited to those that are generally available across different resolver implementations, and generally useful."; leaf timeout { type uint8 { range "1..max"; } units "seconds"; default "5"; description "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."; } leaf attempts { type uint8 { range "1..max"; } default "2"; description "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."; } } } container radius { if-feature radius; description "Configuration of the RADIUS client."; list server { - key address; + key name; ordered-by user; description - "List of RADIUS servers used by the device."; + "List of RADIUS servers used by the device. - leaf address { - type inet:host; + When the RADIUS client is invoked by a calling + 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 - "The address of the RADIUS server."; + "An arbitrary name for the RADIUS 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 RADIUS."; + leaf address { + type inet:host; + mandatory true; + description + "The address of the RADIUS server."; + } 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; @@ -936,31 +1058,31 @@ "RADIUS client options."; leaf timeout { type uint8 { range "1..max"; } units "seconds"; default "5"; description "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."; } leaf attempts { type uint8 { range "1..max"; } default "2"; description "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 { nacm:default-deny-write; if-feature authentication; description "The authentication configuration subtree."; @@ -1019,32 +1141,34 @@ "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; leaf name { type string; description "An arbitrary name for the ssh key."; } leaf algorithm { type string; + mandatory true; description "The public key algorithm name for this ssh key. Valid values are the values in the IANA Secure Shell (SSH) Protocol Parameters registry, Public Key Algorithm Names"; reference "IANA Secure Shell (SSH) Protocol Parameters registry, Public Key Algorithm Names"; } leaf key-data { type binary; + mandatory true; description "The binary key data for this ssh key."; } } } } } rpc set-current-datetime { nacm:default-deny-all; @@ -1103,38 +1226,40 @@ name: ietf-system namespace: urn:ietf:params:xml:ns:yang:ietf-system prefix: sys reference: RFC XXXX 6. Security Considerations The YANG module defined in this memo is designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 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 are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: o /system/clock/timezone: This choice contains the objects used to control the timezone used by the device. o /system/ntp: This container contains the objects used to control the Network Time Protocol servers used by the device. - o /system/dns: This container contains the objects used to control - the Domain Name System servers used by the device. + o /system/dns-resolver: This container contains the objects used to + control the Domain Name System servers used by the device. o /system/radius: This container contains the objects used to control the Remote Authentication Dial-In User Service servers used by the device. o /system/authentication/user-authentication-order: This leaf controls how user login attempts are authenticated by the device. o /system/authentication/user: This list contains the local users enabled on the system. @@ -1142,20 +1267,24 @@ Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability: o /system/platform: This container has objects which may help identify the specific NETCONF server and/or operating system 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 sensitive or vulnerable in some network environments. It is thus important to control access to these operations. These are the operations and their sensitivity/vulnerability: o set-current-datetime: Changes the current date and time on the device. o system-restart: Reboots the device. @@ -1242,59 +1371,70 @@ 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 +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] National Institute of Standards and Technology, "Secure Hash Standard", FIPS PUB 180-3, October 2008, . [I-D.ietf-netmod-iana-timezones] Lange, J., "IANA Timezone Database YANG Module", draft-ietf-netmod-iana-timezones-00 (work in progress), 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. + draft-ietf-netmod-rfc6021-bis-02 (work in progress), + May 2013. [IEEE-1003.1-2008] Institute of Electrical and Electronics Engineers, "POSIX.1-2008", IEEE Standard 1003.1, March 2008. [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April 1992. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, 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) Authentication Protocol", RFC 4252, January 2006. [RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) Transport Layer Protocol", RFC 4253, January 2006. [RFC5607] Nelson, D. and G. Weber, "Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management", RFC 5607, July 2009. @@ -1306,20 +1446,25 @@ and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, 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 Time Zone Database", BCP 175, RFC 6557, February 2012. Authors' Addresses Andy Bierman YumaWorks Email: andy@yumaworks.com