--- 1/draft-ietf-netmod-system-mgmt-02.txt 2012-09-08 00:14:14.749475101 +0200 +++ 2/draft-ietf-netmod-system-mgmt-03.txt 2012-09-08 00:14:14.789426303 +0200 @@ -1,19 +1,19 @@ Network Working Group A. Bierman Internet-Draft YumaWorks Intended status: Standards Track M. Bjorklund -Expires: January 12, 2013 Tail-f Systems - July 11, 2012 +Expires: March 11, 2013 Tail-f Systems + September 7, 2012 YANG Data Model for System Management - draft-ietf-netmod-system-mgmt-02 + draft-ietf-netmod-system-mgmt-03 Abstract This document defines a YANG data model for the configuration and identification of the management system of a device. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -21,21 +21,21 @@ 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 January 12, 2013. + This Internet-Draft will expire on March 11, 2013. Copyright Notice Copyright (c) 2012 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 @@ -58,40 +58,41 @@ 3.1. System Identification . . . . . . . . . . . . . . . . . . 5 3.2. System Time Management . . . . . . . . . . . . . . . . . . 5 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 5 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 6 3.5. User Authentication Model . . . . . . . . . . . . . . . . 6 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 7 3.5.2. Local User Password Authentication . . . . . . . . . . 7 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 7 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 8 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 9 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 - 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 28 - 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 - 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 - 8. Normative References . . . . . . . . . . . . . . . . . . . . . 29 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 25 + 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 8. Normative References . . . . . . . . . . . . . . . . . . . . . 28 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 1. Introduction This document defines a YANG [RFC6020] data model for the configuration and identification of the management system of a device. 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 YANG module defined in this document provides the following - features: + The "ietf-system" YANG module defined in this document provides the + following features: o system administrative data configuration o system identification monitoring o system time-of-day configuration and monitoring o user authentication configuration o local users configuration @@ -174,36 +175,34 @@ +--rw clock | +--ro current-datetime? yang:date-and-time | +--ro boot-datetime? yang:date-and-time | +--rw (timezone)? | +--:(timezone-location) | | +--rw timezone-location? string | +--:(timezone-utc-offset) | +--rw timezone-utc-offset? int16 +--rw ntp +--rw use-ntp? boolean - +--rw configuration-source* identityref +--rw ntp-server [address] +--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 configuration-source* identityref +--rw search* inet:host +--rw server* inet:ip-address +--rw options +--rw ndots? uint8 +--rw timeout? uint8 +--rw attempts? uint8 3.4. RADIUS Client Model The data model for configuration of the RADIUS client has the @@ -309,21 +308,21 @@ 4. System YANG module This YANG module imports YANG extensions from [RFC6536], and imports YANG types from [RFC6021] and [I-D.lange-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@2012-07-11.yang" + file "ietf-system@2012-09-07.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 { @@ -372,25 +371,25 @@ 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-02.txt + // Note: extracted from draft-ietf-netmod-system-mgmt-03.txt // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision "2012-07-11" { + revision "2012-09-07" { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for System Management"; } /* * Typedefs */ @@ -549,34 +548,20 @@ } identity local-users { base authentication-method; description "Indicates password-based authentication of locally configured users."; } - identity configuration-source { - description "Base for all configuration sources."; - } - - identity local-config { - base configuration-source; - description "Local configuration source."; - } - - identity dhcp { - base configuration-source; - description "DHCP configuration source."; - } - /* * Top-level container */ container system { description "System group configuration."; leaf contact { type string { @@ -681,76 +668,65 @@ "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."; } + choice timezone { description - "Configure the system timezone information."; + "The system timezone information."; leaf timezone-location { if-feature timezone-location; type ianatz:iana-timezone; description "The TZ database location identifier string to use for the system, such as 'Europe/Stockholm'."; } leaf timezone-utc-offset { type int16 { - range "-1439 .. 1439"; + 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."; } } } - grouping configuration-source { - leaf-list configuration-source { - ordered-by user; - type identityref { - base configuration-source; - } - description - "Indicates the ordered list of configuration source(s) - that the server should use for the service."; - } - } - container ntp { if-feature ntp; description "Configuration of the NTP client."; leaf use-ntp { 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."; } - uses configuration-source; - list ntp-server { key address; description "List of NTP servers to use for system clock synchronization. If 'use-ntp' is 'true', then the system will attempt to contact and utilize the specified NTP servers."; leaf association-type { type enumeration { @@ -766,23 +742,23 @@ may be expected to synchronize with the configured NTP server."; } enum pool { description "Use pool association mode. This device is not expected to synchronize with the configured NTP server."; } } + default server; description "The desired association type for this NTP server."; - default server; } leaf address { type inet:host; description "The IP address or domain name of the NTP server."; } leaf enabled { type boolean; default true; description @@ -803,22 +779,20 @@ "Indicates whether this server should be preferred or not."; } } } container dns { description "Configuration of the DNS resolver."; - uses configuration-source; - leaf-list search { type inet:host; ordered-by user; description "An ordered list of domains to search when resolving a host name."; } leaf-list server { type inet:ip-address; ordered-by user; @@ -1001,21 +974,21 @@ "The binary key data for this ssh key."; } } } } } rpc set-current-datetime { nacm:default-deny-all; description - "Manually set the /system/clock/current-datetime leaf + "Set the /system/clock/current-datetime leaf to the specified value. If the system is using NTP (e.g., /system/ntp/use-ntp is set to 'true'), then this operation will fail with error-tag 'operation-failed', and error-app-tag value of 'ntp-active'"; input { leaf current-datetime { type yang:date-and-time; mandatory true; @@ -1039,31 +1013,29 @@ A server SHOULD send an rpc reply to the client before shutting down the system."; } } 5. IANA Considerations - This document registers a URI in the IETF XML registry [RFC3688]. + This document registers one URI in the IETF XML registry [RFC3688]. Following the format in RFC 3688, the following registration is requested to be made. URI: urn:ietf:params:xml:ns:yang:ietf-system - Registrant Contact: The NETMOD WG of the IETF. - XML: N/A, the requested URI is an XML namespace. - This document registers a YANG module in the YANG Module Names + This document registers one YANG module in the YANG Module Names registry [RFC6020]. 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 @@ -1142,20 +1114,24 @@ o removed '/system/ntp/server/true' leaf from data model 7.2. 01-02 o added default-stmts to ntp-server/iburst and ntp-server/prefer leafs o changed timezone-location leaf to use iana-timezone typedef instead of a string +7.3. 02-03 + + o removed configuration-source identities and leafs + 8. Normative References [FIPS.180-3.2008] National Institute of Standards and Technology, "Secure Hash Standard", FIPS PUB 180-3, October 2008, . [I-D.lange-netmod-iana-timezones] Lange, J., "IANA Timezone Database YANG Modul",