idnits 2.17.1 draft-ietf-netconf-netconf-event-notifications-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 195 has weird spacing: '...ription estab...' == Line 199 has weird spacing: '...ription res...' == Line 211 has weird spacing: '... stream esta...' == Line 214 has weird spacing: '...ription ret...' == Line 216 has weird spacing: '... stream modi...' -- The document date (December 18, 2018) is 1957 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETCONF E. Voit 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track A. Clemm 5 Expires: June 21, 2019 Huawei 6 A. Gonzalez Prieto 7 Microsoft 8 E. Nilsen-Nygaard 9 A. Tripathy 10 Cisco Systems 11 December 18, 2018 13 Dynamic subscription to YANG Events and Datastores over NETCONF 14 draft-ietf-netconf-netconf-event-notifications-15 16 Abstract 18 This document provides a NETCONF binding to the dynamic subscription 19 capability of both subscribed notifications and YANG push. 21 RFC Editor note: please replace the four references to pre-RFC 22 normative drafts with the actual assigned RFC numbers. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on June 21, 2019. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. Compatibility with RFC-5277's create-subscription . . . . . . 3 61 4. Mandatory XML, event stream and datastore support . . . . . . 3 62 5. NETCONF connectivity and the Dynamic Subscriptions . . . . . 4 63 6. Notification Messages . . . . . . . . . . . . . . . . . . . . 4 64 7. Dynamic Subscriptions and RPC Error Responses . . . . . . . . 4 65 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 66 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 67 10. Notes to the RFC Editor . . . . . . . . . . . . . . . . . . . 6 68 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 11.1. Normative References . . . . . . . . . . . . . . . . . . 6 70 11.2. Informative References . . . . . . . . . . . . . . . . . 7 71 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 7 72 A.1. Event Stream Discovery . . . . . . . . . . . . . . . . . 7 73 A.2. Dynamic Subscriptions . . . . . . . . . . . . . . . . . . 8 74 A.3. Subscription State Notifications . . . . . . . . . . . . 12 75 A.4. Filter Examples . . . . . . . . . . . . . . . . . . . . . 14 76 Appendix B. Changes between revisions . . . . . . . . . . . . . 15 77 B.1. v14 to v15 . . . . . . . . . . . . . . . . . . . . . . . 15 78 B.2. v13 to v14 . . . . . . . . . . . . . . . . . . . . . . . 16 79 B.3. v11 to v13 . . . . . . . . . . . . . . . . . . . . . . . 16 80 B.4. v10 to v11 . . . . . . . . . . . . . . . . . . . . . . . 16 81 B.5. v09 to v10 . . . . . . . . . . . . . . . . . . . . . . . 16 82 B.6. v08 to v09 . . . . . . . . . . . . . . . . . . . . . . . 16 83 B.7. v07 to v08 . . . . . . . . . . . . . . . . . . . . . . . 16 84 B.8. v06 to v07 . . . . . . . . . . . . . . . . . . . . . . . 16 85 B.9. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 16 86 B.10. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 17 87 B.11. v01 to v03 . . . . . . . . . . . . . . . . . . . . . . . 17 88 B.12. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 17 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 91 1. Introduction 93 This document provides a binding for events streamed over the NETCONF 94 protocol [RFC6241] for dynamic subscriptions as defined in 95 [I-D.draft-ietf-netconf-subscribed-notifications]. In addition, as 96 [I-D.ietf-netconf-yang-push] is itself built upon 98 [I-D.draft-ietf-netconf-subscribed-notifications], this document 99 enables a NETCONF client to request via a dynamic subscription and 100 receive updates from a YANG datastore located on a NETCONF server. 102 2. Terminology 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 106 "OPTIONAL" in this document are to be interpreted as described in BCP 107 14 [RFC2119] [RFC8174] when, and only when, they appear in all 108 capitals, as shown here. 110 The following terms are defined in 111 [I-D.draft-ietf-netconf-subscribed-notifications]: dynamic 112 subscription, event stream, notification message, publisher, 113 receiver, subscriber, subscription. No additional terms are defined. 115 3. Compatibility with RFC-5277's create-subscription 117 A publisher is allowed to concurrently support dynamic subscription 118 RPCs of [I-D.draft-ietf-netconf-subscribed-notifications] at the same 119 time as [RFC5277]'s "create-subscription" RPC. However a single 120 NETCONF transport session cannot support both this specification and 121 a subscription established by [RFC5277]'s "create-subscription" RPC. 122 To protect against any attempts to use a single NETCONF transport 123 session in this way: 125 o A solution must reply with the [RFC6241] error "operation-not- 126 supported" if a "create-subscription" RPC is received on a NETCONF 127 session where an [I-D.draft-ietf-netconf-subscribed-notifications] 128 established subscription exists. 129 o A solution must reply with the [RFC6241] error "operation-not- 130 supported" if an "establish-subscription" request has been 131 received on a NETCONF session where the "create-subscription" RPC 132 has successfully [RFC5277] created a subscription. 134 If a publisher supports this specification but not subscriptions via 135 [RFC5277], the publisher MUST NOT advertise 136 "urn:ietf:params:netconf:capability:notification:1.0". 138 4. Mandatory XML, event stream and datastore support 140 The "encode-xml" feature of 141 [I-D.draft-ietf-netconf-subscribed-notifications] MUST be supported. 142 This indicates that XML is a valid encoding for RPCs, state change 143 notifications, and subscribed content. 145 A NETCONF publisher supporting event stream subscription via 146 [I-D.draft-ietf-netconf-subscribed-notifications] MUST support the 147 "NETCONF" event stream identified in that document. 149 5. NETCONF connectivity and the Dynamic Subscriptions 151 For a dynamic subscription, if the NETCONF session involved with the 152 "establish-subscription" terminates the subscription MUST be 153 terminated. 155 For a dynamic subscription, any "modify-subscription", "delete- 156 subscription", or "resynch-subscription" RPCs MUST be sent using the 157 same NETCONF session upon which the referenced subscription was 158 established. 160 6. Notification Messages 162 Notification messages transported over the NETCONF protocol MUST be 163 encoded in a message as defined within [RFC5277], 164 Section 4. And per [RFC5277]'s "eventTime" object definition, the 165 "eventTime" MUST be populated with the event occurrence time. 167 For dynamic subscriptions, all notification messages MUST use the 168 NETCONF transport session used by the "establish-subscription" RPC. 170 7. Dynamic Subscriptions and RPC Error Responses 172 Management of dynamic subscriptions occurs via RPCs as defined in 173 [I-D.ietf-netconf-yang-push] and 174 [I-D.draft-ietf-netconf-subscribed-notifications]. When an RPC error 175 occurs, the NETCONF RPC reply MUST include an "rpc-error" element per 176 [RFC6241] with the error information populated as follows: 178 o an "error-type" node of "application". 179 o an "error-tag" node of "operation-failed". 180 o an "error-severity" of "error" (this MAY but does not have to be 181 included). 182 o an "error-app-tag" node with the value being a string that 183 corresponds to an identity associated with the error, as defined 184 in [I-D.draft-ietf-netconf-subscribed-notifications] section 2.4.6 185 for general subscriptions, and [I-D.ietf-netconf-yang-push] 186 Appendix A.1, for datastore subscriptions. The specific identity 187 to use depends on the RPC for which the error occurred. Each 188 error identity will be inserted as the "error-app-tag" following 189 the form :. An example of such as valid 190 encoding would be "ietf-subscribed-notifications:no-such- 191 subscription". Viable errors for different RPCs are as follows: 193 RPC use base identity 194 ---------------------- ---------------------------- 195 establish-subscription establish-subscription-error 196 modify-subscription modify-subscription-error 197 delete-subscription delete-subscription-error 198 kill-subscription kill-subscription-error 199 resynch-subscription resynch-subscription-error 201 o In case of error responses to an "establish-subscription" or 202 "modify-subscription" request there is the option of including an 203 "error-info" node. This node may contain XML-encoded data with 204 hints for parameter settings that might lead to successful RPC 205 requests in the future. Following are the yang-data structures 206 from [I-D.draft-ietf-netconf-subscribed-notifications] and 207 [I-D.ietf-netconf-yang-push] which may be returned: 209 establish-subscription returns hints in yang-data structure 210 ---------------------- ------------------------------------ 211 target: event stream establish-subscription-stream-error-info 212 target: datastore establish-subscription-datastore-error-info 214 modify-subscription returns hints in yang-data structure 215 ---------------------- ------------------------------------ 216 target: event stream modify-subscription-stream-error-info 217 target: datastore modify-subscription-datastore-error-info 219 The yang-data included within "error-info" SHOULD NOT include the 220 optional leaf "error-reason", as such a leaf would be redundant 221 with information that is already placed within the 222 "error-app-tag". 224 In case of an rpc error resulting from a "delete-subscription", 225 "kill-subscription", or "resynch-subscription" request, no "error- 226 info" needs to be included, as the "subscription-id" is the only RPC 227 input parameter and no hints regarding this RPC input parameters need 228 to be provided. 230 8. Security Considerations 232 If a malicious or buggy NETCONF subscriber sends a number of 233 establish-subscription requests, then these subscriptions accumulate 234 and may use up system resources. In such a situation, subscriptions 235 MAY be terminated by terminating the underlying NETCONF session. The 236 publisher MAY also suspend or terminate a subset of the active 237 subscriptions on that NETCONF session. 239 9. Acknowledgments 241 We wish to acknowledge the helpful contributions, comments, and 242 suggestions that were received from: Andy Bierman, Yan Gang, Sharon 243 Chisholm, Hector Trevino, Peipei Guo, Susan Hares, Tim Jenkins, 244 Balazs Lengyel, Martin Bjorklund, Mahesh Jethanandani, Kent Watsen, 245 and Guangying Zheng. 247 10. Notes to the RFC Editor 249 This section can be removed by the RFC editor after the requests have 250 been performed. 252 RFC 6241 need to be updated. RFC-6241 refers to RFC-5277 which says 253 that a notification message can only be sent after a successful 254 "create-subscription". This text must be modified to also allow 255 notification messages be sent after a successful "establish- 256 subscription". 258 11. References 260 11.1. Normative References 262 [I-D.draft-ietf-netconf-subscribed-notifications] 263 Voit, E., Clemm, A., Gonzalez Prieto, A., Tripathy, A., 264 and E. Nilsen-Nygaard, "Customized Subscriptions to a 265 Publisher's Event Streams", September 2018, 266 . 269 [I-D.ietf-netconf-yang-push] 270 Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto., 271 Tripathy, A., Nilsen-Nygaard, E., Bierman, A., and B. 272 Lengyel, "YANG Datastore Subscription", September 2018, 273 . 276 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 277 Requirement Levels", BCP 14, RFC 2119, 278 DOI 10.17487/RFC2119, March 1997, 279 . 281 [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event 282 Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008, 283 . 285 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 286 and A. Bierman, Ed., "Network Configuration Protocol 287 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 288 . 290 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 291 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 292 May 2017, . 294 11.2. Informative References 296 [RFC8347] Liu, X., Ed., Kyparlis, A., Parikh, R., Lindem, A., and M. 297 Zhang, "A YANG Data Model for the Virtual Router 298 Redundancy Protocol (VRRP)", RFC 8347, 299 DOI 10.17487/RFC8347, March 2018, 300 . 302 [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) 303 Version 1.0", November 1999, 304 . 306 Appendix A. Examples 308 This section is non-normative. 310 A.1. Event Stream Discovery 312 As defined in [I-D.draft-ietf-netconf-subscribed-notifications] an 313 event stream exposes a continuous set of events available for 314 subscription. A NETCONF client can retrieve the list of available 315 event streams from a NETCONF publisher using the "get" operation 316 against the top-level container "/streams" defined in 317 [I-D.draft-ietf-netconf-subscribed-notifications] Section 3.1. 319 The following example illustrates the retrieval of the list of 320 available event streams: 322 324 325 326 328 329 330 332 Figure 1: Get streams request 334 After such a request, the NETCONF publisher returns a list of event 335 streams available, as well as additional information which might 336 exist in the container. 338 A.2. Dynamic Subscriptions 340 A.2.1. Establishing Dynamic Subscriptions 342 The following figure shows two successful "establish-subscription" 343 RPC requests as per 344 [I-D.draft-ietf-netconf-subscribed-notifications]. The first request 345 is given a subscription "id" of 22, the second, an "id" of 23. 347 +------------+ +-----------+ 348 | Subscriber | | Publisher | 349 +------------+ +-----------+ 350 | | 351 | Capability Exchange | 352 |<---------------------------->| 353 | | 354 | | 355 | establish-subscription | 356 |----------------------------->| (a) 357 | RPC Reply: OK, id = 22 | 358 |<-----------------------------| (b) 359 | | 360 | notification message (for 22)| 361 |<-----------------------------| 362 | | 363 | | 364 | establish-subscription | 365 |----------------------------->| 366 | notification message (for 22)| 367 |<-----------------------------| 368 | RPC Reply: OK, id = 23 | 369 |<-----------------------------| 370 | | 371 | | 372 | notification message (for 22)| 373 |<-----------------------------| 374 | notification message (for 23)| 375 |<-----------------------------| 376 | | 378 Figure 2: Multiple subscriptions over a NETCONF session 380 To provide examples of the information being transported, example 381 messages for interactions (a) and (b) in Figure 2 are detailed below: 383 384 386 NETCONF 387 388 /ds:foo/ 389 390 10 391 392 394 Figure 3: establish-subscription request (a) 396 As NETCONF publisher was able to fully satisfy the request (a), the 397 publisher sends the subscription "id" of the accepted subscription 398 within message (b): 400 402 404 22 405 406 408 Figure 4: establish-subscription success (b) 410 If the NETCONF publisher had not been able to fully satisfy the 411 request, or subscriber has no authorization to establish the 412 subscription, the publisher would have sent an RPC error response. 413 For instance, if the "dscp" value of 10 asserted by the subscriber in 414 Figure 3 proved unacceptable, the publisher may have returned: 416 418 419 application 420 operation-failed 421 error 422 423 ietf-subscribed-notifications:dscp-unavailable 424 425 426 428 Figure 5: an unsuccessful establish subscription 430 The subscriber can use this information in future attempts to 431 establish a subscription. 433 A.2.2. Modifying Dynamic Subscriptions 435 An existing subscription may be modified. The following exchange 436 shows a negotiation of such a modification via several exchanges 437 between a subscriber and a publisher. This negotiation consists of a 438 failed RPC modification request/response, followed by a successful 439 one. 441 +------------+ +-----------+ 442 | Subscriber | | Publisher | 443 +------------+ +-----------+ 444 | | 445 | notification message (for 23)| 446 |<-----------------------------| 447 | | 448 | modify-subscription (id = 23)| 449 |----------------------------->| (c) 450 | RPC error (with hint) | 451 |<-----------------------------| (d) 452 | | 453 | modify-subscription (id = 23)| 454 |----------------------------->| 455 | RPC Reply: OK | 456 |<-----------------------------| 457 | | 458 | notification message (for 23)| 459 |<-----------------------------| 460 | | 462 Figure 6: Interaction model for successful subscription modification 464 If the subscription being modified in Figure 6 is a datastore 465 subscription as per [I-D.ietf-netconf-yang-push], the modification 466 request made in (c) may look like that shown in Figure 7. As can be 467 seen, the modifications being attempted are the application of a new 468 XPath filter as well as the setting of a new periodic time interval. 470 472 475 23 476 477 /ds:foo/ds:bar 478 479 480 500 481 482 483 485 Figure 7: Subscription modification request (c) 487 If the NETCONF publisher can satisfy both changes, the publisher 488 sends a positive result for the RPC. If the NETCONF publisher cannot 489 satisfy either of the proposed changes, the publisher sends an RPC 490 error response (d). The following is an example RPC error response 491 for (d) which includes a hint. This hint is an alternative time 492 period value which might have resulted in a successful modification: 494 496 497 application 498 operation-failed 499 error 500 501 ietf-yang-push:period-unsupported 502 503 504 506 507 3000 508 509 510 511 512 514 Figure 8: Modify subscription failure with hint (d) 516 A.2.3. Deleting Dynamic Subscriptions 518 The following demonstrates deleting a subscription. This 519 subscription may have been to either a stream or a datastore. 521 523 525 22 526 527 529 Figure 9: Delete subscription 531 If the NETCONF publisher can satisfy the request, the publisher 532 replies with success to the RPC request. 534 If the NETCONF publisher cannot satisfy the request, the publisher 535 sends an error-rpc element indicating the modification didn't work. 536 Figure 10 shows a valid response for existing valid subscription 537 "id", but that subscription "id" was created on a different NETCONF 538 transport session: 540 542 543 application 544 operation-failed 545 error 546 547 ietf-subscribed-notifications:no-such-subscription 548 549 550 552 Figure 10: Unsuccessful delete subscription 554 A.3. Subscription State Notifications 556 A publisher will send subscription state notifications for dynamic 557 subscriptions according to the definitions within 558 [I-D.draft-ietf-netconf-subscribed-notifications]. 560 A.3.1. subscription-modified 562 As per Section 2.7.2 of 563 [I-D.draft-ietf-netconf-subscribed-notifications], a "subscription- 564 modified" might be sent over NETCONF if the definition of a 565 configured filter changes. A subscription state notification encoded 566 in XML would look like: 568 569 2007-09-01T10:00:00Z 570 572 39 573 574 /ex:foo 575 576 NETCONF 577 578 580 Figure 11: subscription-modified subscription state notification 582 A.3.2. subscription-resumed, and replay-complete 584 A "subscription-resumed" would look like: 586 588 2007-09-01T10:00:00Z 589 591 39 592 593 595 Figure 12: subscription-resumed notification in XML 597 The "replay-complete" is virtually identical, with "subscription- 598 resumed" simply being replaced by "replay-complete". 600 A.3.3. subscription-terminated and subscription-suspended 602 A "subscription-terminated" would look like: 604 606 2007-09-01T10:00:00Z 607 609 39 610 611 suspension-timeout 612 613 614 616 Figure 13: subscription-terminated subscription state notification 618 The "subscription-suspended" is virtually identical, with 619 "subscription-terminated" simply being replaced by "subscription- 620 suspended". 622 A.4. Filter Examples 624 This section provides examples which illustrate both XPath and 625 subtree methods of filtering event record contents. The examples are 626 based on the YANG notification "vrrp-protocol-error-event" as defined 627 per the ietf-vrrp.yang model within [RFC8347]. Event records based 628 on this specification which are generated by the publisher might 629 appear as: 631 632 2018-09-14T08:22:33.44Z 633 635 checksum-error 636 637 639 Figure 14: RFC 8347 (VRRP) - Example Notification 641 Suppose a subscriber wanted to establish a subscription which only 642 passes instances of event records where there is a "checksum-error" 643 as part of a VRRP protocol event. Also assume the publisher places 644 such event records into the NETCONF stream. To get a continuous 645 series of matching event records, the subscriber might request the 646 application of an XPath filter against the NETCONF stream. An 647 "establish-subscription" RPC to meet this objective might be: 649 650 652 NETCONF 653 654 /vrrp-protocol-error-event[ 655 vrrp:protocol-error-reason="vrrp:checksum-error"] 656 657 658 660 Figure 15: Establishing a subscription error reason via XPath 662 For more examples of XPath filters, see [XPATH]. 664 Suppose the "establish-subscription" in Figure 15 was accepted. And 665 suppose later a subscriber decided they wanted to broaden this 666 subscription cover to all VRRP protocol events (i.e., not just those 667 with a "checksum error"). The subscriber might attempt to modify the 668 subscription in a way which replaces the XPath filter with a subtree 669 filter which sends all VRRP protocol events to a subscriber. Such a 670 "modify-subscription" RPC might look like: 672 673 675 99 676 677 679 680 681 683 Figure 16 685 For more examples of subtree filters, see [RFC6241], section 6.4. 687 Appendix B. Changes between revisions 689 (To be removed by RFC editor prior to publication) 691 B.1. v14 to v15 693 o Per Kent's request, added name attribute to artwork. This would 694 be needed for an automated extraction. 696 B.2. v13 to v14 698 o Title change. 700 B.3. v11 to v13 702 o Subscription identifier renamed to id. 703 o Appendix A.4 for filter examples 704 o for v13, Tweak of example to /foo/bar 706 B.4. v10 to v11 708 o Configured removed. 710 B.5. v09 to v10 712 o Tweaks to examples and text. 713 o Downshifted state names. 714 o Removed address from examples. 716 B.6. v08 to v09 718 o Tweaks based on Kent's comments. 719 o Updated examples in Appendix A. And updates to some object names 720 based on changes in the subscribed-notifications draft. 721 o Added a YANG model for the NETCONF identity. 723 B.7. v07 to v08 725 o Tweaks and clarification on :interleave. 727 B.8. v06 to v07 729 o XML encoding and operational datastore mandatory. 730 o Error mechanisms and examples updated. 732 B.9. v05 to v06 734 o Moved examples to appendices 735 o All examples rewritten based on namespace learnings 736 o Normative text consolidated in front 737 o Removed all mention of JSON 738 o Call home process detailed 739 o Note: this is a major revision attempting to cover those comments 740 received from two week review. 742 B.10. v03 to v04 744 o Added additional detail to "configured subscriptions" 745 o Added interleave capability 746 o Adjusted terminology to that in draft-ietf-netconf-subscribed- 747 notifications 748 o Corrected namespaces in examples 750 B.11. v01 to v03 752 o Text simplifications throughout 753 o v02 had no meaningful changes 755 B.12. v00 to v01 757 o Added Call Home in solution for configured subscriptions. 758 o Clarified support for multiple subscription on a single session. 759 No need to support multiple create-subscription. 760 o Added mapping between terminology in yang-push and [RFC6241] (the 761 one followed in this document). 762 o Editorial improvements. 764 Authors' Addresses 766 Eric Voit 767 Cisco Systems 769 Email: evoit@cisco.com 771 Alexander Clemm 772 Huawei 774 Email: ludwig@clemm.org 776 Alberto Gonzalez Prieto 777 Microsoft 779 Email: alberto.gonzalez@microsoft.com 781 Einar Nilsen-Nygaard 782 Cisco Systems 784 Email: einarnn@cisco.com 785 Ambika Prasad Tripathy 786 Cisco Systems 788 Email: ambtripa@cisco.com