--- 1/draft-ietf-netmod-system-mgmt-09.txt 2013-12-23 02:14:32.462117798 -0800 +++ 2/draft-ietf-netmod-system-mgmt-10.txt 2013-12-23 02:14:32.522119285 -0800 @@ -1,19 +1,19 @@ Network Working Group A. Bierman Internet-Draft YumaWorks Intended status: Standards Track M. Bjorklund -Expires: May 11, 2014 Tail-f Systems - November 7, 2013 +Expires: June 26, 2014 Tail-f Systems + December 23, 2013 - YANG Data Model for System Management - draft-ietf-netmod-system-mgmt-09 + A YANG Data Model for System Management + draft-ietf-netmod-system-mgmt-10 Abstract This document defines a YANG data model for the 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. @@ -25,21 +25,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 May 11, 2014. + This Internet-Draft will expire on June 26, 2014. 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 @@ -63,37 +63,39 @@ 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 7 3.1. System Identification . . . . . . . . . . . . . . . . . . 7 3.2. System Time Management . . . . . . . . . . . . . . . . . . 7 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 8 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 8 3.5. User Authentication Model . . . . . . . . . . . . . . . . 9 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 9 3.5.2. Local User Password Authentication . . . . . . . . . . 10 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 - 7.8. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 - 7.9. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 - 8.1. Normative References . . . . . . . . . . . . . . . . . . . 35 - 8.2. Informative References . . . . . . . . . . . . . . . . . . 36 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 + 4. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . . . 11 + 5. System YANG module . . . . . . . . . . . . . . . . . . . . . . 12 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 32 + 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 + 8.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 35 + 8.7. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 35 + 8.8. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 36 + 8.9. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 36 + 8.10. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 36 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 9.1. Normative References . . . . . . . . . . . . . . . . . . . 37 + 9.2. Informative References . . . . . . . . . . . . . . . . . . 38 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 1. Introduction This document defines a YANG [RFC6020] data model for the 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. @@ -371,31 +373,49 @@ set-current-datetime system-restart system-shutdown Two protocol operations are included to restart or shutdown the system. The 'system-restart' operation can be used to restart the entire system (not just the NETCONF server). The 'system-shutdown' operation can be used to power off the entire system. -4. System YANG module +4. Relationship to the SNMPv2-MIB + + If a device implements the SNMPv2-MIB [RFC3418], there are two + objects that MAY be mapped by the implementation. See the YANG + module definition in Section 5 for details. The following table + lists the YANG data nodes with corresponding objects in the SNMPv2- + MIB. + + +----------------+-------------------+ + | YANG data node | SNMPv2-MIB object | + +----------------+-------------------+ + | contact | sysContact | + | location | sysLocation | + +----------------+-------------------+ + + YANG interface configuration data nodes and related SNMPv2-MIB + objects + +5. System YANG module This YANG module imports YANG extensions from [RFC6536], and imports YANG types from [RFC6991] and [I-D.ietf-netmod-iana-timezones]. It also references [RFC1035], [RFC1321], [RFC2865], [RFC3418], [RFC5607], [RFC5966], [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-11-07.yang" + file "ietf-system@2013-12-23.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 { @@ -452,21 +472,21 @@ 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-07.txt // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision "2013-11-07" { + revision "2013-12-23" { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for System Management"; } /* * Typedefs */ @@ -678,46 +698,52 @@ */ container system { description "System group configuration."; leaf contact { type string; description "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."; + + A server implementation MAY map this leaf to the sysContact + MIB object. Such an implementation needs to use some + mechanism to handle the differences in size and characters + allowed between this leaf and sysContact. The definition of + such a mechanism is outside the scope of this document."; 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; description - "The system location. The server MAY restrict the size - and characters in order to maintain compatibility with - the sysLocation MIB object."; + "The system location. + + A server implementation MAY map this leaf to the sysLocation + MIB object. Such an implementation needs to use some + mechanism to handle the differences in size and characters + allowed between this leaf and sysLocation. The definition + of such a mechanism is outside the scope of this document."; reference "RFC 3418: Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) SNMPv2-MIB.sysLocation"; } - container clock { description "Configuration of the system date and time properties."; choice timezone { description "The system timezone information."; case timezone-location { if-feature timezone-location; @@ -1238,39 +1265,39 @@ description "Request that the entire system be shut down immediately. A server SHOULD send an rpc reply to the client before shutting down the system."; } } -5. IANA Considerations +6. IANA Considerations 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 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 +7. 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]. 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 @@ -1321,68 +1348,68 @@ o set-current-datetime: Changes the current date and time on the device. o system-restart: Reboots the device. o system-shutdown: Shuts down the device. This YANG model defines a type "crypt-hash" that can be used to store MD5 hashes. [RFC6151] discusses security considerations for MD5. -7. Change Log +8. Change Log -- RFC Ed.: remove this section before publication. -7.1. 00-01 +8.1. 00-01 o added configuration-source identities o added configuration-source leaf to ntp and dns (via grouping) to choose configuration source o added association-type, iburst, prefer, and true leafs to the ntp- server list o extended the ssh keys for a user to a list of keys. support all defined key algorithms, not just dsa and rsa o clarified timezone-utc-offset description-stmt o removed '/system/ntp/server/true' leaf from data model -7.2. 01-02 +8.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 +8.3. 02-03 o removed configuration-source identities and leafs -7.4. 03-04 +8.4. 03-04 o removed ndots dns resolver option o added radius-authentication-type identity, and identities for pap and chap, and a leaf to control which authentication type to use when communicating with the radius server o made 0 an invalid value for timeouts and attempts -7.5. 04-05 +8.5. 04-05 o updated tree diagram explanation text -7.6. 05-06 +8.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 @@ -1409,51 +1436,55 @@ 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 -7.7. 06-07 +8.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. -7.8. 07-08 +8.8. 07-08 o renamed the DNS transport to 'udp-and-tcp' and added references. o moved the operational state nodes into /system-state. -7.9. 08-09 +8.9. 08-09 o made "ntp" node a presence container o added reference to RFC 6151 o updated reference from 6021-bis to RFC 6991 o cleaned up usage of config false in the YANG module -8. References +8.10. 09-10 -8.1. Normative References + o clarified relationship with SNMPv2-MIB + +9. References + +9.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), @@ -1508,21 +1539,21 @@ [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. [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. -8.2. Informative References +9.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