draft-ietf-netconf-system-notifications-04.txt   draft-ietf-netconf-system-notifications-05.txt 
NETCONF A. Bierman NETCONF A. Bierman
Internet-Draft Brocade Internet-Draft Brocade
Intended status: Standards Track June 13, 2011 Intended status: Standards Track August 7, 2011
Expires: December 15, 2011 Expires: February 8, 2012
Network Configuration Protocol Base Notifications Network Configuration Protocol (NETCONF) Base Notifications
draft-ietf-netconf-system-notifications-04 draft-ietf-netconf-system-notifications-05
Abstract Abstract
The NETCONF protocol provides mechanisms to manipulate configuration The NETCONF protocol provides mechanisms to manipulate configuration
datastores. However, client applications often need to be aware of datastores. However, client applications often need to be aware of
common events such as a change in NETCONF server capabilities, that common events such as a change in NETCONF server capabilities, that
may impact management applications. Standard mechanisms are needed may impact management applications. Standard mechanisms are needed
to support the monitoring of the base system events within the to support the monitoring of the base system events within the
NETCONF server. This document defines a YANG module that allows a NETCONF server. This document defines a YANG module that allows a
NETCONF client to receive notifications for some common system NETCONF client to receive notifications for some common system
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 December 15, 2011. This Internet-Draft will expire on February 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 14 skipping to change at page 2, line 14
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
2. YANG Module for NETCONF Base Notifications . . . . . . . . . . 3 2. YANG Module for NETCONF Base Notifications . . . . . . . . . . 3
2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.1. Notifications . . . . . . . . . . . . . . . . . . . . 4
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12 4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
6. Normative References . . . . . . . . . . . . . . . . . . . . . 14 6. Normative References . . . . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 15 A.1. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 15
A.2. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 15 A.2. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 15
A.3. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 15
A.4. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.4. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 16
A.5. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.5. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 16
A.6. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
The NETCONF protocol [I-D.ietf-netconf-4741bis] provides mechanisms The NETCONF protocol [RFC6241] provides mechanisms to manipulate
to manipulate configuration datastores. However, client applications configuration datastores. However, client applications often need to
often need to be aware of common events such as a change in NETCONF be aware of common events such as a change in NETCONF server
server capabilities, that may impact management applications. capabilities, that may impact management applications. Standard
Standard mechanisms are needed to support the monitoring of the base mechanisms are needed to support the monitoring of the base system
system events within the NETCONF server. This document defines a events within the NETCONF server. This document defines a YANG
YANG module [RFC6020] that allows a NETCONF client to receive module [RFC6020] that allows a NETCONF client to receive
notifications for some common system events. notifications for some common system events.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The following terms are defined in [I-D.ietf-netconf-4741bis]: The following terms are defined in [RFC6241]:
o client o client
o datastore o datastore
o operation o protocol operation
o server o server
The following terms are defined in [RFC5277]: The following terms are defined in [RFC5277]:
o event o event
o stream o stream
o subscription o subscription
The following term is defined in [RFC6020]: The following term is defined in [RFC6020]:
o data node o data node
2. YANG Module for NETCONF Base Notifications 2. YANG Module for NETCONF Base Notifications
2.1. Overview 2.1. Overview
The YANG module defined within this document specifies a small number The YANG module defined within this document specifies a small number
of notification event messages for use within the 'NETCONF' stream, of event notification messages for use within the 'NETCONF' stream,
and accessible to clients via the subscription mechanism in and accessible to clients via the subscription mechanism in
[RFC5277]. [RFC5277].
These notifications pertain to configuration and monitoring portion These notifications pertain to configuration and monitoring portion
of the managed system, not the entire system. A server MUST report of the managed system, not the entire system. A server MUST report
events that are directly related to the NETCONF protocol. A server events that are directly related to the NETCONF protocol. A server
MAY report events for non-NETCONF management sessions, using the MAY report events for non-NETCONF management sessions, using the
'session-id' value of zero. 'session-id' value of zero.
The YANG language is defined in [RFC6020]. This module defines the following notifications for the 'NETCONF'
stream to notify a client application that the NETCONF server state
2.1.1. Notifications has changed:
This module defines some events for the 'NETCONF' stream to notify a
client application that the NETCONF server state has changed.
netconf-config-change: netconf-config-change:
Generated when the NETCONF server detects that the <running> or Generated when the NETCONF server detects that the <running> or
<startup> configuration datastore has changed. Summarizes each <startup> configuration datastore has changed. Summarizes each
edit being reported. edit being reported.
netconf-capability-change: netconf-capability-change:
Generated when the NETCONF server detects that the server Generated when the NETCONF server detects that the server
capabilities have changed. Indicates which capabilities have been capabilities have changed. Indicates which capabilities have been
added, deleted, and/or modified. added, deleted, and/or modified. The manner in which a server
capability is changed is outside the scope of this document.
netconf-session-start: netconf-session-start:
Generated when a NETCONF server detects that a NETCONF session has Generated when a NETCONF server detects that a NETCONF session has
started. A server MAY generate this event for non-NETCONF started. A server MAY generate this event for non-NETCONF
management sessions. Indicates the identity of the user that management sessions. Indicates the identity of the user that
started the session. started the session.
netconf-session-end: netconf-session-end:
Generated when a NETCONF server detects that a NETCONF session has Generated when a NETCONF server detects that a NETCONF session has
terminated. A server MAY optionally generate this event for non- terminated. A server MAY optionally generate this event for non-
NETCONF management sessions. Indicates the identity of the user NETCONF management sessions. Indicates the identity of the user
that owned the session, and why the session was terminated. that owned the session, and why the session was terminated.
netconf-confirmed-commit: netconf-confirmed-commit:
Generated when a NETCONF server detects that a confirmed-commit Generated when a NETCONF server detects that a confirmed-commit
event has occurred. Indicates the event and the current state of event has occurred. Indicates the event and the current state of
the confirmed-commit operation in progress. the confirmed-commit procedure in progress.
2.2. Definitions 2.2. Definitions
<CODE BEGINS> file="ietf-netconf-base-notifications@2011-06-13.yang" <CODE BEGINS> file="ietf-netconf-notifications@2011-08-07.yang"
module ietf-netconf-base-notifications { module ietf-netconf-notifications {
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-netconf-base-notifications"; "urn:ietf:params:xml:ns:yang:ietf-netconf-notifications";
prefix ncbase; prefix ncn;
import ietf-inet-types { prefix inet; } import ietf-inet-types { prefix inet; }
import ietf-netconf { prefix nc; } import ietf-netconf { prefix nc; }
organization organization
"IETF NETCONF (Network Configuration Protocol) Working Group"; "IETF NETCONF (Network Configuration Protocol) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netconf/> "WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
skipping to change at page 5, line 18 skipping to change at page 5, line 18
WG Chair: Mehmet Ersue WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com> <mailto:mehmet.ersue@nsn.com>
Editor: Andy Bierman Editor: Andy Bierman
<mailto:andy.bierman@brocade.com>"; <mailto:andy.bierman@brocade.com>";
description description
"This module defines an YANG data model for use with the "This module defines an YANG data model for use with the
NETCONF protocol that allows the NETCONF client to NETCONF protocol that allows the NETCONF client to
receive common NETCONF base notification events. receive common NETCONF base event notifications.
Copyright (c) 2011 IETF Trust and the persons identified as Copyright (c) 2011 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
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 note // RFC Ed.: replace XXXX with actual RFC number and remove this note
// RFC Ed.: remove this note // RFC Ed.: remove this note
// Note: extracted from // Note: extracted from
// draft-ietf-netconf-system-notifications-04.txt // draft-ietf-netconf-system-notifications-05.txt
revision 2011-06-13 { revision 2011-08-07 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXXX: NETCONF Base Notifications"; "RFC XXXX: NETCONF Base Notifications";
} }
// RFC Ed.: replace XXXX with actual // RFC Ed.: replace XXXX with actual
// RFC number and remove this note // RFC number and remove this note
grouping common-session-parms { grouping common-session-parms {
description description
"Common session parameters to identity a "Common session parameters to identify a
management session."; management session.";
leaf username { leaf username {
description description
"Name of the user for the session."; "Name of the user for the session.";
type string; type string;
mandatory true; mandatory true;
} }
leaf session-id { leaf session-id {
description description
"Identifier of the session. "Identifier of the session.
A non-NETCONF session will be identified by the value zero."; A NETCONF session MUST be identified by a non-zero value.
A non-NETCONF session MAY be identified by the value zero.";
type nc:session-id-or-zero-type; type nc:session-id-or-zero-type;
mandatory true; mandatory true;
} }
leaf source-host { leaf source-host {
description description
"Address of the remote host for the session."; "Address of the remote host for the session.";
type inet:ip-address; type inet:ip-address;
} }
} }
skipping to change at page 7, line 15 skipping to change at page 7, line 15
} }
} // choice server-or-user } // choice server-or-user
} // container changed-by-parms; } // container changed-by-parms;
} }
notification netconf-config-change { notification netconf-config-change {
description description
"Generated when the NETCONF server detects that the "Generated when the NETCONF server detects that the
<running> or <startup> configuration datastore <running> or <startup> configuration datastore
has changed by a management session. has changed by a management session.
Summarizes each edit being reported. The notification summarizes the edits that
have been detected.
The server MAY choose to also generate this The server MAY choose to also generate this
notification while loading a datastore during the notification while loading a datastore during the
boot process for the device."; boot process for the device.";
uses changed-by-parms; uses changed-by-parms;
leaf target-datastore { leaf datastore {
type enumeration { type enumeration {
enum running { enum running {
description "The <running> datastore has changed."; description "The <running> datastore has changed.";
} }
enum startup { enum startup {
description "The <startup> datastore has changed"; description "The <startup> datastore has changed";
} }
} }
description description
"Indicates which configuration datastore has changed."; "Indicates which configuration datastore has changed.";
skipping to change at page 8, line 23 skipping to change at page 8, line 27
operation performed on the target datastore."; operation performed on the target datastore.";
} }
} // list edit } // list edit
} // notification netconf-config-change } // notification netconf-config-change
notification netconf-capability-change { notification netconf-capability-change {
description description
"Generated when the NETCONF server detects that "Generated when the NETCONF server detects that
the server capabilities have changed. the server capabilities have changed.
Indicates which capabilities have been added, deleted, Indicates which capabilities have been added, deleted,
and/or modified."; and/or modified. The manner in which a server
capability is changed is outside the scope of this
document.";
uses changed-by-parms; uses changed-by-parms;
leaf-list added-capability { leaf-list added-capability {
type inet:uri; type inet:uri;
description description
"List of capabilities that have just been added."; "List of capabilities that have just been added.";
} }
leaf-list deleted-capability { leaf-list deleted-capability {
skipping to change at page 9, line 26 skipping to change at page 9, line 31
"Generated when a NETCONF server detects that a "Generated when a NETCONF server detects that a
NETCONF session has terminated. NETCONF session has terminated.
A server MAY optionally generate this event for A server MAY optionally generate this event for
non-NETCONF management sessions. Indicates the non-NETCONF management sessions. Indicates the
identity of the user that owned the session, identity of the user that owned the session,
and why the session was terminated."; and why the session was terminated.";
uses common-session-parms; uses common-session-parms;
leaf killed-by { leaf killed-by {
when "../termination-reason = 'killed'"; when "../termination-reason = 'killed' and .";
type nc:session-id-type; type nc:session-id-type;
description description
"The session ID that issued the <kill-session>, "The ID of the session that directly caused this session
if the session was terminated by this operation. to be abnormally terminated. If this session was abnormally
If the session was abnormally terminated by a terminated by a non-NETCONF session unknown to the server,
non-NETCONF client operation, the value '0' will be then this leaf will not be present.";
used instead.";
} }
leaf termination-reason { leaf termination-reason {
type enumeration { type enumeration {
enum "closed" { enum "closed" {
value 0;
description description
"The session was terminated by the client in normal "The session was terminated by the client in normal
fashion, e.g., by the NETCONF <close-session> fashion, e.g., by the NETCONF <close-session>
operation."; protocol operation.";
} }
enum "killed" { enum "killed" {
value 1;
description description
"The session was terminated by the client in abnormal "The session was terminated in abnormal
fashion, e.g., by the NETCONF <kill-session> fashion, e.g., by the NETCONF <kill-session>
operation."; protocol operation.";
} }
enum "dropped" { enum "dropped" {
value 2;
description description
"The session was terminated because the transport layer "The session was terminated because the transport layer
connection was unexpectedly closed."; connection was unexpectedly closed.";
} }
enum "timeout" { enum "timeout" {
value 3;
description description
"The session was terminated because of inactivity, "The session was terminated because of inactivity,
e.g., waiting for the <hello> message or <rpc> e.g., waiting for the <hello> message or <rpc>
messages."; messages.";
} }
enum "bad-hello" { enum "bad-hello" {
value 4;
description description
"The client's <hello> message was invalid."; "The client's <hello> message was invalid.";
} }
enum "other" { enum "other" {
value 5;
description description
"The session was terminated for some other reason."; "The session was terminated for some other reason.";
} }
} }
mandatory true; mandatory true;
description description
"Reason the session was terminated."; "Reason the session was terminated.";
} }
} // notification netconf-session-end } // notification netconf-session-end
notification netconf-confirmed-commit { notification netconf-confirmed-commit {
description description
"Generated when a NETCONF server detects that a confirmed-commit "Generated when a NETCONF server detects that a confirmed-commit
event has occurred. Indicates the event and the current state event has occurred. Indicates the event and the current state
of the confirmed-commit operation in progress."; of the confirmed-commit procedure in progress.";
reference reference
"I-D draft-ietf-netconf-4741bis section 8.4"; "RFC 6241, section 8.4";
uses common-session-parms { uses common-session-parms {
when "../confirm-event != 'timeout'"; when "../confirm-event != 'timeout'";
} }
leaf confirm-event { leaf confirm-event {
description description
"Indicates the event that caused the notification."; "Indicates the event that caused the notification.";
type enumeration { type enumeration {
enum "start" { enum "start" {
skipping to change at page 12, line 6 skipping to change at page 12, line 4
"The configured timeout value if the event type "The configured timeout value if the event type
is 'start' or 'extend'. This value represents the is 'start' or 'extend'. This value represents the
the approximate number of seconds from the event the approximate number of seconds from the event
time when the 'timeout' event might occur."; time when the 'timeout' event might occur.";
units "seconds"; units "seconds";
type uint32; type uint32;
} }
} // notification netconf-confirmed-commit } // notification netconf-confirmed-commit
} }
<CODE ENDS> <CODE ENDS>
3. IANA Considerations 3. IANA Considerations
This document registers one XML namespace URN in the 'IETF XML This document registers one XML namespace URN in the 'IETF XML
registry', following the format defined in [RFC3688]. registry', following the format defined in [RFC3688].
URI: urn:ietf:params:xml:ns:yang:ietf-netconf-base-notifications URI: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
Registrant Contact: The NETCONF WG of the IETF. Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers one module name in the 'YANG Module Names' This document registers one module name in the 'YANG Module Names'
registry, defined in [RFC6020] . registry, defined in [RFC6020] .
name: ietf-netconf-base-notifications name: ietf-netconf-notifications
prefix: ncbase prefix: ncn
namespace: namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
urn:ietf:params:xml:ns:yang:ietf-netconf-base-notifications
RFC: XXXX // RFC Ed.: replace XXXX and remove this comment RFC: XXXX // RFC Ed.: replace XXXX and remove this comment
4. Security Considerations 4. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC4741]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC4742]. transport is SSH, defined in [RFC6242].
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via <get>, <get-config>, or important to control read access (e.g., via <get>, <get-config>, or
<notification>) to these data nodes. These are the subtrees and data <notification>) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/netconf-config-change: /netconf-config-change:
Event type itself indicates that the system configuration has Event type itself indicates that the system configuration has
changed, and may be now be vulnerable to unspecified attacks. changed.
/netconf-config-change/changed-by: /netconf-config-change/changed-by:
Indicates whether the server or a specific user management session Indicates whether the server or a specific user management session
made the configuration change. Identifies the user name, made the configuration change. Identifies the user name,
session-id, and source host address associated with the session-id, and source host address associated with the
configuration change, if any. configuration change, if any.
/netconf-config-change/datastore: /netconf-config-change/datastore:
Indicates which datastore has been changed. This data can be used Indicates which datastore has been changed. This data can be used
to determine if the non-volatile startup configuration data has to determine if the non-volatile startup configuration data has
been changed. been changed.
skipping to change at page 14, line 48 skipping to change at page 14, line 48
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event
Notifications", RFC 5277, July 2008. Notifications", RFC 5277, July 2008.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010. October 2010.
[I-D.ietf-netconf-4741bis] [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", Bierman, "Network Configuration Protocol (NETCONF)",
draft-ietf-netconf-4741bis-10 (work in progress), RFC 6241, June 2011.
March 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011.
Appendix A. Change Log Appendix A. Change Log
-- RFC Ed.: remove this section before publication. -- RFC Ed.: remove this section before publication.
A.1. 03-04 A.1. 04-05
The module is now ietf-netconf-notifications. The namespace and
prefix are now changed as well.
The target-datastore has been renamed to datastore.
Clarified behavior for non-NETCONF sessions.
Minor editorial comments from WG Last Call.
A.2. 03-04
Renamed module to NETCONF Base Notifications. The module is now Renamed module to NETCONF Base Notifications. The module is now
ietf-netconf-base-notifications. The namespace and prefix are now ietf-netconf-base-notifications. The namespace and prefix are now
changed as well. changed as well.
Changed notifications so a server can report non-NETCONF initiated Changed notifications so a server can report non-NETCONF initiated
events. events.
Replaced security considerations, according to template in RFC 6087. Replaced security considerations, according to template in RFC 6087.
Added Acknowledgements section. Added Acknowledgements section.
A.2. 02-03 A.3. 02-03
Renamed module back to NETCONF system notifications. The module is Renamed module back to NETCONF system notifications. The module is
now ietf-netconf-system-notifications. The namespace and prefix are now ietf-netconf-system-notifications. The namespace and prefix are
now changed as well. now changed as well.
Leaf user-name is now username, and is now mandatory, to be Leaf user-name is now username, and is now mandatory, to be
consistent with netconf monitoring module. consistent with netconf monitoring module.
Leaf remote-host is now source-host to be consistent with netconf Leaf remote-host is now source-host to be consistent with netconf
monitoring module. monitoring module.
skipping to change at page 16, line 5 skipping to change at page 16, line 12
The netconf-config-change description was updated and leaf target- The netconf-config-change description was updated and leaf target-
database is now named target-datastore. database is now named target-datastore.
Term 'database' changed to term 'datastore' in text. Term 'database' changed to term 'datastore' in text.
netconf-confirmed-commit: changed uses common-session-parms to use netconf-confirmed-commit: changed uses common-session-parms to use
when-stmt not refine-stmt. when-stmt not refine-stmt.
netconf-capability-change: updated description text. netconf-capability-change: updated description text.
A.3. 01-02 A.4. 01-02
Renamed module NETCONF Events instead of NETCONF system Renamed module NETCONF Events instead of NETCONF system
notifications. Note that ietf-netconf-notifications is being notifications. Note that ietf-netconf-notifications is being
reserved for the XML content defined in RFC 5277. reserved for the XML content defined in RFC 5277.
Made changes based on mailing list comments and latest WG consensus. Made changes based on mailing list comments and latest WG consensus.
Filled in IANA section. Filled in IANA section.
A.4. 00-01 A.5. 00-01
Removed sys-startup notification. Removed sys-startup notification.
Make changed-by into a grouping, and added usage to sys-config-change Make changed-by into a grouping, and added usage to sys-config-change
notification. notification.
Added target-database leaf to sys-config-change to distinguish Added target-database leaf to sys-config-change to distinguish
between running and startup changes. between running and startup changes.
Removed 'bad-start' from termination-reason leaf in sys-session-end Removed 'bad-start' from termination-reason leaf in sys-session-end
notification. notification.
A.5. 00 A.6. 00
Initial version, based on Initial version, based on
draft-bierman-netconf-system-monitoring-00.txt. draft-bierman-netconf-system-monitoring-00.txt.
Author's Address Author's Address
Andy Bierman Andy Bierman
Brocade Brocade
Email: andy.bierman@brocade.com Email: andy.bierman@brocade.com
 End of changes. 51 change blocks. 
76 lines changed or deleted 82 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/