draft-ietf-netconf-netconf-event-notifications-06.txt   draft-ietf-netconf-netconf-event-notifications-07.txt 
NETCONF A. Gonzalez Prieto NETCONF A. Gonzalez Prieto
Internet-Draft VMware Internet-Draft VMware
Intended status: Standards Track E. Voit Intended status: Standards Track E. Voit
Expires: May 3, 2018 Cisco Systems Expires: August 12, 2018 Cisco Systems
A. Clemm A. Clemm
Huawei Huawei
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
October 30, 2017 February 8, 2018
NETCONF Support for Event Notifications NETCONF Support for Event Notifications
draft-ietf-netconf-netconf-event-notifications-06 draft-ietf-netconf-netconf-event-notifications-07
Abstract Abstract
This document provides a NETCONF binding for This document provides a NETCONF binding for
[I-D.draft-ietf-netconf-subscribed-notifications]. Included are: [I-D.draft-ietf-netconf-subscribed-notifications] and
[I-D.ietf-netconf-yang-push]. Included are:
o Transport mappings for subscription RPCs, state change
notifications, and notification messages
o Functionality which must be supported with NETCONF
o Examples in appendices o transport mappings for subscription RPCs, state change
notifications, and notification messages,
o functional requirements, and
o examples
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 May 3, 2018. This Internet-Draft will expire on August 12, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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. Mandatory stream and datastore support . . . . . . . . . . . 3 4. Mandatory XML, stream and datastore support . . . . . . . . . 3
5. Transport connectivity . . . . . . . . . . . . . . . . . . . 4 5. Transport connectivity . . . . . . . . . . . . . . . . . . . 3
5.1. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 4 5.1. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 3
5.2. Configured Subscriptions . . . . . . . . . . . . . . . . 4 5.2. Configured Subscriptions . . . . . . . . . . . . . . . . 4
6. Notification Messages . . . . . . . . . . . . . . . . . . . . 4 6. Notification Messages . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 7. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 4
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 5 10. Normative References . . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 7
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 6 A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 7
A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 6
A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 7 A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 7
A.3. Configured Subscriptions . . . . . . . . . . . . . . . . 12 A.3. Configured Subscriptions . . . . . . . . . . . . . . . . 14
A.4. Subscription State Notifications . . . . . . . . . . . . 17 A.4. Subscription State Notifications . . . . . . . . . . . . 19
Appendix B. Changes between revisions . . . . . . . . . . . . . 19 Appendix B. Changes between revisions . . . . . . . . . . . . . 21
B.1. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 19 B.1. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 21
B.2. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 19 B.2. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 21
B.3. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 20 B.3. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 21
B.4. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 20 B.4. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 B.5. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
This document defines a binding for notification message delivery for This document defines a binding for events streamed over the NETCONF
[I-D.draft-ietf-netconf-subscribed-notifications] transported over protocol [RFC6241] as per
the NETCONF protocol [RFC6241]. 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 maintain a subset/extract of an actively enables a NETCONF client to request and receive updates from a YANG
changing YANG datastore located on a NETCONF server. datastore located on a NETCONF server.
This document is broken into two main parts. The first contains
normative requirements which are incremental to
[I-D.draft-ietf-netconf-subscribed-notifications] when NETCONF
transport is used. The second are examples and are included as
appendices.
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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, stream, publisher, receiver, subscriber, subscription,
skipping to change at page 3, line 39 skipping to change at page 3, line 29
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]. Such support MUST be indicated by the following
capability: "urn:ietf:params:netconf:capability:interleave:1.0". capability: "urn:ietf:params:netconf:capability:interleave:1.0".
Advertisement of this capability along with support Advertisement of this capability along with support
[I-D.draft-ietf-netconf-subscribed-notifications] will indicate that [I-D.draft-ietf-netconf-subscribed-notifications] will indicate that
a NETCONF publisher is able to receive, process, and respond to a NETCONF publisher is able to receive, process, and respond to
NETCONF requests and NETCONF requests and
[I-D.draft-ietf-netconf-subscribed-notifications] subscription [I-D.draft-ietf-netconf-subscribed-notifications] subscription
operations on a session with active subscriptions. operations on a session with active subscriptions.
4. Mandatory stream and datastore support 4. Mandatory XML, stream and datastore support
A NETCONF publisher MUST support XML encoding of RPCs and
Notifications.
A NETCONF publisher supporting A NETCONF publisher supporting
[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 "running" 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].
5. Transport connectivity 5. Transport connectivity
5.1. Dynamic Subscriptions 5.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.
5.2. Configured Subscriptions 5.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 associated receiver(s). So where session is currently in place with each associated receiver. In
a configured subscription has a receiver in the connecting state, but cases where a configured subscription has a receiver in the
no NETCONF transport exists to that receiver, the publisher MUST be connecting state and the protocol configured as NETCONF, but no
able to initiate a NETCONF transport session via NETCONF call home NETCONF transport session exists to that receiver, the publisher MUST
[RFC8071], section 4.1 to that receiver. Until NETCONF connectivity initiate a transport session via NETCONF call home [RFC8071], section
is established and a subscription-started state change notification 4.1 to that receiver. Until NETCONF connectivity is established and
is successfully sent, that receiver MUST remain in its status of a a subscription-started state change notification is successfully
"connecting". sent, that receiver MUST remain in a status of either "connecting" or
"timeout".
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 as part [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 "suspended" status. assigned a "timeout" status.
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 MAY leave the receiver in a "connecting" status, and retry publisher MUST NOT progress the receiver to the "active" state.
the call home at a future time. Alternatively, the publisher MAY Additionally, the publisher SHOULD place the receiver into a
place the receiver into a "suspended" status after a predetermined "timeout" status after a predetermined number of either failed call
number of call home attempts. home attempts or NETCONF sessions remotely terminated by the
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.
Failure of an active NETCONF session MUST reset the restart the call If an active NETCONF session is disconnected but the stop-time of a
home process, and return the receiver to "connecting". subscription has not been reached, the publisher MUST restart the
call home process and return the receiver to the "connecting" state.
6. Notification Messages 6. Notification Messages
Notification messages transported over NETCONF will be identical in Notification messages transported over NETCONF will be identical in
format and content to those encoded using one-way operations defined format and content to those encoded using one-way operations defined
within [RFC5277], section 4. within [RFC5277], section 4.
7. Security Considerations 7. Dynamic Subscriptions and RPC Error Responses
Management of dynamic subscriptions occurs via RPCs as defined in
[I-D.ietf-netconf-yang-push] and
[I-D.draft-ietf-netconf-subscribed-notifications]. When an RPC error
occurs, the NETCONF RPC reply MUST include an "rpc-error" element per
[RFC6241] with the error information populated as follows:
o "error-type" of "application".
o "error-tag" of "operation-failed".
o Optionally, an "error-severity" of "error" (this MAY but does not
have to be included).
o "error-app-tag" with the value being a string that corresponds to
an identity associated with the error, as defined in
[I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6
for general subscriptions, and [I-D.ietf-netconf-yang-push]
Appendix A.1, for datastore (YANG-Push) subscriptions. The tag to
use depends on the RPC for which the error occurred. Applicable
are identities with a base identity of "establish-subscription-
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
include the optional leaf "error-reason", as such a leaf would be
redundant with the information that is already placed within the
error-app-tag.
In case of an rpc error as a result of a delete-subscription, or 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 RPC input parameters need
to be provided.
Note that "error-path" does not need to be included with the "rpc-
error" element, as subscription errors are generally not associated
with nodes in the datastore but with the choice of RPC input
parameters.
8. 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 and may use up system resources. In such a situation, accumulate and may use up system resources. In such a situation,
subscriptions MAY be terminated by terminating the suspect underlying subscriptions MAY be terminated by terminating the underlying NETCONF
NETCONF sessions. The publisher MAY also suspend or terminate a session. The publisher MAY also suspend or terminate a subset of the
subset of the active subscriptions on the NETCONF session. active subscriptions on that NETCONF session.
The NETCONF Authorization Control Model [RFC6536] SHOULD be used to The NETCONF Authorization Control Model [RFC6536] SHOULD be used to
control and restrict authorization of subscription configuration. control and restrict authorization of subscription configuration.
8. Acknowledgments 9. 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, Kent Watsen, and Guangying Zheng. Balazs Lengyel, Kent Watsen, and Guangying Zheng.
9. References 10. Normative References
9.1. 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, "Custom Subscription to Event
Streams", draft-ietf-netconf-subscribed-notifications-06 Streams", draft-ietf-netconf-subscribed-notifications-10
(work in progress), October 2017. (work in progress), January 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", October 2017, 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-04 Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), August 2017. (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>.
[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>.
skipping to change at page 6, line 19 skipping to change at page 7, line 19
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
[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>.
9.2. Informative References
[I.D.draft-ietf-netconf-notification-messages]
Voit, Eric., Clemm, Alexander., Bierman, A., and T.
Jenkins, "YANG Notification Headers and Bundles",
September 2017, <https://datatracker.ietf.org/doc/
draft-ietf-netconf-notification-messages>.
Appendix A. Examples Appendix A. Examples
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]. Any reply will [I-D.draft-ietf-netconf-subscribed-notifications].
include the stream identities supported on the NETCONF publisher
which may be available to that client.
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 using the "get" operation.
<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. In the example reply below, the list contains streams available.
just the NETCONF stream.
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<streams
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<name>NETCONF</name>
</streams>
</data>
</rpc-reply>
Figure 2: Get streams response
A.2. Dynamic Subscriptions A.2. Dynamic Subscriptions
A.2.1. Establishing Dynamic Subscriptions
The dynamic subscription RPCs and interactions operation are defined The following figure shows two successful "establish-subscription"
in [I-D.draft-ietf-netconf-subscribed-notifications] and enhanced in RPC requests as per
[I-D.ietf-netconf-yang-push]. [I-D.draft-ietf-netconf-subscribed-notifications]. The first request
is given a subscription identifier of 22, the second, an identifier
of 23.
A.2.1. Establishing Dynamic Subscriptions +------------+ +-----------+
| Subscriber | | Publisher |
+------------+ +-----------+
| |
| Capability Exchange |
|<---------------------------->|
| |
| |
| establish-subscription |
|----------------------------->| (a)
| RPC Reply: OK, id = 22 |
|<-----------------------------| (b)
| |
| notification message (for 22)|
|<-----------------------------|
| |
| |
| establish-subscription |
|----------------------------->|
| RPC Reply: OK, id = 23 |
|<-----------------------------|
| |
| |
| notification message (for 22)|
|<-----------------------------|
| notification message (for 23)|
|<-----------------------------|
| |
An example of establish-subscription interactions over NETCONF Figure 2: Multiple subscriptions over a NETCONF session
transport for a sample subscription is described below:
To provide examples of the information being transported, example
messages for interactions (a) and (b) in Figure 2 are detailed below:
<rpc netconf:message-id="102" <rpc netconf: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>
<name>NETCONF</name> <name>NETCONF</name>
<xpath-filter xmlns:ex="http://example.com/events"> <xpath-filter xmlns:ex="http://example.com/events">
/ex:foo /ex:foo
</xpath-filter> </xpath-filter>
</stream> </stream>
<dscp>
10
</dscp>
</establish-subscription> </establish-subscription>
</rpc> </rpc>
Figure 3: establish-subscription over NETCONF Figure 3: establish-subscription request (a)
If the NETCONF publisher can satisfy the request, the publisher sends As NETCONF publisher was able to fully satisfy the request (a), the
a positive "subscription-result" element, and the subscription-id of publisher sends the subscription identifier of the accepted
the accepted subscription. subscription within message (b):
<rpc-reply message-id="102"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<identifier
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
22
</identifier>
</rpc-reply>
Figure 4: establish-subscription success (b)
If the NETCONF publisher had not been able to fully satisfy the
request, or subscriber has no authorization to establish the
subscription, the publisher would have sent an RPC error response.
For instance, if the "dscp" value of 10 asserted by the subscriber in
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">
<subscription-result <rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-app-tag>
dscp-unavailable
</error-app-tag>
<error-info>
<establish-subscription-error-datastore
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
ok <dscp>
</subscription-result> 100
<identifier </dscp>
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> </error-info>
22 </rpc-error>
</identifier>
</rpc-reply> </rpc-reply>
Figure 4: Successful establish-subscription Figure 5: an unsuccessful establish subscription
If the NETCONF publisher cannot satisfy the request, or subscriber
has no authorization to establish the subscription, the publisher
will send a negative "subscription-result" element. For instance:
<rpc-reply message-id="101" The subscriber can use this information in future attempts to
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> establish a subscription.
<subscription-result
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
stream-unavailable
</subscription-result>
</rpc-reply>
Figure 5: Unsuccessful establish subscription A.2.2. Modifying Dynamic Subscriptions
To get an idea of the interaction model, the following figure shows An existing subscription may be modified. The following exchange
two separate establish subscriptions RPC being made. The first is shows a negotiation of such a modification via several exchanges
given subscription id 22, the second, id 23. between a subscriber and a publisher. This negotiation consists of a
failed RPC modification request/response, followed by a successful
one.
+------------+ +-----------+ +------------+ +-----------+
| Subscriber | | Publisher | | Subscriber | | Publisher |
+------------+ +-----------+ +------------+ +-----------+
| | | |
| Capability Exchange | | notification message (for 23)|
|<---------------------------->|
| |
| |
| Establish Subscription |
|----------------------------->|
| RPC Reply: OK, id = 22 |
|<-----------------------------|
| |
| notification message (for 22)|
|<-----------------------------| |<-----------------------------|
| | | |
| modify-subscription (id = 23)|
|----------------------------->| (c)
| RPC error (with hint) |
|<-----------------------------| (d)
| | | |
| Establish Subscription | | modify-subscription (id = 23)|
|----------------------------->| |----------------------------->|
| RPC Reply: OK, id = 23 | | RPC Reply: OK |
|<-----------------------------| |<-----------------------------|
| | | |
| |
| notification message (for 22)|
|<-----------------------------|
| notification message (for 23)| | notification message (for 23)|
|<-----------------------------| |<-----------------------------|
| | | |
Figure 6: Multiple subscription establishments over a single NETCONF Figure 6: Interaction model for successful subscription modification
session
In the example above, it is important to note that the subscription
ids of 22 and 23 are not included in the notification messages of
[I-D.draft-ietf-netconf-subscribed-notifications]. However because
[I-D.ietf-netconf-yang-push] has defined its own notifications,
subscription identifiers are available within those notification
messages. With the availability of
[I.D.draft-ietf-netconf-notification-messages], all notification
messages will be able to transport a subscription identifier.
A.2.2. Modifying Dynamic Subscriptions
The following demonstrates modifying a dynamic subscription. If the subscription being modified in Figure 6 is a datastore
Consider a subscription from [I-D.ietf-netconf-yang-push]. An subscription as per [I-D.ietf-netconf-yang-push], the modification
established may have a new filter applied. The desired modification request made in (c) may look like that shown in Figure 7. As can be
is the application of a new filter. seen, the modifications being attempted are the application of a new
xpath filter as well as the setting of a new periodic time interval.
<rpc message-id="102" <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> <yp:datastore>
<yp:xpath-filter xmlns="http://example.com/datastore"> <yp:xpath-filter xmlns="http://example.com/datastore">
/interfaces-state/interface/oper-status /interfaces-state/interface/oper-status
</yp:xpath-filter> </yp:xpath-filter>
<yp:periodic>
<yp:period>500</yp:period>
</yp:periodic>
</yp:datastore> </yp:datastore>
<identifier> <identifier>
22 23
</identifier> </identifier>
</modify-subscription> </modify-subscription>
</rpc> </rpc>
Figure 7: Subscription modification Figure 7: Subscription modification request (c)
If the NETCONF publisher can satisfy the request, the publisher sends
a positive "subscription-result". This response is like that to an
establish-subscription request, but without the subscription
identifier.
<rpc-reply message-id="102"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<subscription-result
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
ok
</subscription-result>
</rpc-reply>
Figure 8: Successful modify-subscription
If the NETCONF publisher cannot satisfy the request, the publisher
sends a negative "subscription-result" element. Its contents and
semantics match those from an establish-subscription request.
To get an idea of the interaction model, the following figure shows a If the NETCONF publisher can satisfy both changes, the publisher
successful RPC modification request to subscription with an sends a positive result for the RPC. If the NETCONF publisher cannot
identifier of 22. satisfy either of the proposed changes, the publisher sends an RPC
error response (d). The following is an example RPC error response
for (d) which includes a hint. This hint is an alternative time
period value which might have resulted in a successful modification:
+------------+ +-----------+ <rpc-reply message-id="303"
| Subscriber | | Publisher | xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
+------------+ +-----------+ <rpc-error>
| | <error-type>application</error-type>
| notification message | <error-tag>operation-failed</error-tag>
|<-----------------------------| <error-severity>error</error-severity>
| | <error-app-tag>
| Modify Subscription | period-unsupported
|----------------------------->| </error-message>
| RPC Reply: OK | <error-info
|<-----------------------------| xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push">
| | <modify-subscription-error-datastore>
| notification message | <period-hint>
|<-----------------------------| 3000
| | </period-hint>
</modify-subscription-error-datastore>
</error-info>
</rpc-error>
</rpc-reply>
Figure 9: Interaction model for successful subscription modification 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.
<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 10: Delete subscription Figure 9: Delete subscription
If the NETCONF publisher can satisfy the request, the publisher sends
an OK element. For example:
<rpc-reply message-id="103"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Figure 11: Successful delete subscription If the NETCONF publisher can satisfy the request, the publisher
replies with success to the RPC request.
If the NETCONF publisher cannot satisfy the request, the publisher If the NETCONF publisher cannot satisfy the request, the publisher
sends an error-rpc element indicating the modification didn't work. sends an error-rpc element indicating the modification didn't work.
One way this could happen is if an existing valid subscription Figure 10 shows a valid response for existing valid subscription
identifier was given, but that subscription was created on a identifier, but that subscription identifier was created on a
different NETCONF transport session: different NETCONF transport session:
<rpc-reply message-id="103" <rpc-reply message-id="103"
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>invalid-value</error-tag> <error-tag>operation-failed</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-path <error-app-tag>
xmlns:sn="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> no-such-subscription
sn:identifier </error-app-tag>
</error-path> </rpc-error>
<error-message xml:lang="en"> </rpc-reply>
no-such-subscription
</error-message>
</rpc-error>
</rpc-reply>
Figure 12: Unsuccessful delete subscription Figure 10: Unsuccessful delete subscription
A.3. Configured Subscriptions A.3. Configured Subscriptions
Configured subscriptions may be established, modified, and deleted Configured subscriptions may be established, modified, and deleted
using configuration operations against the top-level subtree of using configuration operations against the top-level subtree of
[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. Key differences configuration subscriptions using a NETCONF client.
from dynamic subscriptions over NETCONF is that subscription
lifetimes are decoupled from NETCONF sessions.
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"> xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config> <edit-config>
<target> <target>
<running/> <running/>
</target> </target>
<subscription-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>22</identifier>
<encoding>encode-xml</encoding> <encoding>encode-xml</encoding>
<stream> <stream>
<name>NETCONF</name> <name>NETCONF</name>
<receiver> <receiver>
<address>1.2.3.4</address> <address>1.2.3.4</address>
<port>1234</port> <port>1234</port>
</receiver> </receiver>
</stream> </stream>
</subscription> </subscription>
</subscription-config> </subscriptions>
</edit-config> </edit-config>
</rpc> </rpc>
Figure 13: Create a configured subscription Figure 11: Create a configured subscription
If the request is accepted, the publisher would reply:
<rpc-reply message-id="201"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Figure 14: Response to a successful configuration subscription
establishment
If the request is not accepted because the publisher cannot serve it, If the request is accepted, the publisher will indicate this. If the
no configuration is changed. In this case the publisher may reply: request is not accepted because the publisher cannot serve it, no
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 15: 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's IP address and port will be established if it does not
already exist. This will be accomplished via [RFC8071]. already exist. This will be accomplished via [RFC8071].
To get an idea of the interaction model, the following figure shows a The following figure shows the interaction model for the successful
successful configuration based creation of a subscription. creation of a configured subscription.
+----------+ +-----------+ +---------+ +----------+ +-----------+ +---------+
|Config Ops| | Publisher | | 1.2.3.4 | |Config Ops| | Publisher | | 1.2.3.4 |
+----------+ +-----------+ +---------+ +----------+ +-----------+ +---------+
| | | | | |
| Capability Exchange | | | Capability Exchange | |
|<-------------------------->| | |<-------------------------->| |
| | | | | |
| | | | | |
| Edit-config | | | Edit-config | |
|--------------------------->| | |--------------------------->| |
| RPC Reply: OK | | | RPC Reply: OK | |
|<---------------------------| | |<---------------------------| |
| | Call Home | | | Call Home |
| |<-------------->| | |<-------------->|
| | | | | |
| | Subscription | | | subscription- |
| | Started | | | started |
| |--------------->| | |--------------->|
| | | | | |
| | notification | | | notification |
| | message | | | message |
| |--------------->| | |--------------->|
Figure 16: Interaction model for configured subscription Figure 13: Interaction model for configured subscription
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 subtree subscription-config. 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"
xmlns:nc="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>
<subscription-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> <identifier>
1922 1922
</identifier> </identifier>
<receiver> <receiver>
<address> <address>
1.2.3.5 1.2.3.5
</address> </address>
<port> <port>
1234 1234
</port> </port>
</receiver> </receiver>
</subscription> </subscription>
</subscription-config> </subscriptions>
</edit-config> </edit-config>
</rpc> </rpc>
Figure 17: Modify configured subscription Figure 14: Modify configured subscription
If the request is accepted, the publisher would reply:
<rpc-reply message-id="202"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Figure 18: A successful configured subscription modification
And the previous interaction model would be extended as follows. If the request is accepted, the publisher will indicate success. The
result is that the interaction model described in Figure 13 may be
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 |
+----------+ +-----------+ +---------+ +---------+ +----------+ +-----------+ +---------+ +---------+
| | | |
| | | |
| | notification | | | | notification | |
| | message | | | | message | |
| |--------------->| | | |--------------->| |
| | | |
| Edit-config | | | | Edit-config | | |
|--------------------------->| | | |--------------------------->| | |
| RPC Reply: OK | | | | RPC Reply: OK | | |
|<---------------------------| | | |<---------------------------| | |
| | Call Home | | | | subscription- | |
| |<--------------------------->| | | started | |
| | Subscription | |
| | Started | |
| |---------------------------->| | |---------------------------->|
| | | | | | | |
| | notification | | | | notification | |
| | message | | | | message | |
| |--------------->| | | |--------------->| |
| |---------------------------->| | |---------------------------->|
| | | | | | | |
Figure 19: Interaction model for configured subscription modification Figure 15: Interaction model for configured subscription modification
Note in the above that in the specific example above, modifying a Note in the above that in the specific example above, modifying a
configured subscription actually resulted in subscription-started configured subscription actually resulted in "subscription-started"
notification. If the edit of the configuration had also added a notification. And because of an existing NETCONF session, no
filter, a separate modify-subscription would have gone to the additional call home was needed. Also note that if the edit of the
original receiver. configuration had impacted the filter, a separate modify-subscription
would have been required for the original receiver.
A.3.3. Deleting Configured Subscriptions A.3.3. Deleting Configured Subscriptions
Configured subscriptions can be deleted using configuration Configured subscriptions can be deleted using configuration
operations against the top-level subtree subscription-config. operations against the top-level container "/subscriptions".
Deleting the subscription above would result in the following flow Deleting the subscription above would result in the following flow
impacting all receivers. impacting all active receivers.
+----------+ +-----------+ +---------+ +---------+ +----------+ +-----------+ +---------+ +---------+
|Config Ops| | Publisher | | 1.2.3.4 | | 1.2.3.5 | |Config Ops| | Publisher | | 1.2.3.4 | | 1.2.3.5 |
+----------+ +-----------+ +---------+ +---------+ +----------+ +-----------+ +---------+ +---------+
| | | | | | | |
| | notification | | | | notification | |
| | message | | | | message | |
| |--------------->| | | |--------------->| |
| |---------------------------->| | |---------------------------->|
| | | | | | | |
| Edit-config | | | | Edit-config | | |
|--------------------------->| | | |--------------------------->| | |
| RPC Reply: OK | | | | RPC Reply: OK | | |
|<---------------------------| | | |<---------------------------| | |
| | Subscription | | | | subscription- | |
| | Terminated | | | | terminated | |
| |--------------->| | | |--------------->| |
| |---------------------------->| | |---------------------------->|
| | | | | | | |
Figure 20: Interaction model for configured subscription deletion Figure 16: Interaction model for configured subscription deletion
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>
<encoding>encode-xml</encoding> <encoding>encode-xml</encoding>
<stream> <stream>
<name>NETCONF</name> <name>NETCONF</name>
<xpath-filter xmlns:ex="http://example.com/events"> <xpath-filter xmlns:ex="http://example.com/events">
/ex:foo /ex:foo
</xpath-filter> </xpath-filter>
</stream> </stream>
</subscription-started/> </subscription-started>
</notification> </notification>
Figure 21: subscription-started subscription state notification Figure 17: subscription-started subscription state notification
The subscription-modified is identical, with just the word "started" The "subscription-modified" is identical to Figure 17, with just the
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:
<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-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 22: subscription-completed notification in XML Figure 18: subscription-completed notification in XML
The subscription-resumed and replay-complete are virtually identical, The "subscription-resumed" and "replay-complete" are virtually
with "subscription-completed" simply being replaced by "subscription- identical, with "subscription-completed" simply being replaced by
resumed" and "replay-complete" in both encodings. "subscription-resumed" and "replay-complete" in both encodings.
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">
<identifier>39</identifier> <identifier>39</identifier>
<error-id> <error-id>
unsupportable-volume suspension-timeout
</error-id> </error-id>
</subscription-terminated> </subscription-terminated>
</notification> </notification>
Figure 23: 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. v05 to v06 B.1. v06 to v07
o Moved examples to appendices o XML encoding and operational datastore mandatory.
o Error mechanisms and examples updated.
o All examples rewritten based on namespace learnings B.2. v05 to v06
o Moved examples to appendices
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.2. v03 to v04 B.3. 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.3. v01 to v03 B.4. v01 to v03
o Text simplifications throughout o Text simplifications throughout
o v02 had no meaningful changes o v02 had no meaningful changes
B.4. v00 to v01 B.5. 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 Alberto Gonzalez Prieto
VMware VMware
Email: agonzalezpri@vmware.com Email: agonzalezpri@vmware.com
Eric Voit Eric Voit
 End of changes. 114 change blocks. 
318 lines changed or deleted 326 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/