IETF NETCONF (Network Configuration Protocol) Working Group WG Web: <http://tools.ietf.org/wg/netconf/> WG List: <mailto:netconf@ietf.org> WG Chair: Bert Wijnen <mailto:bertietf@bwijnen.net> WG Chair: Mehmet Ersue <mailto:mehmet.ersue@nsn.com> Editor: Andy Bierman <mailto:andy@netconfcentral.org> This module defines a YANG data model for use with the NETCONF protocol that allows the NETCONF client to receive common NETCONF base event notifications. Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 6470; see the RFC itself for full legal notices. Initial version. RFC 6470: NETCONF Base Notifications Common session parameters to identify a management session. Name of the user for the session. Identifier of the session. A NETCONF session MUST be identified by a non-zero value. A non-NETCONF session MAY be identified by the value zero. Address of the remote host for the session. Common parameters to identify the source of a change event, such as a configuration or capability change. Indicates the source of the change. If caused by internal action, then the empty leaf 'server' will be present. If caused by a management session, then the name, remote host address, and session ID of the session that made the change will be reported. If present, the change was caused by the server. Generated when the NETCONF server detects that the <running> or <startup> configuration datastore has been changed by a management session. The notification summarizes the edits that have been detected. The server MAY choose to also generate this notification while loading a datastore during the boot process for the device. The <running> datastore has changed. The <startup> datastore has changed Indicates which configuration datastore has changed. An edit record SHOULD be present for each distinct edit operation that the server has detected on the target datastore. This list MAY be omitted if the detailed edit operations are not known. The server MAY report entries in this list for changes not made by a NETCONF session (e.g., CLI). Topmost node associated with the configuration change. A server SHOULD set this object to the node within the datastore that is being altered. A server MAY set this object to one of the ancestors of the actual node that was changed, or omit this object, if the exact node is not known. Type of edit operation performed. A server MUST set this object to the NETCONF edit operation performed on the target datastore. Generated when the NETCONF server detects that the server capabilities have changed. Indicates which capabilities have been added, deleted, and/or modified. The manner in which a server capability is changed is outside the scope of this document. List of capabilities that have just been added. List of capabilities that have just been deleted. List of capabilities that have just been modified. A capability is considered to be modified if the base URI for the capability has not changed, but one or more of the parameters encoded at the end of the capability URI have changed. The new modified value of the complete URI is returned. Generated when a NETCONF server detects that a NETCONF session has started. A server MAY generate this event for non-NETCONF management sessions. Indicates the identity of the user that started the session. Generated when a NETCONF server detects that a NETCONF session has terminated. A server MAY optionally generate this event for non-NETCONF management sessions. Indicates the identity of the user that owned the session, and why the session was terminated. The ID of the session that directly caused this session to be abnormally terminated. If this session was abnormally terminated by a non-NETCONF session unknown to the server, then this leaf will not be present. The session was terminated by the client in normal fashion, e.g., by the NETCONF <close-session> protocol operation. The session was terminated in abnormal fashion, e.g., by the NETCONF <kill-session> protocol operation. The session was terminated because the transport layer connection was unexpectedly closed. The session was terminated because of inactivity, e.g., waiting for the <hello> message or <rpc> messages. The client's <hello> message was invalid. The session was terminated for some other reason. Reason the session was terminated. Generated when a NETCONF server detects that a confirmed-commit event has occurred. Indicates the event and the current state of the confirmed-commit procedure in progress. RFC 6241, Section 8.4 The confirmed-commit procedure has started. The confirmed-commit procedure has been canceled, e.g., due to the session being terminated, or an explicit <cancel-commit> operation. The confirmed-commit procedure has been canceled due to the confirm-timeout interval expiring. The common session parameters will not be present in this sub-mode. The confirmed-commit timeout has been extended, e.g., by a new <confirmed-commit> operation. The confirmed-commit procedure has been completed. Indicates the event that caused the notification. The configured timeout value if the event type is 'start' or 'extend'. This value represents the approximate number of seconds from the event time when the 'timeout' event might occur.