draft-ietf-netmod-system-mgmt-04.txt   draft-ietf-netmod-system-mgmt-05.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 29, 2013 Tail-f Systems Expires: August 29, 2013 Tail-f Systems
December 26, 2012 February 25, 2013
YANG Data Model for System Management YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-04 draft-ietf-netmod-system-mgmt-05
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 June 29, 2013. This Internet-Draft will expire on August 29, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2.1. System Identification . . . . . . . . . . . . . . . . . . 4 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. System Time Management . . . . . . . . . . . . . . . . . . 4 2.1. System Identification . . . . . . . . . . . . . . . . . . 5
2.3. User Authentication . . . . . . . . . . . . . . . . . . . 4 2.2. System Time Management . . . . . . . . . . . . . . . . . . 5
3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 5 2.3. User Authentication . . . . . . . . . . . . . . . . . . . 5
3.1. System Identification . . . . . . . . . . . . . . . . . . 5 3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 6
3.2. System Time Management . . . . . . . . . . . . . . . . . . 5 3.1. System Identification . . . . . . . . . . . . . . . . . . 6
3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 5 3.2. System Time Management . . . . . . . . . . . . . . . . . . 6
3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 6 3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6
3.5. User Authentication Model . . . . . . . . . . . . . . . . 6 3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 7 3.5. User Authentication Model . . . . . . . . . . . . . . . . 7
3.5.2. Local User Password Authentication . . . . . . . . . . 7 3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 7 3.5.2. Local User Password Authentication . . . . . . . . . . 8
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 8 3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 8
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 9 3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8. Normative References . . . . . . . . . . . . . . . . . . . . . 29 7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8. Normative References . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
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
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 4, line 5 skipping to change at page 3, line 44
1.1.1. Terms 1.1.1. Terms
The following terms are used within this document: The following terms are used within this document:
o system: This term refers to the embodiment of the entire set of o system: This term refers to the embodiment of the entire set of
management interfaces that a single NETCONF server is supporting management interfaces that a single NETCONF server is supporting
at a given moment. The set of physical entities managed by a at a given moment. The set of physical entities managed by a
single NETCONF server can be static or it can change dynamically. single NETCONF server can be static or it can change dynamically.
1.2. Tree Diagrams
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as
follows:
o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration
(read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node and "*"
denotes a "leaf-list".
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
2. Objectives 2. Objectives
2.1. System Identification 2.1. System Identification
There are many common properties used to identify devices, operating There are many common properties used to identify devices, operating
systems, software versions, etc. that need to be supported in the systems, software versions, etc. that need to be supported in the
system data module. These objects are defined as operational data system data module. These objects are defined as operational data
and intended to be specific to the device vendor. and intended to be specific to the device vendor.
Some user-configurable administrative strings are also provided such Some user-configurable administrative strings are also provided such
skipping to change at page 9, line 15 skipping to change at page 10, line 15
4. System YANG module 4. 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 [RFC6021] and [I-D.lange-netmod-iana-timezones]. It YANG types from [RFC6021] and [I-D.lange-netmod-iana-timezones]. It
also references [RFC1321], [RFC2865], [RFC3418], [RFC5607], also references [RFC1321], [RFC2865], [RFC3418], [RFC5607],
[IEEE-1003.1-2008], and [FIPS.180-3.2008]. [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-12-26.yang" <CODE BEGINS> file "ietf-system@2013-02-25.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 10, line 30 skipping to change at page 11, 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-04.txt // Note: extracted from draft-ietf-netmod-system-mgmt-05.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-12-26" { revision "2013-02-25" {
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 29, line 5 skipping to change at page 29, line 48
7.4. 03-04 7.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
o updated tree diagram explanation text
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] [I-D.lange-netmod-iana-timezones]
Lange, J., "IANA Timezone Database YANG Module", Lange, J., "IANA Timezone Database YANG Module",
 End of changes. 10 change blocks. 
32 lines changed or deleted 58 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/