1 module ietf-netconf-monitoring {
3 namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring";
6 import ietf-yang-types { prefix yang; }
7 import ietf-inet-types { prefix inet; }
10 "IETF NETCONF (Network Configuration) Working Group";
13 "WG Web: <http://tools.ietf.org/wg/netconf/>
14 WG List: <mailto:netconf@ietf.org>
16 WG Chair: Mehmet Ersue
17 <mailto:mehmet.ersue@nsn.com>
20 <mailto:bertietf@bwijnen.net>
23 <mailto:mark.scott@ericsson.com>
25 Editor: Martin Bjorklund
26 <mailto:mbj@tail-f.com>";
29 "NETCONF Monitoring Module.
30 All elements in this module are read-only.
32 Copyright (c) 2010 IETF Trust and the persons identified as
33 authors of the code. All rights reserved.
35 Redistribution and use in source and binary forms, with or
36 without modification, is permitted pursuant to, and subject
37 to the license terms contained in, the Simplified BSD
38 License set forth in Section 4.c of the IETF Trust's
39 Legal Provisions Relating to IETF Documents
40 (http://trustee.ietf.org/license-info).
42 This version of this YANG module is part of RFC 6022; see
43 the RFC itself for full legal notices.";
49 "RFC 6022: YANG Module for NETCONF Monitoring";
52 typedef tls-fingerprint-type {
54 pattern '([0-9a-fA-F]){2}(:([0-9a-fA-F]){2})*';
57 "A cryptographic signature (fingerprint) value that can be used to
58 uniquely reference other data of potentially arbitrary length.";
61 typedef netconf-datastore-type {
68 "Enumeration of possible NETCONF datastore types.";
70 "RFC 4741: NETCONF Configuration Protocol";
73 container netconf-state {
76 "The netconf-state container is the root of the monitoring
79 container datastores {
81 "Contains the list of NETCONF configuration datastores.";
86 "List of NETCONF configuration datastores supported by
87 the NETCONF server and related information.";
90 type netconf-datastore-type;
92 "Name of the datastore associated with this list entry.";
96 "This container is present only if the datastore
99 "The NETCONF <lock> and <partial-lock> operations allow
100 a client to lock specific resources in a datastore. The
101 NETCONF server will prevent changes to the locked
102 resources by all sessions except the one that acquired
105 Monitoring information is provided for each datastore
106 entry including details such as the session that acquired
107 the lock, the type of lock (global or partial) and the
108 list of locked resources. Multiple locks per datastore
113 "Indicates if a global lock or a set of partial locks
117 container global-lock {
119 "Present if the global lock is set.";
121 leaf locked-by-session {
125 "The session ID of the session that has locked
126 this resource. Both a global lock and a partial
127 lock MUST contain the NETCONF session-id.
129 If the lock is held by a session that is not managed
130 by the NETCONF server (e.g., a CLI session), a session
131 id of 0 (zero) is reported.";
133 "RFC 4741: NETCONF Configuration Protocol";
136 type yang:date-and-time;
139 "The date and time of when the resource was
143 container capabilities {
145 "Contains the list of NETCONF capabilities supported by the
148 leaf-list capability {
151 "List of NETCONF capabilities supported by the server.";
161 "List of partial locks.";
163 "RFC 5717: Partial Lock Remote Procedure Call (RPC) for
169 "This is the lock id returned in the <partial-lock>
176 "The xpath expression that was used to request
177 the lock. The select expression indicates the
178 original intended scope of the lock.";
180 leaf-list locked-node {
183 "The list of instance-identifiers (i.e., the
184 locked nodes). The scope of the partial lock is defined by the list
191 choice algorithm-and-hash {
195 type tls-fingerprint-type;
201 type tls-fingerprint-type;
207 type tls-fingerprint-type;
213 type tls-fingerprint-type;
219 type tls-fingerprint-type;
225 type tls-fingerprint-type;
230 "Specifies the signature algorithm and cryptographic
231 signature (fingerprint) used to identify an X.509
234 Implementations of this YANG module MAY, but are not
235 required to, implement all of these cryptographic signature
236 algorithms. Implementations of this YANG module MUST
237 implement at least one of these cryptographic signature
240 The available choices may be extended in the future as
241 stronger cryptographic signature algorithms become
242 available and are deemed necessary.";
245 "RFC 5246: The Transport Layer Security (TLS) Protocol
246 Version 1.2; Section 7.4.1.4.1, Signature Algorithms";
247 } // choice algorithm-and-hash