Internet Engineering Task Force (IETF) A. Bierman
Request for Comments: 6470 Brocade
Category: Standards Track February 2012
ISSN: 2070-1721
Internet Engineering Task Force (IETF) A. Bierman
Request for Comments: 6470 Brocade
Category: Standards Track February 2012
ISSN: 2070-1721
Network Configuration Protocol (NETCONF) Base Notifications
网络配置协议（NETCONF）基本通知
Abstract
摘要
The Network Configuration Protocol (NETCONF) provides mechanisms to manipulate configuration datastores. However, client applications often need to be aware of common events, such as a change in NETCONF server capabilities, that may impact management applications. Standard mechanisms are needed to support the monitoring of the base system events within the NETCONF server. This document defines a YANG module that allows a NETCONF client to receive notifications for some common system events.
网络配置协议（NETCONF）提供了操作配置数据存储的机制。但是，客户端应用程序通常需要知道可能影响管理应用程序的常见事件，例如NETCONF服务器功能的更改。需要标准机制来支持对NETCONF服务器内基本系统事件的监视。本文档定义了一个模块，该模块允许NETCONF客户端接收一些常见系统事件的通知。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6470.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6470.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Terminology ................................................2
2. YANG Module for NETCONF Base Notifications ......................3
2.1. Overview ...................................................3
2.2. Definitions ................................................4
3. IANA Considerations ............................................11
4. Security Considerations ........................................12
5. Acknowledgements ...............................................14
6. Normative References ...........................................14
1. Introduction ....................................................2
1.1. Terminology ................................................2
2. YANG Module for NETCONF Base Notifications ......................3
2.1. Overview ...................................................3
2.2. Definitions ................................................4
3. IANA Considerations ............................................11
4. Security Considerations ........................................12
5. Acknowledgements ...............................................14
6. Normative References ...........................................14
The NETCONF protocol [RFC6241] provides mechanisms to manipulate configuration datastores. However, client applications often need to be aware of common events, such as a change in NETCONF server capabilities, that may impact management applications. Standard mechanisms are needed to support the monitoring of the base system events within the NETCONF server. This document defines a YANG module [RFC6020] that allows a NETCONF client to receive notifications for some common system events.
NETCONF协议[RFC6241]提供了操作配置数据存储的机制。但是，客户端应用程序通常需要知道可能影响管理应用程序的常见事件，例如NETCONF服务器功能的更改。需要标准机制来支持对NETCONF服务器内基本系统事件的监视。本文档定义了一个模块[RFC6020]，该模块允许NETCONF客户端接收一些常见系统事件的通知。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The following terms are defined in [RFC6241]:
[RFC6241]中定义了以下术语：
o client o datastore o protocol operation o server
o 客户端o数据存储o协议操作o服务器
The following terms are defined in [RFC5277]:
[RFC5277]中定义了以下术语：
o event o stream o subscription
o 事件o流o订阅
The following term is defined in [RFC6020]:
[RFC6020]中定义了以下术语：
o data node
o 数据节点
The YANG module defined within this document specifies a small number of event notification messages for use within the 'NETCONF' stream, and accessible to clients via the subscription mechanism described in [RFC5277]. This module imports data types from the 'ietf-netconf' module defined in [RFC6241] and 'ietf-inet-types' module defined in [RFC6021].
本文档中定义的模块指定了少量事件通知消息，用于“NETCONF”流中，并可通过[RFC5277]中描述的订阅机制供客户端访问。此模块从[RFC6241]中定义的“ietf netconf”模块和[RFC6021]中定义的“ietf inet types”模块导入数据类型。
These notifications pertain to configuration and monitoring portions of the managed system, not the entire system. A server MUST report events that are directly related to the NETCONF protocol. A server MAY report events for non-NETCONF management sessions, using the 'session-id' value of zero.
这些通知涉及受管系统的配置和监视部分，而不是整个系统。服务器必须报告与NETCONF协议直接相关的事件。服务器可以使用“会话id”值零报告非NETCONF管理会话的事件。
This module defines the following notifications for the 'NETCONF' stream to notify a client application that the NETCONF server state has changed:
此模块为“NETCONF”流定义以下通知，以通知客户端应用程序NETCONF服务器状态已更改：
netconf-config-change: 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.
netconf配置更改：当netconf服务器检测到<running>或<startup>配置数据存储已被管理会话更改时生成。通知汇总了已检测到的编辑。
netconf-capability-change: 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.
netconf功能更改：当netconf服务器检测到服务器功能已更改时生成。指示已添加、删除和/或修改的功能。更改服务器功能的方式超出了本文档的范围。
netconf-session-start: 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.
netconf会话启动：当netconf服务器检测到netconf会话已启动时生成。服务器可能会为非NETCONF管理会话生成此事件。指示启动会话的用户的标识。
netconf-session-end: 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.
netconf会话结束：当netconf服务器检测到netconf会话已终止时生成。服务器可以选择为非NETCONF管理会话生成此事件。指示拥有会话的用户的身份，以及会话终止的原因。
netconf-confirmed-commit: 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.
netconf确认提交：当netconf服务器检测到发生确认提交事件时生成。指示正在进行的已确认提交过程的事件和当前状态。
<CODE BEGINS> file="ietf-netconf-notifications@2011-12-09.yang"
<CODE BEGINS> file="ietf-netconf-notifications@2011-12-09.yang"
module ietf-netconf-notifications {
模块ietf netconf通知{
namespace
"urn:ietf:params:xml:ns:yang:ietf-netconf-notifications";
namespace
"urn:ietf:params:xml:ns:yang:ietf-netconf-notifications";
prefix ncn;
前缀ncn；
import ietf-inet-types { prefix inet; }
import ietf-netconf { prefix nc; }
import ietf-inet-types { prefix inet; }
import ietf-netconf { prefix nc; }
organization "IETF NETCONF (Network Configuration Protocol) Working Group";
组织“IETF网络配置协议工作组”；
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
WG Chair: Bert Wijnen
<mailto:bertietf@bwijnen.net>
WG Chair: Bert Wijnen
<mailto:bertietf@bwijnen.net>
WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com>
Editor: Andy Bierman
<mailto:andy@netconfcentral.org>";
Editor: Andy Bierman
<mailto:andy@netconfcentral.org>";
description "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.
description“此模块定义一个数据模型，用于NETCONF协议，允许NETCONF客户端接收常见的NETCONF基本事件通知。
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
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
根据简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改
set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
IETF信托法律条款第4.c节中规定的IETF文件(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.";
此模块的此版本是RFC 6470的一部分；有关完整的法律通知，请参见RFC本身。“；
revision "2012-02-06" {
description
"Initial version.";
reference
"RFC 6470: NETCONF Base Notifications";
}
revision "2012-02-06" {
description
"Initial version.";
reference
"RFC 6470: NETCONF Base Notifications";
}
grouping common-session-parms {
description
"Common session parameters to identify a
management session.";
grouping common-session-parms {
description
"Common session parameters to identify a
management session.";
leaf username {
type string;
mandatory true;
description
"Name of the user for the session.";
}
leaf username {
type string;
mandatory true;
description
"Name of the user for the session.";
}
leaf session-id {
type nc:session-id-or-zero-type;
mandatory true;
description
"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.";
}
leaf session-id {
type nc:session-id-or-zero-type;
mandatory true;
description
"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.";
}
leaf source-host {
type inet:ip-address;
description
"Address of the remote host for the session.";
}
}
leaf source-host {
type inet:ip-address;
description
"Address of the remote host for the session.";
}
}
grouping changed-by-parms {
description
"Common parameters to identify the source
of a change event, such as a configuration
or capability change.";
grouping changed-by-parms {
description
"Common parameters to identify the source
of a change event, such as a configuration
or capability change.";
container changed-by {
description
"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.";
choice server-or-user {
mandatory true;
leaf server {
type empty;
description
"If present, the change was caused
by the server.";
}
container changed-by {
description
"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.";
choice server-or-user {
mandatory true;
leaf server {
type empty;
description
"If present, the change was caused
by the server.";
}
case by-user {
uses common-session-parms;
}
} // choice server-or-user
} // container changed-by-parms
}
case by-user {
uses common-session-parms;
}
} // choice server-or-user
} // container changed-by-parms
}
notification netconf-config-change { description "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.
netconf服务器检测到管理会话更改了<running>或<startup>配置数据存储时生成的通知netconf config change{description]。该通知总结了检测到的编辑。
The server MAY choose to also generate this notification while loading a datastore during the boot process for the device.";
在设备引导过程中加载数据存储时，服务器也可以选择生成此通知。“；
uses changed-by-parms;
由parms更改的用途；
leaf datastore {
type enumeration {
enum running {
description "The <running> datastore has changed.";
}
enum startup {
description "The <startup> datastore has changed";
}
}
default "running";
description
"Indicates which configuration datastore has changed.";
}
leaf datastore {
type enumeration {
enum running {
description "The <running> datastore has changed.";
}
enum startup {
description "The <startup> datastore has changed";
}
}
default "running";
description
"Indicates which configuration datastore has changed.";
}
list edit {
description
"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).";
list edit {
description
"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).";
leaf target {
type instance-identifier;
description
"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.";
}
leaf target {
type instance-identifier;
description
"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.";
}
leaf operation {
type nc:edit-operation-type;
description
"Type of edit operation performed.
A server MUST set this object to the NETCONF edit
operation performed on the target datastore.";
}
} // list edit
} // notification netconf-config-change
leaf operation {
type nc:edit-operation-type;
description
"Type of edit operation performed.
A server MUST set this object to the NETCONF edit
operation performed on the target datastore.";
}
} // list edit
} // notification netconf-config-change
notification netconf-capability-change {
description
"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.";
notification netconf-capability-change {
description
"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.";
uses changed-by-parms;
由parms更改的用途；
leaf-list added-capability {
type inet:uri;
description
"List of capabilities that have just been added.";
}
leaf-list added-capability {
type inet:uri;
description
"List of capabilities that have just been added.";
}
leaf-list deleted-capability {
type inet:uri;
description
"List of capabilities that have just been deleted.";
}
leaf-list deleted-capability {
type inet:uri;
description
"List of capabilities that have just been deleted.";
}
leaf-list modified-capability {
type inet:uri;
description
"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.";
}
} // notification netconf-capability-change
leaf-list modified-capability {
type inet:uri;
description
"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.";
}
} // notification netconf-capability-change
notification netconf-session-start {
description
"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.";
uses common-session-parms;
} // notification netconf-session-start
notification netconf-session-start {
description
"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.";
uses common-session-parms;
} // notification netconf-session-start
notification netconf-session-end {
description
"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.";
notification netconf-session-end {
description
"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.";
uses common-session-parms;
使用公共会话参数；
leaf killed-by {
when "../termination-reason = 'killed'";
type nc:session-id-type;
description
"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.";
}
leaf killed-by {
when "../termination-reason = 'killed'";
type nc:session-id-type;
description
"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.";
}
leaf termination-reason {
type enumeration {
enum "closed" {
description
"The session was terminated by the client in normal
fashion, e.g., by the NETCONF <close-session>
protocol operation.";
}
enum "killed" {
description
"The session was terminated in abnormal
fashion, e.g., by the NETCONF <kill-session>
protocol operation.";
}
enum "dropped" {
description
"The session was terminated because the transport layer
connection was unexpectedly closed.";
}
enum "timeout" {
description
"The session was terminated because of inactivity,
e.g., waiting for the <hello> message or <rpc>
messages.";
}
leaf termination-reason {
type enumeration {
enum "closed" {
description
"The session was terminated by the client in normal
fashion, e.g., by the NETCONF <close-session>
protocol operation.";
}
enum "killed" {
description
"The session was terminated in abnormal
fashion, e.g., by the NETCONF <kill-session>
protocol operation.";
}
enum "dropped" {
description
"The session was terminated because the transport layer
connection was unexpectedly closed.";
}
enum "timeout" {
description
"The session was terminated because of inactivity,
e.g., waiting for the <hello> message or <rpc>
messages.";
}
enum "bad-hello" {
description
"The client's <hello> message was invalid.";
}
enum "other" {
description
"The session was terminated for some other reason.";
}
}
mandatory true;
description
"Reason the session was terminated.";
}
} // notification netconf-session-end
enum "bad-hello" {
description
"The client's <hello> message was invalid.";
}
enum "other" {
description
"The session was terminated for some other reason.";
}
}
mandatory true;
description
"Reason the session was terminated.";
}
} // notification netconf-session-end
notification netconf-confirmed-commit {
description
"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.";
reference
"RFC 6241, Section 8.4";
notification netconf-confirmed-commit {
description
"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.";
reference
"RFC 6241, Section 8.4";
uses common-session-parms {
when "../confirm-event != 'timeout'";
}
uses common-session-parms {
when "../confirm-event != 'timeout'";
}
leaf confirm-event {
type enumeration {
enum "start" {
description
"The confirmed-commit procedure has started.";
}
enum "cancel" {
description
"The confirmed-commit procedure has been canceled,
e.g., due to the session being terminated, or an
explicit <cancel-commit> operation.";
}
enum "timeout" {
description
"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.";
}
leaf confirm-event {
type enumeration {
enum "start" {
description
"The confirmed-commit procedure has started.";
}
enum "cancel" {
description
"The confirmed-commit procedure has been canceled,
e.g., due to the session being terminated, or an
explicit <cancel-commit> operation.";
}
enum "timeout" {
description
"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.";
}
enum "extend" {
description
"The confirmed-commit timeout has been extended,
e.g., by a new <confirmed-commit> operation.";
}
enum "complete" {
description
"The confirmed-commit procedure has been completed.";
}
}
mandatory true;
description
"Indicates the event that caused the notification.";
}
enum "extend" {
description
"The confirmed-commit timeout has been extended,
e.g., by a new <confirmed-commit> operation.";
}
enum "complete" {
description
"The confirmed-commit procedure has been completed.";
}
}
mandatory true;
description
"Indicates the event that caused the notification.";
}
leaf timeout {
when
"../confirm-event = 'start' or ../confirm-event = 'extend'";
type uint32;
units "seconds";
description
"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.";
}
} // notification netconf-confirmed-commit
leaf timeout {
when
"../confirm-event = 'start' or ../confirm-event = 'extend'";
type uint32;
units "seconds";
description
"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.";
}
} // notification netconf-confirmed-commit
}
}
<CODE ENDS>
<代码结束>
This document registers one XML namespace URN in the 'IETF XML registry', following the format defined in [RFC3688].
本文档按照[RFC3688]中定义的格式，在“IETF XML注册表”中注册一个XML名称空间URN。
URI: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
URI: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
Registrant Contact: The IESG.
注册人联系人：IESG。
XML: N/A; the requested URI is an XML namespace.
XML：不适用；请求的URI是一个XML命名空间。
This document registers one module name in the 'YANG Module Names' registry, defined in [RFC6020].
本文件在[RFC6020]中定义的“模块名称”注册表中注册了一个模块名称。
name: ietf-netconf-notifications
prefix: ncn
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
RFC: 6470
name: ietf-netconf-notifications
prefix: ncn
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
RFC: 6470
The YANG module defined in this memo is designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer and the mandatory-to-implement secure transport is SSH, defined in [RFC6242].
本备忘录中定义的模块旨在通过NETCONF协议[RFC6241]访问。最低的NETCONF层是安全传输层，实现安全传输所必需的是SSH，定义见[RFC6242]。
Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:
在某些网络环境中，此模块中的某些可读数据节点可能被视为敏感或易受攻击。因此，控制对这些数据节点的读取访问（例如，通过get、get config或通知）非常重要。这些是子树和数据节点及其敏感性/漏洞：
/netconf-config-change:
Event type itself indicates that the system configuration has
changed. This event could alert an attacker that specific
configuration data nodes have been altered.
/netconf-config-change/changed-by:
Indicates whether the server or a specific user management session
made the configuration change. Identifies the user name,
session-id, and source host address associated with the
configuration change, if any.
/netconf-config-change/datastore:
Indicates which datastore has been changed. This data can be used
to determine if the non-volatile startup configuration data has
been changed.
/netconf-config-change/edit:
Identifies the specific edit operations and specific datastore
subtree(s) that have changed. This data could be used to
determine if specific server vulnerabilities may now be present.
/netconf-config-change:
Event type itself indicates that the system configuration has
changed. This event could alert an attacker that specific
configuration data nodes have been altered.
/netconf-config-change/changed-by:
Indicates whether the server or a specific user management session
made the configuration change. Identifies the user name,
session-id, and source host address associated with the
configuration change, if any.
/netconf-config-change/datastore:
Indicates which datastore has been changed. This data can be used
to determine if the non-volatile startup configuration data has
been changed.
/netconf-config-change/edit:
Identifies the specific edit operations and specific datastore
subtree(s) that have changed. This data could be used to
determine if specific server vulnerabilities may now be present.
/netconf-capability-change:
Event type itself indicates that the system capabilities have
changed, and may now be vulnerable to unspecified attacks. An
attacker will likely need to understand the content represented by
specific capability URI strings. For example, knowing that a
packet capture monitoring capability has been added to the system
might help an attacker identify the device for possible
unauthorized eavesdropping.
/netconf-capability-change/changed-by:
Indicates whether the server or a specific user management session
made the capability change. Identifies the user name, session-id,
and source host address associated with the capability change, if
any.
/netconf-capability-change/added-capability:
Indicates the specific capability URIs that have been added. This
data could be used to determine if specific server vulnerabilities
may now be present.
/netconf-capability-change/deleted-capability:
Indicates the specific capability URIs that have been deleted.
This data could be used to determine if specific server
vulnerabilities may now be present.
/netconf-capability-change/modified-capability:
Indicates the specific capability URIs that have been modified.
This data could be used to determine if specific server
vulnerabilities may now be present.
/netconf-capability-change:
Event type itself indicates that the system capabilities have
changed, and may now be vulnerable to unspecified attacks. An
attacker will likely need to understand the content represented by
specific capability URI strings. For example, knowing that a
packet capture monitoring capability has been added to the system
might help an attacker identify the device for possible
unauthorized eavesdropping.
/netconf-capability-change/changed-by:
Indicates whether the server or a specific user management session
made the capability change. Identifies the user name, session-id,
and source host address associated with the capability change, if
any.
/netconf-capability-change/added-capability:
Indicates the specific capability URIs that have been added. This
data could be used to determine if specific server vulnerabilities
may now be present.
/netconf-capability-change/deleted-capability:
Indicates the specific capability URIs that have been deleted.
This data could be used to determine if specific server
vulnerabilities may now be present.
/netconf-capability-change/modified-capability:
Indicates the specific capability URIs that have been modified.
This data could be used to determine if specific server
vulnerabilities may now be present.
/netconf-session-start:
Event type itself indicates that a NETCONF or other management
session may start altering the device configuration and/or state.
It may be possible for an attacker to alter the configuration by
somehow taking advantage of another session concurrently editing
an unlocked datastore.
/netconf-session-start/username:
Indicates the user name associated with the session.
/netconf-session-start/source-host:
Indicates the source host address associated with the session.
/netconf-session-start:
Event type itself indicates that a NETCONF or other management
session may start altering the device configuration and/or state.
It may be possible for an attacker to alter the configuration by
somehow taking advantage of another session concurrently editing
an unlocked datastore.
/netconf-session-start/username:
Indicates the user name associated with the session.
/netconf-session-start/source-host:
Indicates the source host address associated with the session.
/netconf-session-end:
Event type itself indicates that a NETCONF or other management
session may be finished altering the device configuration. This
event could alert an attacker that a datastore may have been
altered.
/netconf-session-end/username:
Indicates the user name associated with the session.
/netconf-session-end/source-host:
Indicates the source host address associated with the session.
/netconf-session-end:
Event type itself indicates that a NETCONF or other management
session may be finished altering the device configuration. This
event could alert an attacker that a datastore may have been
altered.
/netconf-session-end/username:
Indicates the user name associated with the session.
/netconf-session-end/source-host:
Indicates the source host address associated with the session.
/netconf-confirmed-commit:
Event type itself indicates that the <running> datastore may have
changed. This event could alert an attacker that the device
behavior has changed.
/netconf-confirmed-commit/username:
Indicates the user name associated with the session.
/netconf-confirmed-commit/source-host:
Indicates the source host address associated with the session.
/netconf-confirmed-commit/confirm-event:
Indicates the specific confirmed-commit state change that
occurred. A value of 'complete' probably indicates that the
<running> datastore has changed.
/netconf-confirmed-commit/timeout:
Indicates the number of seconds in the future when the <running>
datastore may change, due to the server reverting to an older
configuration.
/netconf-confirmed-commit:
Event type itself indicates that the <running> datastore may have
changed. This event could alert an attacker that the device
behavior has changed.
/netconf-confirmed-commit/username:
Indicates the user name associated with the session.
/netconf-confirmed-commit/source-host:
Indicates the source host address associated with the session.
/netconf-confirmed-commit/confirm-event:
Indicates the specific confirmed-commit state change that
occurred. A value of 'complete' probably indicates that the
<running> datastore has changed.
/netconf-confirmed-commit/timeout:
Indicates the number of seconds in the future when the <running>
datastore may change, due to the server reverting to an older
configuration.
Thanks to Martin Bjorklund, Juergen Schoenwaelder, Kent Watsen, and many other members of the NETCONF WG for providing important input to this document.
感谢Martin Bjorklund、Juergen Schoenwaeld、Kent Watsen和NETCONF工作组的许多其他成员为本文件提供了重要的投入。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[RFC3688]Mealling，M.“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event Notifications", RFC 5277, July 2008.
[RFC5277]Chisholm，S.和H.Trevino，“NETCONF事件通知”，RFC 5277，2008年7月。
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010.
[RFC6020]Bjorklund，M.，Ed.“YANG-网络配置协议（NETCONF）的数据建模语言”，RFC6020，2010年10月。
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021, October 2010.
[RFC6021]Schoenwaeld，J.，Ed.，“常见的杨氏数据类型”，RFC 602112010年10月。
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011.
[RFC6241]Enns，R.，Ed.，Bjorklund，M.，Ed.，Schoenwaeld，J.，Ed.，和A.Bierman，Ed.“网络配置协议（NETCONF）”，RFC 62412011年6月。
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011.
[RFC6242]Wasserman，M.“在安全Shell（SSH）上使用NETCONF协议”，RFC6242，2011年6月。
Author's Address
作者地址
Andy Bierman Brocade
安迪·比尔曼·博科
EMail: andy@netconfcentral.org
EMail: andy@netconfcentral.org