< draft-ietf-netconf-netconf-event-notifications-19.txt   draft-ietf-netconf-netconf-event-notifications-20.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: October 31, 2019 Huawei Expires: November 9, 2019 Huawei
A. Gonzalez Prieto A. Gonzalez Prieto
Microsoft Microsoft
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
April 29, 2019 May 8, 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-19 draft-ietf-netconf-netconf-event-notifications-20
Abstract Abstract
This document provides a NETCONF binding to the dynamic subscription This document provides a Network Configuration Protocol (NETCONF)
capability of both subscribed notifications and YANG-Push. binding to the dynamic subscription 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 references to pre-RFC normative
normative drafts with the actual assigned RFC numbers. 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 October 31, 2019. This Internet-Draft will expire on November 9, 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 35 skipping to change at page 2, line 36
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 . . . . . . . . 5 7. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
11. Notes to the RFC Editor . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . 7
12.1. Normative References . . . . . . . . . . . . . . . . . . 7 11.2. Informative References . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . 9 A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 9
A.3. Subscription State Notifications . . . . . . . . . . . . 14 A.3. Subscription State Notifications . . . . . . . . . . . . 13
A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 15 A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Changes between revisions . . . . . . . . . . . . . 17 Appendix B. Changes between revisions . . . . . . . . . . . . . 16
B.1. v17 to v19 . . . . . . . . . . . . . . . . . . . . . . . 17 B.1. v19 to v20 . . . . . . . . . . . . . . . . . . . . . . . 16
B.2. v16 to v17 . . . . . . . . . . . . . . . . . . . . . . . 17 B.2. v17 to v19 . . . . . . . . . . . . . . . . . . . . . . . 17
B.3. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 17 B.3. v16 to v17 . . . . . . . . . . . . . . . . . . . . . . . 17
B.4. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 17 B.4. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 17
B.5. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 18 B.5. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 17
B.6. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 18 B.6. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 17
B.7. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 18 B.7. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 17
B.8. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 18 B.8. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 17
B.9. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 18 B.9. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 17
B.10. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 18 B.10. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 18
B.11. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 18 B.11. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 18
B.12. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 18 B.12. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 18
B.13. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 19 B.13. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 18
B.14. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 19 B.14. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 18
B.15. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 19 B.15. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 18
B.16. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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.draft-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.
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
skipping to change at page 3, line 42 skipping to change at page 3, line 43
The following terms are defined in The following terms are defined in
[I-D.draft-ietf-netconf-subscribed-notifications]: dynamic [I-D.draft-ietf-netconf-subscribed-notifications]: dynamic
subscription, event stream, notification message, publisher, subscription, event stream, notification message, publisher,
receiver, subscriber, subscription. No additional terms are defined. receiver, subscriber, subscription. No additional terms are defined.
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 MUST NOT support both this specification
a subscription established by [RFC5277]'s "create-subscription" RPC. and a subscription established by [RFC5277]'s "create-subscription"
To protect against any attempts to use a single NETCONF transport RPC. To protect against any attempts to use a single NETCONF
session in this way: transport session in this way:
o A solution MUST reply with the [RFC6241] "rpc-error" element o A solution MUST reply with the [RFC6241] "rpc-error" element
containing the "error-tag" value of "operation-not-supported" if a containing the "error-tag" value of "operation-not-supported" if a
"create-subscription" RPC is received on a NETCONF session where "create-subscription" RPC is received on a NETCONF session where
an [I-D.draft-ietf-netconf-subscribed-notifications] established an [I-D.draft-ietf-netconf-subscribed-notifications] established
subscription exists. subscription exists.
o A solution MUST reply with the [RFC6241] "rpc-error" element o A solution MUST reply with the [RFC6241] "rpc-error" element
containing the "error-tag" value of "operation-not-supported" if containing the "error-tag" value of "operation-not-supported" if
an "establish-subscription" request has been received on a NETCONF an "establish-subscription" request has been received on a NETCONF
session where the "create-subscription" RPC has successfully session where the "create-subscription" RPC has successfully
[RFC5277] created a subscription. [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".
skipping to change at page 4, line 29 skipping to change at page 4, line 30
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
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.draft-ietf-netconf-yang-push] and
[I-D.draft-ietf-netconf-subscribed-notifications]. For a dynamic [I-D.draft-ietf-netconf-subscribed-notifications]. For a dynamic
subscription, if the NETCONF session involved with the "establish- subscription, if the NETCONF session involved with the "establish-
subscription" terminates, the subscription MUST be terminated. 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 "resync-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" 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
When an RPC error occurs as defined in When an RPC error occurs as defined in
[I-D.draft-ietf-netconf-subscribed-notifications] Section 2.4.6 and [I-D.draft-ietf-netconf-subscribed-notifications] Section 2.4.6 and
[I-D.ietf-netconf-yang-push] Appendix A, the NETCONF RPC reply MUST [I-D.draft-ietf-netconf-yang-push] Appendix A, the NETCONF RPC reply
include an "rpc-error" element per [RFC6241] with the error MUST include an "rpc-error" element per [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 with the value being a string that corresponds o An "error-tag" node with the value being a string that corresponds
to an identity associated with the error. This "error-tag" will to an identity associated with the error. This "error-tag" will
come from one of two places. Either it will correspond to the come from one of two places. Either it will correspond to the
error identities within error identities within
[I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6 [I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6
for general subscription errors: for general subscription errors:
error identity uses error-tag error identity uses error-tag
---------------------- -------------- ---------------------- --------------
dscp-unavailable invalid-value dscp-unavailable invalid-value
encoding-unsupported invalid-value encoding-unsupported invalid-value
filter-unsupported invalid-value filter-unsupported invalid-value
insufficient-resources resource-denied insufficient-resources resource-denied
no-such-subscription invalid-value no-such-subscription invalid-value
replay-unsupported operation-not-supported replay-unsupported operation-not-supported
Or this "error-tag" will correspond to the error identities within Or this "error-tag" will correspond to the error identities within
[I-D.ietf-netconf-yang-push] Appendix A.1 for subscription errors [I-D.draft-ietf-netconf-yang-push] Appendix A.1 for subscription
specific to YANG datastores: errors specific to YANG datastores:
error identity uses error-tag error identity uses error-tag
---------------------- -------------- ---------------------- --------------
cant-exclude operation-not-supported cant-exclude operation-not-supported
datastore-not-subscribable invalid-value datastore-not-subscribable invalid-value
no-such-subscription-resync invalid-value no-such-subscription-resync invalid-value
on-change-unsupported operation-not-supported on-change-unsupported operation-not-supported
on-change-sync-unsupported operation-not-supported on-change-sync-unsupported operation-not-supported
period-unsupported invalid-value period-unsupported invalid-value
update-too-big too-big update-too-big too-big
sync-too-big too-big sync-too-big too-big
unchanging-selection operation-failed unchanging-selection operation-failed
o an "error-severity" of "error" (this MAY be included). 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.draft-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
skipping to change at page 6, line 23 skipping to change at page 6, line 23
delete-subscription delete-subscription-error delete-subscription delete-subscription-error
kill-subscription delete-subscription-error kill-subscription delete-subscription-error
resync-subscription resync-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.draft-ietf-netconf-yang-push] which may be returned:
establish-subscription returns hints in yang-data structure establish-subscription returns hints in yang-data structure
---------------------- ------------------------------------ ---------------------- ------------------------------------
target: event stream establish-subscription-stream-error-info target: event stream establish-subscription-stream-error-info
target: datastore establish-subscription-datastore-error-info target: datastore establish-subscription-datastore-error-info
modify-subscription returns hints in yang-data structure modify-subscription returns hints in yang-data structure
---------------------- ------------------------------------ ---------------------- ------------------------------------
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
skipping to change at page 7, line 19 skipping to change at page 7, line 19
This document has no actions for IANA. This document has no actions for IANA.
10. Acknowledgments 10. 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,
Qin Wu, and Guangying Zheng. Qin Wu, and Guangying Zheng.
11. Notes to the RFC Editor 11. References
This section can be removed by the RFC editor after the requests have
been performed.
RFC 6241 needs to be updated based on the needs of this draft.
RFC-6241 section 1.2 bullet "(2)" targets RFC-5277 (actually it
identifies RFC 5717, but that was an error fixed after RFC
publication). Anyway the current phrasing in RFC-5277 says that a
notification message can only be sent after a successful "create-
subscription". Therefore the reference text must be modified to also
allow notification messages be sent after a successful "establish-
subscription". Proposed text for bullet (2) of RFC-6241 would be:
(2) The Messages layer provides a simple, transport-independent
framing mechanism for encoding RPCs and notifications.
Section 4 documents the RPC messages, [RFC5277] documents
Notifications sent as a result of a <create-subscription> RPC,
and [RFC xxxx] documents Notifications sent as a result of
an <establish-subscription> RPC.
(where xxxx is replaced with this RFC number)
12. References
12.1. Normative References 11.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, "Customized Subscriptions to a and E. Nilsen-Nygaard, "Customized Subscriptions to a
Publisher's Event Streams", September 2018, Publisher's Event Streams", September 2018,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-subscribed-notifications/>. draft-ietf-netconf-subscribed-notifications/>.
[I-D.ietf-netconf-yang-push] [I-D.draft-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", September 2018, Lengyel, "YANG Datastore Subscription", September 2018,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-yang-push/>. draft-ietf-netconf-yang-push/>.
[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>.
skipping to change at page 8, line 30 skipping to change at page 8, line 9
[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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
12.2. Informative References 11.2. Informative References
[RFC8347] Liu, X., Ed., Kyparlis, A., Parikh, R., Lindem, A., and M. [RFC8347] Liu, X., Ed., Kyparlis, A., Parikh, R., Lindem, A., and M.
Zhang, "A YANG Data Model for the Virtual Router Zhang, "A YANG Data Model for the Virtual Router
Redundancy Protocol (VRRP)", RFC 8347, Redundancy Protocol (VRRP)", RFC 8347,
DOI 10.17487/RFC8347, March 2018, DOI 10.17487/RFC8347, March 2018,
<https://www.rfc-editor.org/info/rfc8347>. <https://www.rfc-editor.org/info/rfc8347>.
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)
Version 1.0", November 1999, Version 1.0", November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>. <http://www.w3.org/TR/1999/REC-xpath-19991116>.
skipping to change at page 12, line 29 skipping to change at page 11, line 40
| RPC Reply: OK | | RPC Reply: OK |
|<-----------------------------| |<-----------------------------|
| | | |
| notification message (for 23)| | notification message (for 23)|
|<-----------------------------| |<-----------------------------|
| | | |
Figure 6: Interaction model for successful subscription modification Figure 6: Interaction model for successful subscription modification
If the subscription being modified in Figure 6 is a datastore If the subscription being modified in Figure 6 is a datastore
subscription as per [I-D.ietf-netconf-yang-push], the modification subscription as per [I-D.draft-ietf-netconf-yang-push], the
request made in (c) may look like that shown in Figure 7. As can be modification request made in (c) may look like that shown in
seen, the modifications being attempted are the application of a new Figure 7. As can be seen, the modifications being attempted are the
XPath filter as well as the setting of a new periodic time interval. application of a new 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:ex="http://example.com/datastore"> <yp:datastore-xpath-filter xmlns:ex="http://example.com/datastore">
/ex:foo/ex:bar /ex:foo/ex:bar
</yp:datastore-xpath-filter> </yp:datastore-xpath-filter>
skipping to change at page 17, line 24 skipping to change at page 16, line 47
</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. v17 to v19 B.1. v19 to v20
o Notes to RFC editor removed, consideration moved under Figure 10
in SN.
B.2. v17 to v19
o Per Benjamin Kaduk's discuss on SN, adjusted IPR to o Per Benjamin Kaduk's discuss on SN, adjusted IPR to
pre5378Trust200902 pre5378Trust200902
B.2. v16 to v17 B.3. v16 to v17
o During the SN YANG Doctor review, a suggestion was made to update o During the SN YANG Doctor review, a suggestion was made to update
the error-tags to make the mechanism work with embedded NETCONF the error-tags to make the mechanism work with embedded NETCONF
and RESTCONF error reporting. and RESTCONF error reporting.
o Minor text tweaks from review. o Minor text tweaks from review.
B.3. v15 to v16 B.4. 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.4. v14 to v15 B.5. 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.5. v13 to v14 B.6. v13 to v14
o Title change. o Title change.
B.6. v11 to v13 B.7. 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.7. v10 to v11 B.8. v10 to v11
o Configured removed. o Configured removed.
B.8. v09 to v10 B.9. 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.9. v08 to v09 B.10. 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.10. v07 to v08 B.11. v07 to v08
o Tweaks and clarification on :interleave. o Tweaks and clarification on :interleave.
B.11. v06 to v07 B.12. 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.12. v05 to v06 B.13. 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.13. v03 to v04 B.14. 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.14. v01 to v03 B.15. v01 to v03
o Text simplifications throughout o Text simplifications throughout
o v02 had no meaningful changes o v02 had no meaningful changes
B.15. v00 to v01 B.16. 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. 38 change blocks. 
89 lines changed or deleted 72 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/