draft-ietf-netmod-system-mgmt-09.txt   draft-ietf-netmod-system-mgmt-10.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: May 11, 2014 Tail-f Systems Expires: June 26, 2014 Tail-f Systems
November 7, 2013 December 23, 2013
YANG Data Model for System Management A YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-09 draft-ietf-netmod-system-mgmt-10
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 some common system properties within a device identification of some common system properties within a device
containing a NETCONF server. This includes data node definitions for containing a NETCONF server. This includes data node definitions for
system identification, time-of-day management, user management, DNS system identification, time-of-day management, user management, DNS
resolver configuration, and some protocol operations for system resolver configuration, and some protocol operations for system
management. management.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 May 11, 2014. This Internet-Draft will expire on June 26, 2014.
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 28 skipping to change at page 2, line 28
3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 7 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 7
3.1. System Identification . . . . . . . . . . . . . . . . . . 7 3.1. System Identification . . . . . . . . . . . . . . . . . . 7
3.2. System Time Management . . . . . . . . . . . . . . . . . . 7 3.2. System Time Management . . . . . . . . . . . . . . . . . . 7
3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 8 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 8
3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 8 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 8
3.5. User Authentication Model . . . . . . . . . . . . . . . . 9 3.5. User Authentication Model . . . . . . . . . . . . . . . . 9
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 9 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 9
3.5.2. Local User Password Authentication . . . . . . . . . . 10 3.5.2. Local User Password Authentication . . . . . . . . . . 10
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 10 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 10
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 10 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 10
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 11 4. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 5. System YANG module . . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 32 7. Security Considerations . . . . . . . . . . . . . . . . . . . 32
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.7. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.8. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 8.7. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.9. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 34 8.8. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 8.9. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.1. Normative References . . . . . . . . . . . . . . . . . . . 35 8.10. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.2. Informative References . . . . . . . . . . . . . . . . . . 36 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 9.1. Normative References . . . . . . . . . . . . . . . . . . . 37
9.2. Informative References . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for the This document defines a YANG [RFC6020] data model for the
configuration and identification of some common properties within a configuration and identification of some common properties within a
device containing a NETCONF server. device containing a NETCONF server.
Devices that are managed by NETCONF and perhaps other mechanisms have Devices that are managed by NETCONF and perhaps other mechanisms have
common properties that need to be configured and monitored in a common properties that need to be configured and monitored in a
standard way. standard way.
skipping to change at page 11, line 5 skipping to change at page 11, line 5
set-current-datetime set-current-datetime
system-restart system-restart
system-shutdown system-shutdown
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. 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 This YANG module imports YANG extensions from [RFC6536], and imports
YANG types from [RFC6991] and [I-D.ietf-netmod-iana-timezones]. It YANG types from [RFC6991] and [I-D.ietf-netmod-iana-timezones]. It
also references [RFC1035], [RFC1321], [RFC2865], [RFC3418], also references [RFC1035], [RFC1321], [RFC2865], [RFC3418],
[RFC5607], [RFC5966], [IEEE-1003.1-2008], and [FIPS.180-3.2008]. [RFC5607], [RFC5966], [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-11-07.yang" <CODE BEGINS> file "ietf-system@2013-12-23.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 12, line 38 skipping to change at page 13, line 38
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-07.txt // Note: extracted from draft-ietf-netmod-system-mgmt-07.txt
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2013-11-07" { revision "2013-12-23" {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for System Management"; "RFC XXXX: A YANG Data Model for System Management";
} }
/* /*
* Typedefs * Typedefs
*/ */
skipping to change at page 17, line 21 skipping to change at page 18, line 21
*/ */
container system { container system {
description description
"System group configuration."; "System group configuration.";
leaf contact { leaf contact {
type string; type string;
description description
"The administrator contact information for the system. "The administrator contact information for the system.
The server MAY restrict the size and characters in
order to maintain compatibility with the sysContact A server implementation MAY map this leaf to the sysContact
MIB object."; 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 reference
"RFC 3418: Management Information Base (MIB) for the "RFC 3418: Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP) Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysContact"; SNMPv2-MIB.sysContact";
} }
leaf hostname { leaf hostname {
type inet:domain-name; type inet:domain-name;
description description
"The name of the host. This name can be a single domain "The name of the host. This name can be a single domain
label, or the fully qualified domain name of the host."; label, or the fully qualified domain name of the host.";
} }
leaf location { leaf location {
type string; type string;
description description
"The system location. The server MAY restrict the size "The system location.
and characters in order to maintain compatibility with
the sysLocation MIB object."; 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 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 clock { container clock {
description description
"Configuration of the system date and time properties."; "Configuration of the system date and time properties.";
choice timezone { choice timezone {
description description
"The system timezone information."; "The system timezone information.";
case timezone-location { case timezone-location {
if-feature timezone-location; if-feature timezone-location;
skipping to change at page 29, line 5 skipping to change at page 31, line 5
description description
"Request that the entire system be shut down immediately. "Request that the entire system be shut down immediately.
A server SHOULD send an rpc reply to the client before A server SHOULD send an rpc reply to the client before
shutting down the system."; shutting down the system.";
} }
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 6. IANA Considerations
This document registers one 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 Following the format in RFC 3688, the following registration is
requested to be made. requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-system URI: urn:ietf:params:xml:ns:yang:ietf-system
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers one YANG module in the YANG Module Names This document registers one YANG module in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-system name: ietf-system
namespace: urn:ietf:params:xml:ns:yang:ietf-system namespace: urn:ietf:params:xml:ns:yang:ietf-system
prefix: sys prefix: sys
reference: RFC XXXX reference: RFC XXXX
6. Security Considerations 7. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. Authorization for access to specific transport is SSH [RFC6242]. Authorization for access to specific
portions of conceptual data and operations within this module is portions of conceptual data and operations within this module is
provided by the NETCONF access control model (NACM) [RFC6536]. provided by the NETCONF access control model (NACM) [RFC6536].
There are a number of data nodes defined in this YANG module which There are a number of data nodes defined in this YANG module which
are writable/creatable/deletable (i.e., config true, which is the are writable/creatable/deletable (i.e., config true, which is the
skipping to change at page 32, line 5 skipping to change at page 34, line 5
o set-current-datetime: Changes the current date and time on the o set-current-datetime: Changes the current date and time on the
device. device.
o system-restart: Reboots the device. o system-restart: Reboots the device.
o system-shutdown: Shuts down the device. o system-shutdown: Shuts down the device.
This YANG model defines a type "crypt-hash" that can be used to store This YANG model defines a type "crypt-hash" that can be used to store
MD5 hashes. [RFC6151] discusses security considerations for MD5. MD5 hashes. [RFC6151] discusses security considerations for MD5.
7. Change Log 8. Change Log
-- RFC Ed.: remove this section before publication. -- RFC Ed.: remove this section before publication.
7.1. 00-01 8.1. 00-01
o added configuration-source identities o added configuration-source identities
o added configuration-source leaf to ntp and dns (via grouping) to o added configuration-source leaf to ntp and dns (via grouping) to
choose configuration source choose configuration source
o added association-type, iburst, prefer, and true leafs to the ntp- o added association-type, iburst, prefer, and true leafs to the ntp-
server list server list
o extended the ssh keys for a user to a list of keys. support all o extended the ssh keys for a user to a list of keys. support all
defined key algorithms, not just dsa and rsa defined key algorithms, not just dsa and rsa
o clarified timezone-utc-offset description-stmt o clarified timezone-utc-offset description-stmt
o removed '/system/ntp/server/true' leaf from data model 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 o added default-stmts to ntp-server/iburst and ntp-server/prefer
leafs leafs
o changed timezone-location leaf to use iana-timezone typedef o changed timezone-location leaf to use iana-timezone typedef
instead of a string instead of a string
7.3. 02-03 8.3. 02-03
o removed configuration-source identities and leafs o removed configuration-source identities and leafs
7.4. 03-04 8.4. 03-04
o removed ndots dns resolver option o removed ndots dns resolver option
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 8.5. 04-05
o updated tree diagram explanation text 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/use-ntp to ntp/enabled
o changed ntp/ntp-server to ntp/server o changed ntp/ntp-server to ntp/server
o removed /system/platform/nodename leaf o removed /system/platform/nodename leaf
o changed /system/name to /system/hostname o changed /system/name to /system/hostname
o simplified must expression in user-authentication-order o simplified must expression in user-authentication-order
skipping to change at page 33, line 46 skipping to change at page 35, line 46
o changed /system/platform/nodename to /system/platform/hostname o changed /system/platform/nodename to /system/platform/hostname
o changed /system/radius/server/{leafs} to be within a choice and o changed /system/radius/server/{leafs} to be within a choice and
'udp' case statement so other transport specific parameters can 'udp' case statement so other transport specific parameters can
augment this list or they can be added by the WG to a future augment this list or they can be added by the WG to a future
version of this module. {leafs} are authentication-port and version of this module. {leafs} are authentication-port and
shared-secret. shared-secret.
o updated YANG tree diagrams for objects added in -05 and -06 o updated YANG tree diagrams for objects added in -05 and -06
7.7. 06-07 8.7. 06-07
o updated the Abstract and Introduction o updated the Abstract and Introduction
o updated Tree diagram notation o updated Tree diagram notation
o identify all external servers (dns, ntp, radius) by name instead o identify all external servers (dns, ntp, radius) by name instead
of address, in order to make the data model extensible for of address, in order to make the data model extensible for
additional transport protocol. additional transport protocol.
o updated the Security Considerations section with a reference to o updated the Security Considerations section with a reference to
NACM. NACM.
7.8. 07-08 8.8. 07-08
o renamed the DNS transport to 'udp-and-tcp' and added references. o renamed the DNS transport to 'udp-and-tcp' and added references.
o moved the operational state nodes into /system-state. 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 made "ntp" node a presence container
o added reference to RFC 6151 o added reference to RFC 6151
o updated reference from 6021-bis to RFC 6991 o updated reference from 6021-bis to RFC 6991
o cleaned up usage of config false in the YANG module 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] [FIPS.180-3.2008]
National Institute of Standards and Technology, "Secure National Institute of Standards and Technology, "Secure
Hash Standard", FIPS PUB 180-3, October 2008, <http:// Hash Standard", FIPS PUB 180-3, October 2008, <http://
csrc.nist.gov/publications/fips/fips180-3/ csrc.nist.gov/publications/fips/fips180-3/
fips180-3_final.pdf>. fips180-3_final.pdf>.
[I-D.ietf-netmod-iana-timezones] [I-D.ietf-netmod-iana-timezones]
Lange, J., "IANA Timezone Database YANG Module", Lange, J., "IANA Timezone Database YANG Module",
draft-ietf-netmod-iana-timezones-00 (work in progress), draft-ietf-netmod-iana-timezones-00 (work in progress),
skipping to change at page 36, line 27 skipping to change at page 38, line 27
[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.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
July 2013. July 2013.
8.2. Informative References 9.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC6557] Lear, E. and P. Eggert, "Procedures for Maintaining the [RFC6557] Lear, E. and P. Eggert, "Procedures for Maintaining the
Time Zone Database", BCP 175, RFC 6557, February 2012. Time Zone Database", BCP 175, RFC 6557, February 2012.
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
 End of changes. 25 change blocks. 
47 lines changed or deleted 77 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/