draft-ietf-netmod-system-mgmt-01.txt   draft-ietf-netmod-system-mgmt-02.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: January 1, 2013 Tail-f Systems Expires: January 12, 2013 Tail-f Systems
June 30, 2012 July 11, 2012
YANG Data Model for System Management YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-01 draft-ietf-netmod-system-mgmt-02
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 the management system of a device. identification of the management system of a device.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 January 1, 2013. This Internet-Draft will expire on January 12, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 29 skipping to change at page 2, line 29
3.5. User Authentication Model . . . . . . . . . . . . . . . . 6 3.5. User Authentication Model . . . . . . . . . . . . . . . . 6
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 7 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 7
3.5.2. Local User Password Authentication . . . . . . . . . . 7 3.5.2. Local User Password Authentication . . . . . . . . . . 7
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 7 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 7
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 8 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 8
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 9 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8. Normative References . . . . . . . . . . . . . . . . . . . . . 29 8. Normative References . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
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 the management system of a configuration and identification of the management system of a
device. device.
Devices that are managed by NETCONF and perhaps other mechanisms have Devices that are managed by NETCONF and perhaps other mechanisms have
skipping to change at page 5, line 42 skipping to change at page 5, line 42
| +--:(timezone-location) | +--:(timezone-location)
| | +--rw timezone-location? string | | +--rw timezone-location? string
| +--:(timezone-utc-offset) | +--:(timezone-utc-offset)
| +--rw timezone-utc-offset? int16 | +--rw timezone-utc-offset? int16
+--rw ntp +--rw ntp
+--rw use-ntp? boolean +--rw use-ntp? boolean
+--rw configuration-source* identityref +--rw configuration-source* identityref
+--rw ntp-server [address] +--rw ntp-server [address]
+--rw association-type? enumeration +--rw association-type? enumeration
+--rw address inet:host +--rw address inet:host
+--rw enabled boolean +--rw enabled? boolean
+--rw iburst boolean +--rw iburst? boolean
+--rw prefer boolean +--rw prefer? boolean
3.3. DNS Resolver Model 3.3. DNS Resolver Model
The data model for configuration of the DNS resolver has the The data model for configuration of the DNS resolver has the
following structure: following structure:
+--rw system +--rw system
+--rw dns +--rw dns
+--rw configuration-source* identityref +--rw configuration-source* identityref
+--rw search* inet:host +--rw search* inet:host
skipping to change at page 9, line 7 skipping to change at page 9, line 7
3.6. System Control 3.6. System Control
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. System YANG module
This YANG module imports YANG extensions from [RFC6536], imports YANG This YANG module imports YANG extensions from [RFC6536], and imports
types from [RFC6021], and references [RFC1321], [RFC2865], [RFC3418], YANG types from [RFC6021] and [I-D.lange-netmod-iana-timezones]. It
[RFC5607], [IEEE-1003.1-2008], and [FIPS.180-3.2008]. 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 RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-system@2012-06-30.yang" <CODE BEGINS> file "ietf-system@2012-07-11.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 {
prefix inet; prefix inet;
} }
import ietf-netconf-acm { import ietf-netconf-acm {
prefix nacm; prefix nacm;
} }
import iana-timezones {
prefix ianatz;
}
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: David Kessens WG Chair: David Kessens
<mailto:david.kessens@nsn.com> <mailto:david.kessens@nsn.com>
skipping to change at page 10, line 24 skipping to change at page 10, line 30
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
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-01.txt // Note: extracted from draft-ietf-netmod-system-mgmt-02.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 "2012-06-30" { revision "2012-07-11" {
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 16, line 48 skipping to change at page 17, line 4
"The current system date and time."; "The current system date and time.";
} }
leaf boot-datetime { leaf boot-datetime {
type yang:date-and-time; type yang:date-and-time;
config false; config false;
description description
"The system date and time when the NETCONF "The system date and time when the NETCONF
server last restarted."; server last restarted.";
} }
choice timezone { choice timezone {
description description
"Configure the system timezone information."; "Configure the system timezone information.";
leaf timezone-location { leaf timezone-location {
if-feature timezone-location; if-feature timezone-location;
type string; type ianatz:iana-timezone;
description description
"The TZ database location identifier string "The TZ database location identifier string
to use for the system, such as 'Europe/Stockholm'. to use for the system, such as 'Europe/Stockholm'.";
[FIXME: replace string with enumeration]";
} }
leaf timezone-utc-offset { leaf timezone-utc-offset {
type int16 { type int16 {
range "-1439 .. 1439"; range "-1439 .. 1439";
} }
description description
"The number of minutes to add to UTC time to "The number of minutes to add to UTC time to
identify the timezone for this system. identify the timezone for this system.
For example, 'UTC - 8:00 hours' would be For example, 'UTC - 8:00 hours' would be
skipping to change at page 19, line 8 skipping to change at page 19, line 11
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default true;
description description
"Indicates whether this server is enabled for use or "Indicates whether this server is enabled for use or
not."; not.";
} }
leaf iburst { leaf iburst {
type boolean; type boolean;
default false;
description description
"Indicates whether this server should enable burst "Indicates whether this server should enable burst
synchronization or not."; synchronization or not.";
} }
leaf prefer { leaf prefer {
type boolean; type boolean;
default false;
description description
"Indicates whether this server should be preferred "Indicates whether this server should be preferred
or not."; or not.";
} }
} }
} }
container dns { container dns {
description description
"Configuration of the DNS resolver."; "Configuration of the DNS resolver.";
skipping to change at page 29, line 5 skipping to change at page 28, line 26
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
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
8. Normative References 8. 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.lange-netmod-iana-timezones]
Lange, J., "IANA Timezone Database YANG Modul",
draft-lange-netmod-iana-timezones-01 (work in progress),
June 2012.
[IEEE-1003.1-2008] [IEEE-1003.1-2008]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
"POSIX.1-2008", IEEE Standard 1003.1, March 2008. "POSIX.1-2008", IEEE Standard 1003.1, March 2008.
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
 End of changes. 17 change blocks. 
17 lines changed or deleted 36 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/