draft-ietf-netconf-netconf-event-notifications-16.txt   draft-ietf-netconf-netconf-event-notifications-17.txt 
NETCONF E. Voit NETCONF E. Voit
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track A. Clemm Intended status: Standards Track A. Clemm
Expires: July 12, 2019 Huawei Expires: August 17, 2019 Huawei
A. Gonzalez Prieto A. Gonzalez Prieto
Microsoft Microsoft
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
January 8, 2019 February 13, 2019
Dynamic subscription to YANG Events and Datastores over NETCONF Dynamic subscription to YANG Events and Datastores over NETCONF
draft-ietf-netconf-netconf-event-notifications-16 draft-ietf-netconf-netconf-event-notifications-17
Abstract Abstract
This document provides a NETCONF binding to the dynamic subscription This document provides a NETCONF binding to the dynamic subscription
capability of both subscribed notifications and YANG push. capability of both subscribed notifications and 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
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 July 12, 2019. This Internet-Draft will expire on August 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Compatibility with RFC-5277's create-subscription . . . . . . 3 3. Compatibility with RFC-5277's create-subscription . . . . . . 3
4. Mandatory XML, event stream and datastore support . . . . . . 4 4. Mandatory XML, event stream and datastore support . . . . . . 4
5. NETCONF connectivity and the Dynamic Subscriptions . . . . . 4 5. NETCONF connectivity and the Dynamic Subscriptions . . . . . 4
6. Notification Messages . . . . . . . . . . . . . . . . . . . . 4 6. Notification Messages . . . . . . . . . . . . . . . . . . . . 4
7. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 4 7. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 4
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
11. Notes to the RFC Editor . . . . . . . . . . . . . . . . . . . 6 11. Notes to the RFC Editor . . . . . . . . . . . . . . . . . . . 7
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
12.1. Normative References . . . . . . . . . . . . . . . . . . 7 12.1. Normative References . . . . . . . . . . . . . . . . . . 7
12.2. Informative References . . . . . . . . . . . . . . . . . 7 12.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 8
A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 8 A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 8
A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 8 A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 9
A.3. Subscription State Notifications . . . . . . . . . . . . 13 A.3. Subscription State Notifications . . . . . . . . . . . . 14
A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 14 A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Changes between revisions . . . . . . . . . . . . . 16 Appendix B. Changes between revisions . . . . . . . . . . . . . 17
B.1. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 16 B.1. v16 to v17 . . . . . . . . . . . . . . . . . . . . . . . 17
B.2. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 16 B.2. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 17
B.3. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 16 B.3. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 17
B.4. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 16 B.4. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 17
B.5. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 16 B.5. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 17
B.6. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 17 B.6. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 18
B.7. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 17 B.7. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 18
B.8. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 17 B.8. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 18
B.9. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 17 B.9. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 18
B.10. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 17 B.10. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 18
B.11. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 17 B.11. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 18
B.12. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 17 B.12. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 18
B.13. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 18 B.13. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 B.14. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
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] for dynamic subscriptions as defined in protocol [RFC6241] for dynamic subscriptions as defined in
[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 via a dynamic subscription and enables a NETCONF client to request via a dynamic subscription and
receive updates from a YANG datastore located on a NETCONF server. receive updates from a YANG datastore located on a NETCONF server.
skipping to change at page 3, line 38 skipping to change at page 3, line 38
3. Compatibility with RFC-5277's create-subscription 3. Compatibility with RFC-5277's create-subscription
A publisher is allowed to concurrently support dynamic subscription A publisher is allowed to concurrently support dynamic subscription
RPCs of [I-D.draft-ietf-netconf-subscribed-notifications] at the same RPCs of [I-D.draft-ietf-netconf-subscribed-notifications] at the same
time as [RFC5277]'s "create-subscription" RPC. However a single time as [RFC5277]'s "create-subscription" RPC. However a single
NETCONF transport session cannot support both this specification and NETCONF transport session cannot support both this specification and
a subscription established by [RFC5277]'s "create-subscription" RPC. a subscription established by [RFC5277]'s "create-subscription" RPC.
To protect against any attempts to use a single NETCONF transport To protect against any attempts to use a single NETCONF transport
session in this way: session in this way:
o A solution must reply with the [RFC6241] error "operation-not- o A solution MUST reply with the [RFC6241] "rpc-error" element
supported" if a "create-subscription" RPC is received on a NETCONF containing the "error-tag" value of "operation-not-supported" if a
session where an [I-D.draft-ietf-netconf-subscribed-notifications] "create-subscription" RPC is received on a NETCONF session where
established subscription exists. an [I-D.draft-ietf-netconf-subscribed-notifications] established
o A solution must reply with the [RFC6241] error "operation-not- subscription exists.
supported" if an "establish-subscription" request has been o A solution MUST reply with the [RFC6241] "rpc-error" element
received on a NETCONF session where the "create-subscription" RPC containing the "error-tag" value of "operation-not-supported" if
has successfully [RFC5277] created a subscription. an "establish-subscription" request has been received on a NETCONF
session where the "create-subscription" RPC has successfully
[RFC5277] created a subscription.
If a publisher supports this specification but not subscriptions via If a publisher supports this specification but not subscriptions via
[RFC5277], the publisher MUST NOT advertise [RFC5277], the publisher MUST NOT advertise
"urn:ietf:params:netconf:capability:notification:1.0". "urn:ietf:params:netconf:capability:notification:1.0".
4. Mandatory XML, event stream and datastore support 4. Mandatory XML, event stream and datastore support
The "encode-xml" feature of The "encode-xml" feature of
[I-D.draft-ietf-netconf-subscribed-notifications] MUST be supported. [I-D.draft-ietf-netconf-subscribed-notifications] MUST be supported.
This indicates that XML is a valid encoding for RPCs, state change This indicates that XML is a valid encoding for RPCs, state change
notifications, and subscribed content. notifications, and subscribed content.
A NETCONF publisher supporting event stream subscription via 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 document. "NETCONF" event stream identified in that document.
5. NETCONF connectivity and the Dynamic Subscriptions 5. NETCONF connectivity and the Dynamic Subscriptions
For a dynamic subscription, if the NETCONF session involved with the Management of dynamic subscriptions occurs via RPCs as defined in
"establish-subscription" terminates the subscription MUST be [I-D.ietf-netconf-yang-push] and
terminated. [I-D.draft-ietf-netconf-subscribed-notifications]. For a dynamic
subscription, if the NETCONF session involved with the "establish-
subscription" terminates, the subscription MUST be terminated.
For a dynamic subscription, any "modify-subscription", "delete- For a dynamic subscription, any "modify-subscription", "delete-
subscription", or "resynch-subscription" RPCs MUST be sent using the subscription", or "resync-subscription" RPCs MUST be sent using the
same NETCONF session upon which the referenced subscription was same NETCONF session upon which the referenced subscription was
established. established.
6. Notification Messages 6. Notification Messages
Notification messages transported over the NETCONF protocol MUST be Notification messages transported over the NETCONF protocol MUST be
encoded in a <notification> message as defined within [RFC5277], encoded in a <notification> message as defined within [RFC5277],
Section 4. And per [RFC5277]'s "eventTime" object definition, the Section 4. And per [RFC5277]'s "eventTime" object definition, the
"eventTime" MUST be populated with the event occurrence time. "eventTime" MUST be populated with the event occurrence time.
For dynamic subscriptions, all notification messages MUST use the For dynamic subscriptions, all notification messages MUST use the
NETCONF transport session used by the "establish-subscription" RPC. NETCONF transport session used by the "establish-subscription" RPC.
7. Dynamic Subscriptions and RPC Error Responses 7. Dynamic Subscriptions and RPC Error Responses
Management of dynamic subscriptions occurs via RPCs as defined in When an RPC error occurs as defined in
[I-D.ietf-netconf-yang-push] and [I-D.draft-ietf-netconf-subscribed-notifications] Section 2.4.6 and
[I-D.draft-ietf-netconf-subscribed-notifications]. When an RPC error [I-D.ietf-netconf-yang-push] Appendix A, the NETCONF RPC reply MUST
occurs, the NETCONF RPC reply MUST include an "rpc-error" element per include an "rpc-error" element per [RFC6241] with the error
[RFC6241] with the error information populated as follows: information populated as follows:
o an "error-type" node of "application". o An "error-type" node of "application".
o an "error-tag" node of "operation-failed". o An "error-tag" node with the value being a string that corresponds
o an "error-severity" of "error" (this MAY but does not have to be to an identity associated with the error. This "error-tag" will
included). come from one of two places. Either it will correspond to the
error identities within
[I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6
for general subscription errors:
error identity uses error-tag
---------------------- --------------
dscp-unavailable invalid-value
encoding-unsupported invalid-value
filter-unsupported invalid-value
insufficient-resources resource-denied
no-such-subscription invalid-value
replay-unsupported operation-not-supported
Or this "error-tag" will correspond to the error identities within
[I-D.ietf-netconf-yang-push] Appendix A.1 for subscription errors
specific to YANG datastores:
error identity uses error-tag
---------------------- --------------
cant-exclude operation-not-supported
datastore-not-subscribable invalid-value
no-such-subscription-resync invalid-value
on-change-unsupported operation-not-supported
on-change-sync-unsupported operation-not-supported
period-unsupported invalid-value
update-too-big too-big
sync-too-big too-big
unchanging-selection operation-failed
o an "error-severity" of "error" (this MAY be included).
o an "error-app-tag" node with the value being a string that o an "error-app-tag" node with the value being a string that
corresponds to an identity associated with the error, as defined corresponds to an identity associated with the error, as defined
in [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 subscriptions. The specific identity Appendix A.1, for datastore subscriptions. The specific identity
to use depends on the RPC for which the error occurred. Each to use depends on the RPC for which the error occurred. Each
error identity will be inserted as the "error-app-tag" following error identity will be inserted as the "error-app-tag" following
the form <modulename>:<identityname>. An example of such as valid the form <modulename>:<identityname>. An example of such as valid
encoding would be "ietf-subscribed-notifications:no-such- encoding would be "ietf-subscribed-notifications:no-such-
subscription". Viable errors for different RPCs are as follows: subscription". Viable errors for different RPCs are as follows:
RPC use base identity RPC use base identity
---------------------- ---------------------------- ---------------------- ----------------------------
establish-subscription establish-subscription-error establish-subscription establish-subscription-error
modify-subscription modify-subscription-error modify-subscription modify-subscription-error
delete-subscription delete-subscription-error delete-subscription delete-subscription-error
kill-subscription kill-subscription-error kill-subscription delete-subscription-error
resynch-subscription resynch-subscription-error resync-subscription resync-subscription-error
o In case of error responses to an "establish-subscription" or o In case of error responses to an "establish-subscription" or
"modify-subscription" request there is the option of including an "modify-subscription" request there is the option of including an
"error-info" node. This node may contain XML-encoded data with "error-info" node. This node may contain XML-encoded data with
hints for parameter settings that might lead to successful RPC hints for parameter settings that might lead to successful RPC
requests in the future. Following are the yang-data structures requests in the future. Following are the yang-data structures
from [I-D.draft-ietf-netconf-subscribed-notifications] and from [I-D.draft-ietf-netconf-subscribed-notifications] and
[I-D.ietf-netconf-yang-push] which may be returned: [I-D.ietf-netconf-yang-push] which may be returned:
establish-subscription returns hints in yang-data structure establish-subscription returns hints in yang-data structure
skipping to change at page 5, line 43 skipping to change at page 6, line 29
---------------------- ------------------------------------ ---------------------- ------------------------------------
target: event stream modify-subscription-stream-error-info target: event stream modify-subscription-stream-error-info
target: datastore modify-subscription-datastore-error-info target: datastore modify-subscription-datastore-error-info
The yang-data included within "error-info" SHOULD NOT include the The yang-data included within "error-info" SHOULD NOT include the
optional leaf "error-reason", as such a leaf would be redundant optional leaf "error-reason", as such a leaf would be redundant
with information that is already placed within the with information that is already placed within the
"error-app-tag". "error-app-tag".
In case of an rpc error resulting from a "delete-subscription", In case of an rpc error resulting from a "delete-subscription",
"kill-subscription", or "resynch-subscription" request, no "error- "kill-subscription", or "resync-subscription" request, no "error-
info" needs to be included, as the "subscription-id" is the only RPC info" needs to be included, as the "subscription-id" is the only RPC
input parameter and no hints regarding this RPC input parameters need input parameter and no hints regarding this RPC input parameters need
to be provided. to be provided.
8. Security Considerations 8. Security Considerations
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 accumulate establish-subscription requests, then these subscriptions accumulate
and may use up system resources. In such a situation, subscriptions and may use up system resources. In such a situation, subscriptions
MAY be terminated by terminating the underlying NETCONF session. The MAY be terminated by terminating the underlying NETCONF session. The
skipping to change at page 9, line 44 skipping to change at page 10, line 44
| | | |
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 message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <rpc message-id="102" 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>NETCONF</stream> <stream-xpath-filter xmlns:ex="http://example.com/events">
<stream-xpath-filter xmlns:ds="http://example.com/events"> /ex:foo/
/ds:foo/
</stream-xpath-filter> </stream-xpath-filter>
<stream>NETCONF</stream>
<dscp>10</dscp> <dscp>10</dscp>
</establish-subscription> </establish-subscription>
</rpc> </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 "id" of the accepted subscription publisher sends the subscription "id" of the accepted subscription
within message (b): within message (b):
skipping to change at page 10, line 29 skipping to change at page 11, line 29
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>invalid-value</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-app-tag> <error-app-tag>
ietf-subscribed-notifications:dscp-unavailable ietf-subscribed-notifications:dscp-unavailable
</error-app-tag> </error-app-tag>
</rpc-error> </rpc-error>
</rpc-reply> </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
skipping to change at page 11, line 40 skipping to change at page 12, line 40
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">
<id>23</id> <id>23</id>
<yp:datastore-xpath-filter xmlns:ds="http://example.com/datastore"> <yp:datastore-xpath-filter xmlns:ex="http://example.com/datastore">
/ds:foo/ds:bar /ex:foo/ex:bar
</yp:datastore-xpath-filter> </yp:datastore-xpath-filter>
<yp:periodic> <yp:periodic>
<yp:period>500</yp:period> <yp:period>500</yp:period>
</yp:periodic> </yp:periodic>
</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>invalid-value</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-app-tag> <error-app-tag>
ietf-yang-push:period-unsupported ietf-yang-push:period-unsupported
</error-app-tag> </error-app-tag>
<error-info> <error-info>
<modify-subscription-datastore-error-info <modify-subscription-datastore-error-info
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push"> xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push">
<period-hint> <period-hint>
3000 3000
</period-hint> </period-hint>
skipping to change at page 13, line 11 skipping to change at page 14, line 11
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.
Figure 10 shows a valid response for existing valid subscription Figure 10 shows a valid response for existing valid subscription
"id", but that subscription "id" was created on a different NETCONF "id", but that subscription "id" was created on a different NETCONF
transport session: 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>operation-failed</error-tag> <error-tag>invalid-value</error-tag>
<error-severity>error</error-severity> <error-severity>error</error-severity>
<error-app-tag> <error-app-tag>
ietf-subscribed-notifications:no-such-subscription ietf-subscribed-notifications:no-such-subscription
</error-app-tag> </error-app-tag>
</rpc-error> </rpc-error>
</rpc-reply> </rpc-reply>
Figure 10: Unsuccessful delete subscription Figure 10: Unsuccessful delete subscription
A.3. Subscription State Notifications A.3. Subscription State Notifications
skipping to change at page 16, line 24 skipping to change at page 17, line 24
</rpc> </rpc>
Figure 16 Figure 16
For more examples of subtree filters, see [RFC6241], section 6.4. For more examples of subtree filters, see [RFC6241], section 6.4.
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. v15 to v16 B.1. v16 to v17
o During the SN YANG Doctor review, a suggestion was made to update
the error-tags to make the mechanism work with embedded NETCONF
and RESTCONF error reporting.
o Minor text tweaks from review.
B.2. v15 to v16
o During the shepherd review, two clarifications were requested o During the shepherd review, two clarifications were requested
which do not impact the technical details of this document. These which do not impact the technical details of this document. These
clarifications were: (a) further describing that dynamic clarifications were: (a) further describing that dynamic
subscriptions can have state change notifications, and (b) more subscriptions can have state change notifications, and (b) more
details about the recommended text refinement desired for RFC6241. details about the recommended text refinement desired for RFC6241.
B.2. v14 to v15 B.3. v14 to v15
o Per Kent's request, added name attribute to artwork. This would o Per Kent's request, added name attribute to artwork. This would
be needed for an automated extraction. be needed for an automated extraction.
B.3. v13 to v14 B.4. v13 to v14
o Title change. o Title change.
B.4. v11 to v13 B.5. v11 to v13
o Subscription identifier renamed to id. o Subscription identifier renamed to id.
o Appendix A.4 for filter examples o Appendix A.4 for filter examples
o for v13, Tweak of example to /foo/bar o for v13, Tweak of example to /foo/bar
B.5. v10 to v11 B.6. v10 to v11
o Configured removed. o Configured removed.
B.6. v09 to v10 B.7. v09 to v10
o Tweaks to examples and text. o Tweaks to examples and text.
o Downshifted state names. o Downshifted state names.
o Removed address from examples. o Removed address from examples.
B.7. v08 to v09 B.8. v08 to v09
o Tweaks based on Kent's comments. o Tweaks based on Kent's comments.
o Updated examples in Appendix A. And updates to some object names o Updated examples in Appendix A. And updates to some object names
based on changes in the subscribed-notifications draft. based on changes in the subscribed-notifications draft.
o Added a YANG model for the NETCONF identity. o Added a YANG model for the NETCONF identity.
B.8. v07 to v08 B.9. v07 to v08
o Tweaks and clarification on :interleave. o Tweaks and clarification on :interleave.
B.9. v06 to v07 B.10. 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.10. v05 to v06 B.11. 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.11. v03 to v04 B.12. 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.12. v01 to v03 B.13. v01 to v03
o Text simplifications throughout o Text simplifications throughout
o v02 had no meaningful changes o v02 had no meaningful changes
B.13. v00 to v01 B.14. 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
 End of changes. 34 change blocks. 
70 lines changed or deleted 113 lines changed or added

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