Last Call Review for IETF NETCONF Event Notifications

The Internet Engineering Steering Group has received a request from
the Network Configuration Working Group (NETCONF) to consider the
"NETCONF Event Notifications" specification as an IETF Proposed
Standard. The IESG plans to make a decision in the next few weeks,
and solicits final comments on this action through 2008-01-29. This
memo defines a mechanism whereby the NETCONF client indicates
interest in receiving event notifications from a NETCONF server by
creating a subscription to receive event notifications. The NETCONF
server replies to indicate whether the subscription request was
successful and, if it was successful, begins sending the event
notifications to the NETCONF client as the events occur within the
system. These event notifications will continue to be sent until
either the NETCONF session is terminated or the subscription
terminates for some other reason. The event notification subscription
allows a number of options to enable the NETCONF client to specify
which events are of interest. These are specified when the subscription
is created. The motivation for this work is to enable the sending of
asynchronous messages that are consistent with the data model (content)
and security model used within a NETCONF implementation. The contents
of all event streams made available to a NETCONF client (i.e., the
notification sent by the NETCONF server) MUST be encoded in XML.
Section 4 presents the XML Schema for Event Notifications. An "event"
is something that happens which may be of interest -- a configuration
change, a fault, a change in status, crossing a threshold, or an
external input to the system, for example. Often this results in an
asynchronous message, sometimes referred to as a notification or
event notification, being sent to interested parties to notify them
that this event has occurred. A "subscription" is an agreement and
method to receive event notifications over a NETCONF session. A
concept related to the delivery of notifications (if there are any
to send) involving destination and selection of notifications; it
is bound to the lifetime of a session.