Network Working Group A. Bierman
Internet-Draft YumaWorks
Intended status: Standards Track M. Bjorklund
Expires: October 23, 2013 Tail-f Systems
April 21, 2013
YANG Data Model for System Management
draft-ietf-netmod-system-mgmt-06
Abstract
This document defines a YANG data model for the configuration and
identification of the management system of a device.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 October 23, 2013.
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
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Bierman & Bjorklund Expires October 23, 2013 [Page 1]
Internet-Draft YANG System Management April 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. System Identification . . . . . . . . . . . . . . . . . . 5
2.2. System Time Management . . . . . . . . . . . . . . . . . . 5
2.3. User Authentication . . . . . . . . . . . . . . . . . . . 5
3. System Data Model . . . . . . . . . . . . . . . . . . . . . . 6
3.1. System Identification . . . . . . . . . . . . . . . . . . 6
3.2. System Time Management . . . . . . . . . . . . . . . . . . 6
3.3. DNS Resolver Model . . . . . . . . . . . . . . . . . . . . 6
3.4. RADIUS Client Model . . . . . . . . . . . . . . . . . . . 7
3.5. User Authentication Model . . . . . . . . . . . . . . . . 7
3.5.1. SSH Public Key Authentication . . . . . . . . . . . . 8
3.5.2. Local User Password Authentication . . . . . . . . . . 8
3.5.3. RADIUS Password Authentication . . . . . . . . . . . . 9
3.6. System Control . . . . . . . . . . . . . . . . . . . . . . 9
4. System YANG module . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.5. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8. Normative References . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
Bierman & Bjorklund Expires October 23, 2013 [Page 2]
Internet-Draft YANG System Management April 2013
1. Introduction
This document defines a YANG [RFC6020] data model for the
configuration and identification of some common properties within the
management system of a device.
Devices that are managed by NETCONF and perhaps other mechanisms have