draft-ietf-netconf-netconf-event-notifications-08.txt   draft-ietf-netconf-netconf-event-notifications-09.txt 
NETCONF A. Gonzalez Prieto NETCONF E. Voit
Internet-Draft VMware Internet-Draft Cisco Systems
Intended status: Standards Track E. Voit Intended status: Standards Track A. Clemm
Expires: August 26, 2018 Cisco Systems Expires: November 5, 2018 Huawei
A. Clemm A. Gonzalez Prieto
Huawei VMware
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
February 22, 2018 May 4, 2018
NETCONF Support for Event Notifications NETCONF Support for Event Notifications
draft-ietf-netconf-netconf-event-notifications-08 draft-ietf-netconf-netconf-event-notifications-09
Abstract Abstract
This document provides a NETCONF binding to subscribed notifications This document provides a NETCONF binding to subscribed notifications
and to YANG push. and to YANG push.
RFC Editor note: please replace the four references to pre-RFC RFC Editor note: please replace the four references to pre-RFC
normative drafts with the actual assigned RFC numbers. normative drafts with the actual assigned RFC numbers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 26, 2018. This Internet-Draft will expire on November 5, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 17 skipping to change at page 2, line 17
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Interleave Capability . . . . . . . . . . . . . . . . . . . . 3 3. Interleave Capability . . . . . . . . . . . . . . . . . . . . 3
4. Compatibility with RFC-5277's create-subscription . . . . . . 3 4. Compatibility with RFC-5277's create-subscription . . . . . . 3
5. Mandatory XML, stream and datastore support . . . . . . . . . 3 5. Mandatory XML, event stream and datastore support . . . . . . 4
6. Transport connectivity . . . . . . . . . . . . . . . . . . . 4 6. NETCONF connectivity and the subscription lifecycle . . . . . 4
6.1. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 4 6.1. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 4
6.2. Configured Subscriptions . . . . . . . . . . . . . . . . 4 6.2. Configured Subscriptions . . . . . . . . . . . . . . . . 4
7. Notification Messages . . . . . . . . . . . . . . . . . . . . 5 7. Notification Messages . . . . . . . . . . . . . . . . . . . . 5
8. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 5 8. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 5
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. YANG module . . . . . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. Normative References . . . . . . . . . . . . . . . . . . . . 6 11. Security Considerations . . . . . . . . . . . . . . . . . . . 8
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 7 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 7 13. Normative References . . . . . . . . . . . . . . . . . . . . 9
A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 8 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 10
A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 10
A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 11
A.3. Configured Subscriptions . . . . . . . . . . . . . . . . 15 A.3. Configured Subscriptions . . . . . . . . . . . . . . . . 15
A.4. Subscription State Notifications . . . . . . . . . . . . 20 A.4. Subscription State Notifications . . . . . . . . . . . . 20
Appendix B. Changes between revisions . . . . . . . . . . . . . 22 Appendix B. Changes between revisions . . . . . . . . . . . . . 22
B.1. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 22 B.1. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 22
B.2. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 22 B.2. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 22
B.3. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 22 B.3. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 22
B.4. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 22 B.4. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 22
B.5. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 23 B.5. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 23
B.6. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 23 B.6. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 23
B.7. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
This document provides a binding for events streamed over the NETCONF This document provides a binding for events streamed over the NETCONF
protocol [RFC6241] as per protocol [RFC6241] as per
[I-D.draft-ietf-netconf-subscribed-notifications]. In addition, as [I-D.draft-ietf-netconf-subscribed-notifications]. In addition, as
[I-D.ietf-netconf-yang-push] is itself built upon [I-D.ietf-netconf-yang-push] is itself built upon
[I-D.draft-ietf-netconf-subscribed-notifications], this document [I-D.draft-ietf-netconf-subscribed-notifications], this document
enables a NETCONF client to request and receive updates from a YANG enables a NETCONF client to request and receive updates from a YANG
datastore located on a NETCONF server. datastore located on a NETCONF server.
2. Terminology 2. 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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The following terms are defined in The following terms are defined in
[I-D.draft-ietf-netconf-subscribed-notifications]: notification [I-D.draft-ietf-netconf-subscribed-notifications]: notification
message, stream, publisher, receiver, subscriber, subscription, message, event stream, publisher, receiver, subscriber, subscription,
configured subscription. configured subscription.
3. Interleave Capability 3. Interleave Capability
To support multiple subscriptions on a single session, a NETCONF To support multiple subscriptions on a single session, a NETCONF
publisher MUST support the :interleave capability as defined in publisher MUST support the :interleave capability as defined in
[RFC5277]. Such support MUST be indicated by the following [RFC5277]. Advertisement of both the :interleave capability and
capability: "urn:ietf:params:netconf:capability:interleave:1.0".
Advertisement of both the :interleave capability and
"urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" within a "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" within a
NETCONF capability exchange MUST indicate that a NETCONF publisher is NETCONF capability exchange MUST indicate that a NETCONF publisher is
able to receive, process, and respond to NETCONF requests and able to receive, process, and respond to NETCONF requests and
[I-D.draft-ietf-netconf-subscribed-notifications] subscription [I-D.draft-ietf-netconf-subscribed-notifications] subscription
operations. operations.
4. Compatibility with RFC-5277's create-subscription 4. Compatibility with RFC-5277's create-subscription
A publisher is allowed to concurrently support both A publisher is allowed to concurrently support configured
[I-D.draft-ietf-netconf-subscribed-notifications] and [RFC5277]'s subscriptions and dynamic subscription RPCs of
"create-subscription" RPC, however this support MUST NOT happen on a [I-D.draft-ietf-netconf-subscribed-notifications] at the same time as
single transport NETCONF session. To accomplish this: [RFC5277]'s "create-subscription" RPC. However a single NETCONF
transport session cannot support both this specification and a
subscription established by [RFC5277]'s "create-subscription" RPC.
To protect against any attempts to use a single NETCONF transport
session in this way:
o A solution must reply with the [RFC6241] error "operation-not- o A solution must reply with the [RFC6241] error "operation-not-
supported" if a "create-subscription" RPC is received on a NETCONF supported" if a "create-subscription" RPC is received on a NETCONF
session where at least one subscription is currently active. session where any other
[I-D.draft-ietf-netconf-subscribed-notifications] or [RFC5277]
subscription exists.
o It is a prohibited to send updates or state change notifications o It is a prohibited to send updates or state change notifications
for a configured subscription on a NETCONF session where the for a configured subscription on a NETCONF session where the
create-subscription RPC has successfully created a subscription. create-subscription RPC has successfully [RFC5277] created
o A "create-subscription" RPC MUST be rejected if a subscription is subscription.
already active across that NETCONF transport session. o A "create-subscription" RPC MUST be rejected if any
[I-D.draft-ietf-netconf-subscribed-notifications] or
[RFC5277]subscription is active across that NETCONF transport
session.
5. Mandatory XML, stream and datastore support If a publisher supports this specification but not subscriptions via
[RFC5277], the publisher MUST NOT advertise
"urn:ietf:params:netconf:capability:notification:1.0".
A NETCONF publisher MUST support XML encoding of RPCs and 5. Mandatory XML, event stream and datastore support
Notifications.
A NETCONF publisher supporting The "encode-xml" feature of
[I-D.draft-ietf-netconf-subscribed-notifications] is mandatory to
support. This indicates that XML is a valid encoding for RPCs, state
change notifications, and subscribed content.
A NETCONF publisher supporting event stream subscription via
[I-D.draft-ietf-netconf-subscribed-notifications] MUST support the [I-D.draft-ietf-netconf-subscribed-notifications] MUST support the
"NETCONF" event stream identified in that draft. "NETCONF" event stream identified in that draft.
A NETCONF publisher supporting [I-D.ietf-netconf-yang-push] MUST A NETCONF publisher supporting [I-D.ietf-netconf-yang-push] MUST
support the operational state datastore as defined by support the operational state datastore as defined by
[I.D.draft-ietf-netmod-revised-datastores]. [I.D.draft-ietf-netmod-revised-datastores].
6. Transport connectivity 6. NETCONF connectivity and the subscription lifecycle
This section describes how the availability of NETCONF transport
impacts the establishment and lifecycle of different types of
[I-D.draft-ietf-netconf-subscribed-notifications] subscriptions.
6.1. Dynamic Subscriptions 6.1. Dynamic Subscriptions
For dynamic subscriptions, if the NETCONF session involved with the For dynamic subscriptions, if the NETCONF session involved with the
"establish-subscription" terminates, the subscription MUST be "establish-subscription" terminates, the subscription MUST be
deleted. deleted.
6.2. Configured Subscriptions 6.2. Configured Subscriptions
For a configured subscription, there is no guarantee a transport For a configured subscription, there is no guarantee a transport
session is currently in place with each associated receiver. In session is currently in place with each associated receiver. In
cases where a configured subscription has a receiver in the cases where a configured subscription has a receiver in the
connecting state and the protocol configured as NETCONF, but no CONNECTING state as described in
NETCONF transport session exists to that receiver, the publisher MUST [I-D.draft-ietf-netconf-subscribed-notifications], section 2.5.1, and
initiate a transport session via NETCONF call home [RFC8071], section the "transport" for that subscription is "NETCONF", but no NETCONF
4.1 to that receiver. Until NETCONF connectivity is established and transport session exists to that receiver (or all existing NETCONF
a subscription-started state change notification is successfully transport sessions are currently supporting [RFC5277] subscriptions),
sent, that receiver MUST remain in a status of either "connecting" or then the publisher MUST initiate a transport session via NETCONF call
"timeout". home [RFC8071], section 4.1 to that receiver. Until NETCONF
connectivity is established and a "subscription-started" state change
notification is successfully sent, that receiver MUST remain in
either the CONNECTING or the TIMEOUT state.
If the call home fails because the publisher receives receiver If the call home fails because the publisher receives receiver
credentials which are subsequently declined per [RFC8071], credentials which are subsequently declined per [RFC8071],
Section 4.1, step S5 authentication, then that receiver MUST be Section 4.1, step S5 authentication, then that receiver MUST be
assigned a "timeout" status. placed into the TIMEOUT state.
If the call home fails to establish for any other reason, the If the call home fails to establish for any other reason, the
publisher MUST NOT progress the receiver to the "active" state. publisher MUST NOT progress the receiver to the ACTIVE state.
Additionally, the publisher SHOULD place the receiver into a Additionally, the publisher SHOULD place the receiver into the
"timeout" status after a predetermined number of either failed call TIMEOUT state after a predetermined number of either failed call home
home attempts or NETCONF sessions remotely terminated by the attempts or NETCONF sessions remotely terminated by the receiver.
receiver.
NETCONF Transport session connectivity SHOULD be verified via NETCONF transport session connectivity SHOULD be verified via
Section 4.1, step S7. Section 4.1, step S7.
If an active NETCONF session is disconnected but the stop-time of a If a NETCONF session is disconnected but the "stop-time" of a
subscription has not been reached, the publisher MUST restart the subscription being transported over that session has not been
call home process and return the receiver to the "connecting" state. reached, the publisher restarts the call home process and return the
receiver to the CONNECTING state.
7. Notification Messages 7. Notification Messages
Notification messages transported over NETCONF will be identical in Notification messages transported over the NETCONF protocol will be
format and content to those encoded using one-way operations defined identical in format and content to those encoded using one-way
within [RFC5277], section 4. operations defined within [RFC5277], section 4.
8. Dynamic Subscriptions and RPC Error Responses 8. Dynamic Subscriptions and RPC Error Responses
Management of dynamic subscriptions occurs via RPCs as defined in Management of dynamic subscriptions occurs via RPCs as defined in
[I-D.ietf-netconf-yang-push] and [I-D.ietf-netconf-yang-push] and
[I-D.draft-ietf-netconf-subscribed-notifications]. When an RPC error [I-D.draft-ietf-netconf-subscribed-notifications]. When an RPC error
occurs, the NETCONF RPC reply MUST include an "rpc-error" element per occurs, the NETCONF RPC reply MUST include an "rpc-error" element per
[RFC6241] with the error information populated as follows: [RFC6241] with the error information populated as follows:
o "error-type" of "application". o an "error-type" node of "application".
o "error-tag" of "operation-failed". o an "error-tag" node of "operation-failed".
o Optionally, an "error-severity" of "error" (this MAY but does not o an "error-severity" of "error" (this MAY but does not have to be
have to be included). included).
o "error-app-tag" with the value being a string that corresponds to o an "error-app-tag" node with the value being a string that
an identity associated with the error, as defined in corresponds to an identity associated with the error, as defined
[I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6 in [I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6
for general subscriptions, and [I-D.ietf-netconf-yang-push] for general subscriptions, and [I-D.ietf-netconf-yang-push]
Appendix A.1, for datastore (YANG-Push) subscriptions. The tag to Appendix A.1, for datastore subscriptions. The tag to use depends
use depends on the RPC for which the error occurred. Applicable on the RPC for which the error occurred. Viable errors for
are identities with a base identity of "establish-subscription- different RPCs are as follows:
error" (for error responses to an establish-subscription request),
"modify- subscription-error" (for error responses to a modify-
subscription request), "delete-subscription-error" (for error
responses to a delete-subscription request), "resynch-
subscription-error" (for error responses to resynch-subscription
request), or "kill- subscription-error" (for error responses to a
kill-subscription request), respectively.
o In case of error responses to an establish-subscription or modify-
subscription request: optionally, "error-info" containing XML-
encoded data with hints regarding parameter settings that might
lead to successful requests in the future, per yang-data
definitions "establish-subscription-error-datastore" (for error
responses to an establish-subscription request) or "modify-
subscription-error-datastore (for error responses to a modify-
subscription request), respectively.
These yang-data that is included in "error-info" SHOULD NOT RPC use base identity
include the optional leaf "error-reason", as such a leaf would be ---------------------- ----------------------------
redundant with the information that is already placed within the establish-subscription establish-subscription-error
error-app-tag. modify-subscription modify-subscription-error
delete-subscription delete-subscription-error
kill-subscription kill-subscription-error
resynch-subscription resynch-subscription-error
In case of an rpc error as a result of a delete-subscription, or a o In case of error responses to an "establish-subscription" or
kill-subscription, or a resynch-subscription request, no error- "modify-subscription" request there is the option of including an
info needs to be included, as the subscription-id is the only RPC "error-info" node. This node may contain XML-encoded data with
input parameter and no hints regarding RPC input parameters need hints for parameter settings that might lead to successful RPC
to be provided. requests in the future. Following are the yang-data structures
which may be returned:
establish-subscription returns hints in yang-data structure
---------------------- ------------------------------------
target: event stream establish-subscription-stream-error-info
target: datastore establish-subscription-datastore-error-info
modify-subscription returns hints in yang-data structure
---------------------- ------------------------------------
target: event stream modify-subscription-stream-error-info
target: datastore modify-subscription-datastore-error-info
The yang-data included within "error-info" SHOULD NOT include the
optional leaf "error-reason", as such a leaf would be redundant
with information that is already placed within the
"error-app-tag".
In case of an rpc error as a result of a "delete-subscription", a
"kill-subscription", or a "resynch-subscription" request, no
"error-info" needs to be included, as the "subscription-id" is
the only RPC input parameter and no hints regarding this RPC input
parameters need to be provided.
Note that "error-path" does not need to be included with the "rpc- Note that "error-path" does not need to be included with the "rpc-
error" element, as subscription errors are generally not associated error" element, as subscription errors are generally not associated
with nodes in the datastore but with the choice of RPC input with nodes in the datastore but with the choice of RPC input
parameters. parameters.
9. Security Considerations 9. YANG module
This module references
[I-D.draft-ietf-netconf-subscribed-notifications].
[ note to the RFC Editor - please replace XXXX within this YANG model
with the number of this document ]
module ietf-netconf-subscribed-notifications {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-netconf-subscribed-notifications";
prefix nsn;
import ietf-subscribed-notifications {
prefix sn;
}
organization "IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http:/tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
Editor: Eric Voit
<mailto:evoit@cisco.com>
Editor: Alexander Clemm
<mailto:ludwig@clemm.org>
Editor: Alberto Gonzalez Prieto
<mailto:agonzalezpri@vmware.com>
Editor: Ambika Prasad Tripathy
<mailto:ambtripa@cisco.com>
Editor: Einar Nilsen-Nygaard
<mailto:einarnn@cisco.com>";
description
"Defines NETCONF as a supported transport for subscribed event
notifications.
Copyright (c) 2018 IETF Trust and the persons identified as authors
of the code. 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
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the RFC
itself for full legal notices.";
revision 2018-04-20 {
description
"Initial version";
reference
"RFC XXXX: NETCONF Support for Event Notifications";
}
identity netconf {
base sn:transport;
base sn:inline-address;
description
"NETCONF is used as a transport for notification messages and
state change notifications.";
}
}
10. IANA Considerations
This document registers the following namespace URI in the "IETF XML
Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-netconf-subscribed-
notifications
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
This document registers the following YANG module in the "YANG Module
Names" registry [RFC6020]:
Name: ietf-netconf-subscribed-notifications
Namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-subscribed-
notifications
Prefix: nsn
Reference: RFC XXXX: NETCONF Support for Event Notifications
11. Security Considerations
Notification messages (including state change notifications) are Notification messages (including state change notifications) are
never sent before the NETCONF capabilities exchange has completed. never sent before the NETCONF capabilities exchange has completed.
If a malicious or buggy NETCONF subscriber sends a number of If a malicious or buggy NETCONF subscriber sends a number of
"establish-subscription" requests, then these subscriptions establish-subscription requests, then these subscriptions accumulate
accumulate and may use up system resources. In such a situation, and may use up system resources. In such a situation, subscriptions
subscriptions MAY be terminated by terminating the underlying NETCONF MAY be terminated by terminating the underlying NETCONF session. The
session. The publisher MAY also suspend or terminate a subset of the publisher MAY also suspend or terminate a subset of the active
active subscriptions on that NETCONF session. subscriptions on that NETCONF session.
The NETCONF Authorization Control Model [rfc6536bis] SHOULD be used This draft does not define a YANG module and therefore doesn't have
to control and restrict authorization of subscription configuration. any YANG-related Security Considerations.
10. Acknowledgments 12. Acknowledgments
We wish to acknowledge the helpful contributions, comments, and We wish to acknowledge the helpful contributions, comments, and
suggestions that were received from: Andy Bierman, Yan Gang, Sharon suggestions that were received from: Andy Bierman, Yan Gang, Sharon
Chisholm, Hector Trevino, Peipei Guo, Susan Hares, Tim Jenkins, Chisholm, Hector Trevino, Peipei Guo, Susan Hares, Tim Jenkins,
Balazs Lengyel, Martin Bjorklund, Mahesh Jethanandani, Kent Watsen, Balazs Lengyel, Martin Bjorklund, Mahesh Jethanandani, Kent Watsen,
and Guangying Zheng. and Guangying Zheng.
11. Normative References 13. Normative References
[I-D.draft-ietf-netconf-subscribed-notifications] [I-D.draft-ietf-netconf-subscribed-notifications]
Voit, E., Clemm, A., Gonzalez Prieto, A., Tripathy, A., Voit, E., Clemm, A., Gonzalez Prieto, A., Tripathy, A.,
and E. Nilsen-Nygaard, "Custom Subscription to Event and E. Nilsen-Nygaard, "Customized Subscriptions to a
Streams", draft-ietf-netconf-subscribed-notifications-10 Publisher's Event Streams", draft-ietf-netconf-subscribed-
(work in progress), January 2018. notifications-11 (work in progress), April 2018.
[I-D.ietf-netconf-yang-push] [I-D.ietf-netconf-yang-push]
Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto., Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto.,
Tripathy, A., Nilsen-Nygaard, E., Bierman, A., and B. Tripathy, A., Nilsen-Nygaard, E., Bierman, A., and B.
Lengyel, "YANG Datastore Subscription", February 2018, Lengyel, "YANG Datastore Subscription", February 2018,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-yang-push/>. draft-ietf-netconf-yang-push/>.
[I.D.draft-ietf-netmod-revised-datastores] [I.D.draft-ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10 Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), January 2018. (work in progress), January 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event
Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008, Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008,
<https://www.rfc-editor.org/info/rfc5277>. <https://www.rfc-editor.org/info/rfc5277>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[rfc6536bis]
Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Module", December 2017,
<https://datatracker.ietf.org/doc/
draft-ietf-netconf-rfc6536bis/>.
[RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home", [RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
RFC 8071, DOI 10.17487/RFC8071, February 2017, RFC 8071, DOI 10.17487/RFC8071, February 2017,
<https://www.rfc-editor.org/info/rfc8071>. <https://www.rfc-editor.org/info/rfc8071>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Appendix A. Examples Appendix A. Examples
This section is non-normative.
A.1. Event Stream Discovery A.1. Event Stream Discovery
As defined in [I-D.draft-ietf-netconf-subscribed-notifications] an As defined in [I-D.draft-ietf-netconf-subscribed-notifications] an
event stream exposes a continuous set of events available for event stream exposes a continuous set of events available for
subscription. A NETCONF client can retrieve the list of available subscription. A NETCONF client can retrieve the list of available
event streams from a NETCONF publisher using the "get" operation event streams from a NETCONF publisher using the "get" operation
against the top-level container "/streams" defined in against the top-level container "/streams" defined in
[I-D.draft-ietf-netconf-subscribed-notifications]. [I-D.draft-ietf-netconf-subscribed-notifications] Section 3.1.
The following example illustrates the retrieval of the list of The following example illustrates the retrieval of the list of
available event streams using the "get" operation. available event streams:
<rpc message-id="101" <rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get> <get>
<filter type="subtree"> <filter type="subtree">
<streams <streams
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"/> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"/>
</filter> </filter>
</get> </get>
</rpc> </rpc>
Figure 1: Get streams request Figure 1: Get streams request
After such a request, the NETCONF publisher returns a list of event After such a request, the NETCONF publisher returns a list of event
streams available. streams available, as well as additional information which might
exist in the container.
A.2. Dynamic Subscriptions A.2. Dynamic Subscriptions
A.2.1. Establishing Dynamic Subscriptions A.2.1. Establishing Dynamic Subscriptions
The following figure shows two successful "establish-subscription" The following figure shows two successful "establish-subscription"
RPC requests as per RPC requests as per
[I-D.draft-ietf-netconf-subscribed-notifications]. The first request [I-D.draft-ietf-netconf-subscribed-notifications]. The first request
is given a subscription identifier of 22, the second, an identifier is given a subscription identifier of 22, the second, an identifier
of 23. of 23.
skipping to change at page 10, line 5 skipping to change at page 12, line 5
|<-----------------------------| |<-----------------------------|
| notification message (for 23)| | notification message (for 23)|
|<-----------------------------| |<-----------------------------|
| | | |
Figure 2: Multiple subscriptions over a NETCONF session Figure 2: Multiple subscriptions over a NETCONF session
To provide examples of the information being transported, example To provide examples of the information being transported, example
messages for interactions (a) and (b) in Figure 2 are detailed below: messages for interactions (a) and (b) in Figure 2 are detailed below:
<rpc netconf:message-id="102" <rpc message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <establish-subscription
<establish-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<stream> <stream>NETCONF</stream>
<name>NETCONF</name> <stream-xpath-filter xmlns:ex="http://example.com/events">
<xpath-filter xmlns:ex="http://example.com/events"> /ex:foo/
/ex:foo </stream-xpath-filter>
</xpath-filter> <dscp>10</dscp>
</stream> </establish-subscription>
<dscp> </rpc>
10
</dscp>
</establish-subscription>
</rpc>
Figure 3: establish-subscription request (a) Figure 3: establish-subscription request (a)
As NETCONF publisher was able to fully satisfy the request (a), the As NETCONF publisher was able to fully satisfy the request (a), the
publisher sends the subscription identifier of the accepted publisher sends the subscription identifier of the accepted
subscription within message (b): subscription within message (b):
<rpc-reply message-id="102" <rpc-reply message-id="102"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<identifier <identifier
skipping to change at page 11, line 5 skipping to change at page 12, line 38
</rpc-reply> </rpc-reply>
Figure 4: establish-subscription success (b) Figure 4: establish-subscription success (b)
If the NETCONF publisher had not been able to fully satisfy the If the NETCONF publisher had not been able to fully satisfy the
request, or subscriber has no authorization to establish the request, or subscriber has no authorization to establish the
subscription, the publisher would have sent an RPC error response. subscription, the publisher would have sent an RPC error response.
For instance, if the "dscp" value of 10 asserted by the subscriber in For instance, if the "dscp" value of 10 asserted by the subscriber in
Figure 3 proved unacceptable, the publisher may have returned: Figure 3 proved unacceptable, the publisher may have returned:
<rpc-reply message-id="102" <rpc-reply message-id="102"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error> <rpc-error>
<error-type>application</error-type> <error-type>application</error-type>
<error-tag>operation-failed</error-tag> <error-tag>operation-failed</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-app-tag> <error-app-tag>dscp-unavailable</error-app-tag>
dscp-unavailable </rpc-error>
</error-app-tag> </rpc-reply>
<error-info>
<establish-subscription-error-datastore
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<dscp>
100
</dscp>
</error-info>
</rpc-error>
</rpc-reply>
Figure 5: an unsuccessful establish subscription Figure 5: an unsuccessful establish subscription
The subscriber can use this information in future attempts to The subscriber can use this information in future attempts to
establish a subscription. establish a subscription.
A.2.2. Modifying Dynamic Subscriptions A.2.2. Modifying Dynamic Subscriptions
An existing subscription may be modified. The following exchange An existing subscription may be modified. The following exchange
shows a negotiation of such a modification via several exchanges shows a negotiation of such a modification via several exchanges
skipping to change at page 13, line 10 skipping to change at page 14, line 10
subscription as per [I-D.ietf-netconf-yang-push], the modification subscription as per [I-D.ietf-netconf-yang-push], the modification
request made in (c) may look like that shown in Figure 7. As can be request made in (c) may look like that shown in Figure 7. As can be
seen, the modifications being attempted are the application of a new seen, the modifications being attempted are the application of a new
xpath filter as well as the setting of a new periodic time interval. xpath filter as well as the setting of a new periodic time interval.
<rpc message-id="303" <rpc message-id="303"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<modify-subscription <modify-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"
xmlns:yp="urn:ietf:params:xml:ns:yang:ietf-yang-push"> xmlns:yp="urn:ietf:params:xml:ns:yang:ietf-yang-push">
<yp:datastore> <identifier>23</identifier>
<yp:xpath-filter xmlns="http://example.com/datastore"> <yp:datastore-xpath-filter xmlns="http://example.com/datastore">
/interfaces-state/interface/oper-status /interfaces-state/interface/oper-status
</yp:xpath-filter> </yp:datastore-xpath-filter>
<yp:periodic> <yp:periodic>
<yp:period>500</yp:period> <yp:period>500</yp:period>
</yp:periodic> </yp:periodic>
</yp:datastore>
<identifier>
23
</identifier>
</modify-subscription> </modify-subscription>
</rpc> </rpc>
Figure 7: Subscription modification request (c) Figure 7: Subscription modification request (c)
If the NETCONF publisher can satisfy both changes, the publisher If the NETCONF publisher can satisfy both changes, the publisher
sends a positive result for the RPC. If the NETCONF publisher cannot sends a positive result for the RPC. If the NETCONF publisher cannot
satisfy either of the proposed changes, the publisher sends an RPC satisfy either of the proposed changes, the publisher sends an RPC
error response (d). The following is an example RPC error response error response (d). The following is an example RPC error response
for (d) which includes a hint. This hint is an alternative time for (d) which includes a hint. This hint is an alternative time
period value which might have resulted in a successful modification: period value which might have resulted in a successful modification:
<rpc-reply message-id="303" <rpc-reply message-id="303"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error> <rpc-error>
<error-type>application</error-type> <error-type>application</error-type>
<error-tag>operation-failed</error-tag> <error-tag>operation-failed</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-app-tag> <error-app-tag>
period-unsupported period-unsupported
</error-message> </error-app-tag>
<error-info <error-info
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push"> xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push">
<modify-subscription-error-datastore> <modify-subscription-datastore-error-info>
<period-hint> <period-hint>
3000 3000
</period-hint> </period-hint>
</modify-subscription-error-datastore> </modify-subscription-datastore-error-info>
</error-info> </error-info>
</rpc-error> </rpc-error>
</rpc-reply> </rpc-reply>
Figure 8: Modify subscription failure with Hint (d) Figure 8: Modify subscription failure with Hint (d)
A.2.3. Deleting Dynamic Subscriptions A.2.3. Deleting Dynamic Subscriptions
The following demonstrates deleting a subscription. The following demonstrates deleting a subscription. This
subscription may have been to either a stream or a datastore.
<rpc message-id="103" <rpc message-id="103"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<delete-subscription <delete-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<identifier>22</identifier> <identifier>22</identifier>
</delete-subscription> </delete-subscription>
</rpc> </rpc>
Figure 9: Delete subscription Figure 9: Delete subscription
skipping to change at page 16, line 5 skipping to change at page 16, line 9
[I-D.draft-ietf-netconf-subscribed-notifications] or [I-D.draft-ietf-netconf-subscribed-notifications] or
[I-D.ietf-netconf-yang-push]. [I-D.ietf-netconf-yang-push].
In this section, we present examples of how to manage the In this section, we present examples of how to manage the
configuration subscriptions using a NETCONF client. configuration subscriptions using a NETCONF client.
A.3.1. Creating Configured Subscriptions A.3.1. Creating Configured Subscriptions
For subscription creation, a NETCONF client may send: For subscription creation, a NETCONF client may send:
<rpc message-id="201" <rpc message-id="201" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config> <edit-config>
<target> <target>
<running/> <running/>
</target> </target>
<subscriptions <default-operation>none</default-operation>
<config>
<subscriptions
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<subscription> <subscription>
<identifier>22</identifier> <identifier>1922</identifier>
<encoding>encode-xml</encoding> <transport xmlns:nsn=
<stream> "urn:ietf:params:xml:ns:yang:ietf-netconf-subscribed-notifications">
<name>NETCONF</name> nsn:netconf
<receiver> <transport>
<address>1.2.3.4</address> <stream>NETCONF</stream>
<port>1234</port> <receivers>
</receiver> <receiver>
</stream> <name>receiver1</name>
</subscription> <address>1.2.3.4</address>
</subscriptions> </receiver>
</receivers>
</subscription>
</subscriptions>
</config>
</edit-config> </edit-config>
</rpc> </rpc>
Figure 11: Create a configured subscription Figure 11: Create a configured subscription
If the request is accepted, the publisher will indicate this. If the If the request is accepted, the publisher will indicate this. If the
request is not accepted because the publisher cannot serve it, no request is not accepted because the publisher cannot serve it, no
configuration is changed. In this case the publisher may reply: configuration is changed. In this case the publisher may reply:
<rpc-reply message-id="201" <rpc-reply message-id="201"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error> <rpc-error>
<error-type>application</error-type> <error-type>application</error-type>
<error-tag>resource-denied</error-tag> <error-tag>resource-denied</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-message xml:lang="en"> <error-message xml:lang="en">
Temporarily the publisher cannot serve this Temporarily the publisher cannot serve this
subscription due to the current workload. subscription due to the current workload.
</error-message> </error-message>
</rpc-error> </rpc-error>
</rpc-reply> </rpc-reply>
Figure 12: Response to a failed configured subscription establishment Figure 12: Response to a failed configured subscription establishment
After a subscription has been created, NETCONF connectivity to each After a subscription has been created, NETCONF connectivity to each
receiver's IP address and port will be established if it does not receiver will be established if it does not already exist. This will
already exist. This will be accomplished via [RFC8071]. be accomplished via [RFC8071].
The following figure shows the interaction model for the successful The following figure shows the interaction model for the successful
creation of a configured subscription. creation of a configured subscription.
+----------+ +-----------+ +---------+ +----------+ +-----------+ +---------+
|Config Ops| | Publisher | | 1.2.3.4 | |Config Ops| | Publisher | | 1.2.3.4 |
+----------+ +-----------+ +---------+ +----------+ +-----------+ +---------+
| | | | | |
| Capability Exchange | | | Capability Exchange | |
|<-------------------------->| | |<-------------------------->| |
skipping to change at page 18, line 5 skipping to change at page 18, line 13
establishment establishment
A.3.2. Modifying Configured Subscriptions A.3.2. Modifying Configured Subscriptions
Configured subscriptions can be modified using configuration Configured subscriptions can be modified using configuration
operations against the top-level container "/subscriptions". operations against the top-level container "/subscriptions".
For example, the subscription established in the previous section For example, the subscription established in the previous section
could be modified as follows, here a adding a second receiver: could be modified as follows, here a adding a second receiver:
<rpc message-id="202" <rpc message-id="202" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" <edit-config>
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"> <target>
<edit-config> <running/>
<target> </target>
<running/> <config>
</target> <subscriptions
<subscriptions
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<subscription> <subscription>
<identifier> <identifier>
1922 1922
</identifier> </identifier>
<receiver> <receivers>
<address> <receiver>
1.2.3.5 <name>receiver2</name>
</address> <address>1.2.3.5</address>
<port> </receiver>
1234 </receivers>
</port> </subscription>
</receiver> </subscriptions>
</subscription> </config>
</subscriptions> </edit-config>
</edit-config> </rpc>
</rpc>
Figure 14: Modify configured subscription Figure 14: Modify configured subscription
If the request is accepted, the publisher will indicate success. The If the request is accepted, the publisher will indicate success. The
result is that the interaction model described in Figure 13 may be result is that the interaction model described in Figure 13 may be
extended as follows. extended as follows.
+----------+ +-----------+ +---------+ +---------+ +----------+ +-----------+ +---------+ +---------+
|Config Ops| | Publisher | | 1.2.3.4 | | 1.2.3.5 | |Config Ops| | Publisher | | 1.2.3.4 | | 1.2.3.5 |
+----------+ +-----------+ +---------+ +---------+ +----------+ +-----------+ +---------+ +---------+
skipping to change at page 21, line 5 skipping to change at page 21, line 5
A.4. Subscription State Notifications A.4. Subscription State Notifications
A publisher will send subscription state notifications according to A publisher will send subscription state notifications according to
the definitions within the definitions within
[I-D.draft-ietf-netconf-subscribed-notifications]). [I-D.draft-ietf-netconf-subscribed-notifications]).
A.4.1. subscription-started and subscription-modified A.4.1. subscription-started and subscription-modified
A "subscription-started" over NETCONF encoded in XML would look like: A "subscription-started" over NETCONF encoded in XML would look like:
<notification <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
xmlns=" urn:ietf:params:xml:ns:netconf:notification:1.0"> <eventTime>2007-09-01T10:00:00Z</eventTime>
<eventTime>2007-09-01T10:00:00Z</eventTime> <subscription-started
<subscription-started xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"/> <identifier>39</identifier>
<identifier>39</identifier> <transport xmlns:nsn=
<encoding>encode-xml</encoding> "urn:ietf:params:xml:ns:yang:ietf-netconf-subscribed-notifications">
<stream> nsn:netconf
<name>NETCONF</name> <transport>
<xpath-filter xmlns:ex="http://example.com/events"> <stream-xpath-filter xmlns:ex="http://example.com/events">
/ex:foo /ex:foo
</xpath-filter> </stream-xpath-filter>
</stream> <stream>NETCONF</stream>
</subscription-started> </subscription-started>
</notification> </notification>
Figure 17: subscription-started subscription state notification Figure 17: subscription-started subscription state notification
The "subscription-modified" is identical to Figure 17, with just the The "subscription-modified" is identical to Figure 17, with just the
word "started" being replaced by "modified". word "started" being replaced by "modified".
A.4.2. subscription-completed, subscription-resumed, and replay- A.4.2. subscription-completed, subscription-resumed, and replay-
complete complete
A "subscription-completed" would look like: A "subscription-completed" would look like:
skipping to change at page 21, line 44 skipping to change at page 21, line 44
<subscription-completed <subscription-completed
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<identifier>39</identifier> <identifier>39</identifier>
</subscription-completed> </subscription-completed>
</notification> </notification>
Figure 18: subscription-completed notification in XML Figure 18: subscription-completed notification in XML
The "subscription-resumed" and "replay-complete" are virtually The "subscription-resumed" and "replay-complete" are virtually
identical, with "subscription-completed" simply being replaced by identical, with "subscription-completed" simply being replaced by
"subscription-resumed" and "replay-complete" in both encodings. "subscription-resumed" and "replay-complete".
A.4.3. subscription-terminated and subscription-suspended A.4.3. subscription-terminated and subscription-suspended
A "subscription-terminated" would look like: A "subscription-terminated" would look like:
<notification <notification
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2007-09-01T10:00:00Z</eventTime> <eventTime>2007-09-01T10:00:00Z</eventTime>
<subscription-terminated <subscription-terminated
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
skipping to change at page 22, line 27 skipping to change at page 22, line 27
Figure 19: subscription-terminated subscription state notification Figure 19: subscription-terminated subscription state notification
The "subscription-suspended" is virtually identical, with The "subscription-suspended" is virtually identical, with
"subscription-terminated" simply being replaced by "subscription- "subscription-terminated" simply being replaced by "subscription-
suspended". suspended".
Appendix B. Changes between revisions Appendix B. Changes between revisions
(To be removed by RFC editor prior to publication) (To be removed by RFC editor prior to publication)
B.1. v07 to v08 B.1. v08 to v09
o Tweaks based on Kent's comments.
o Updated examples in Appendix A. And updates to some object names
based on changes in the subscribed-notifications draft.
o Added a YANG model for the NETCONF identity.
B.2. v07 to v08
o Tweaks and clarification on :interleave. o Tweaks and clarification on :interleave.
B.2. v06 to v07 B.3. v06 to v07
o XML encoding and operational datastore mandatory. o XML encoding and operational datastore mandatory.
o Error mechanisms and examples updated. o Error mechanisms and examples updated.
B.3. v05 to v06 B.4. v05 to v06
o Moved examples to appendices o Moved examples to appendices
o All examples rewritten based on namespace learnings o All examples rewritten based on namespace learnings
o Normative text consolidated in front o Normative text consolidated in front
o Removed all mention of JSON o Removed all mention of JSON
o Call home process detailed o Call home process detailed
o Note: this is a major revision attempting to cover those comments o Note: this is a major revision attempting to cover those comments
received from two week review. received from two week review.
B.4. v03 to v04 B.5. v03 to v04
o Added additional detail to "configured subscriptions" o Added additional detail to "configured subscriptions"
o Added interleave capability o Added interleave capability
o Adjusted terminology to that in draft-ietf-netconf-subscribed- o Adjusted terminology to that in draft-ietf-netconf-subscribed-
notifications notifications
o Corrected namespaces in examples o Corrected namespaces in examples
B.5. v01 to v03 B.6. v01 to v03
o Text simplifications throughout o Text simplifications throughout
o v02 had no meaningful changes o v02 had no meaningful changes
B.6. v00 to v01 B.7. v00 to v01
o Added Call Home in solution for configured subscriptions. o Added Call Home in solution for configured subscriptions.
o Clarified support for multiple subscription on a single session. o Clarified support for multiple subscription on a single session.
No need to support multiple create-subscription. No need to support multiple create-subscription.
o Added mapping between terminology in yang-push and [RFC6241] (the o Added mapping between terminology in yang-push and [RFC6241] (the
one followed in this document). one followed in this document).
o Editorial improvements. o Editorial improvements.
Authors' Addresses Authors' Addresses
Alberto Gonzalez Prieto
VMware
Email: agonzalezpri@vmware.com
Eric Voit Eric Voit
Cisco Systems Cisco Systems
Email: evoit@cisco.com Email: evoit@cisco.com
Alexander Clemm Alexander Clemm
Huawei Huawei
Email: ludwig@clemm.org Email: ludwig@clemm.org
Alberto Gonzalez Prieto
VMware
Email: agonzalezpri@vmware.com
Einar Nilsen-Nygaard Einar Nilsen-Nygaard
Cisco Systems Cisco Systems
Email: einarnn@cisco.com Email: einarnn@cisco.com
Ambika Prasad Tripathy Ambika Prasad Tripathy
Cisco Systems Cisco Systems
Email: ambtripa@cisco.com Email: ambtripa@cisco.com
 End of changes. 68 change blocks. 
246 lines changed or deleted 373 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/