< draft-ietf-netconf-netconf-event-notifications-21.txt   draft-ietf-netconf-netconf-event-notifications-22.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: November 16, 2019 Huawei Expires: November 20, 2019 Huawei
A. Gonzalez Prieto A. Gonzalez Prieto
Microsoft Microsoft
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
May 15, 2019 May 19, 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-21 draft-ietf-netconf-netconf-event-notifications-22
Abstract Abstract
This document provides a Network Configuration Protocol (NETCONF) This document provides a Network Configuration Protocol (NETCONF)
binding to the dynamic subscription capability of both subscribed binding to the dynamic subscription capability of both subscribed
notifications and YANG-Push. notifications and YANG-Push.
RFC Editor note: please replace the references to pre-RFC normative RFC Editor note: please replace the references to pre-RFC normative
drafts with the actual assigned RFC numbers. drafts with the actual assigned RFC numbers.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 November 16, 2019. This Internet-Draft will expire on November 20, 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 45 skipping to change at page 2, line 45
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 8 11.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 . . . . . . . . . . . . 14
A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 15 A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Changes between revisions . . . . . . . . . . . . . 17 Appendix B. Changes between revisions . . . . . . . . . . . . . 17
B.1. v20 to v21 . . . . . . . . . . . . . . . . . . . . . . . 17 B.1. v21 to v22 . . . . . . . . . . . . . . . . . . . . . . . 17
B.2. v19 to v20 . . . . . . . . . . . . . . . . . . . . . . . 17 B.2. v20 to v21 . . . . . . . . . . . . . . . . . . . . . . . 17
B.3. v17 to v19 . . . . . . . . . . . . . . . . . . . . . . . 17 B.3. v19 to v20 . . . . . . . . . . . . . . . . . . . . . . . 17
B.4. v16 to v17 . . . . . . . . . . . . . . . . . . . . . . . 17 B.4. v17 to v19 . . . . . . . . . . . . . . . . . . . . . . . 17
B.5. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 17 B.5. v16 to v17 . . . . . . . . . . . . . . . . . . . . . . . 17
B.6. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 18 B.6. v15 to v16 . . . . . . . . . . . . . . . . . . . . . . . 18
B.7. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 18 B.7. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 18
B.8. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 18 B.8. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 18
B.9. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 18 B.9. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 18
B.10. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 18 B.10. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 18
B.11. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 18 B.11. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 18
B.12. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 18 B.12. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 18
B.13. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 18 B.13. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 18
B.14. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 18 B.14. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 19
B.15. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 19 B.15. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 19
B.16. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 19 B.16. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 19
B.17. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 19 B.17. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 19
B.18. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
This document specifies the binding of a stream of events which form This document specifies the binding of a stream of events which form
part of a dynamic subscription to the NETCONF protocol [RFC6241]. part of a dynamic subscription to the NETCONF protocol [RFC6241].
Dynamic subscriptions are defined in Dynamic subscriptions are defined in
[I-D.draft-ietf-netconf-subscribed-notifications]. In addition, as [I-D.draft-ietf-netconf-subscribed-notifications]. In addition, as
[I-D.draft-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
skipping to change at page 4, line 51 skipping to change at page 4, line 51
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" populated with the event occurrence time. "eventTime" is 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.draft-ietf-netconf-yang-push] Appendix A, the NETCONF RPC reply [I-D.draft-ietf-netconf-yang-push] Appendix A, the NETCONF RPC reply
MUST include an "rpc-error" element per [RFC6241] with the error MUST include an "rpc-error" element per [RFC6241] with the error
skipping to change at page 17, 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. v20 to v21 B.1. v21 to v22
o Added "is".
B.2. v20 to v21
o Including Tom Petch's text to resolve the meaning of 'binding'. o Including Tom Petch's text to resolve the meaning of 'binding'.
o A few small wording tweaks. o A few small wording tweaks.
B.2. v19 to v20 B.3. v19 to v20
o Notes to RFC editor removed, consideration moved under Figure 10 o Notes to RFC editor removed, consideration moved under Figure 10
in SN. in SN.
B.3. v17 to v19 B.4. 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.4. v16 to v17 B.5. 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.5. v15 to v16 B.6. 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.6. v14 to v15 B.7. 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.7. v13 to v14 B.8. v13 to v14
o Title change. o Title change.
B.8. v11 to v13 B.9. 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.9. v10 to v11 B.10. v10 to v11
o Configured removed. o Configured removed.
B.10. v09 to v10 B.11. 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.11. v08 to v09 B.12. 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.12. v07 to v08 B.13. v07 to v08
o Tweaks and clarification on :interleave. o Tweaks and clarification on :interleave.
B.13. v06 to v07 B.14. 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.14. v05 to v06 B.15. 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.15. v03 to v04 B.16. 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.16. v01 to v03 B.17. v01 to v03
o Text simplifications throughout o Text simplifications throughout
o v02 had no meaningful changes o v02 had no meaningful changes
B.17. v00 to v01 B.18. 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. 23 change blocks. 
39 lines changed or deleted 44 lines changed or added

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