draft-ietf-netmod-system-mgmt-10.txt		draft-ietf-netmod-system-mgmt-11.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: June 26, 2014 Tail-f Systems		Expires: July 24, 2014 Tail-f Systems
	December 23, 2013		January 20, 2014
	A YANG Data Model for System Management		A YANG Data Model for System Management
	draft-ietf-netmod-system-mgmt-10		draft-ietf-netmod-system-mgmt-11
	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 June 26, 2014.		This Internet-Draft will expire on July 24, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 37		skipping to change at page 3, line 37
	o system control operations (shutdown, restart, setting time)		o system control operations (shutdown, restart, setting time)
	1.1. Terminology		1.1. Terminology
	The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14, [RFC2119].		14, [RFC2119].
			The following terms are defined in [RFC6241] and are not redefined
			here:
			o client
			o configuration data
			o server
			o state data
	1.2. Tree Diagrams		1.2. Tree Diagrams
	A simplified graphical representation of the data model is used in		A simplified graphical representation of the data model is used in
	this document. The meaning of the symbols in these diagrams is as		this document. The meaning of the symbols in these diagrams is as
	follows:		follows:
	o Brackets "[" and "]" enclose list keys.		o Brackets "[" and "]" enclose list keys.
	o Abbreviations before data node names: "rw" means configuration		o Abbreviations before data node names: "rw" means configuration
	(read-write) and "ro" state data (read-only).		(read-write) and "ro" state data (read-only).
	skipping to change at page 5, line 24		skipping to change at page 5, line 24
	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. It should be		Timezone database [RFC6557] also need to be supported. It should be
	possible for the server, as well as clients, to configure the system		possible to configure the system to use NTP.
	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. It should be possible for the server, as well as		or by vendors. It should be possible to configure the system
	clients, to configure the system authentication properties.		authentication properties.
	2.4. DNS Resolver		2.4. DNS Resolver
	The configuration of the DNS resolver within the system containing		The configuration of the DNS resolver within the system containing
	the NETCONF server is required to control how domain names are		the NETCONF server is required in order to control how domain names
	resolved.		are resolved.
	2.5. System Control		2.5. System Control
	A few operations are needed to support common tasks such as		A few operations are needed to support common tasks such as
	restarting the device or setting the system date and time.		restarting the device or setting the system date and time.
	3. System Data Model		3. System Data Model
	3.1. System Identification		3.1. System Identification
End of changes. 8 change blocks.
	11 lines changed or deleted		21 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/