idnits 2.17.1 draft-tao-netconf-data-export-capabilities-05.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 : ---------------------------------------------------------------------------- ** There are 17 instances of too long lines in the document, the longest one being 82 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 12, 2021) is 1016 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) == Missing Reference: 'RFC8641' is mentioned on line 89, but not defined == Missing Reference: 'I-D.netconf-notification-capabilities' is mentioned on line 98, but not defined == Unused Reference: 'RFC7950' is defined on line 551, but no explicit reference was found in the text == Unused Reference: 'RFC8126' is defined on line 559, but no explicit reference was found in the text == Unused Reference: 'RFC8342' is defined on line 573, but no explicit reference was found in the text == Unused Reference: 'RFC8407' is defined on line 578, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-netconf-https-notif' is defined on line 589, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-netconf-udp-notif' is defined on line 594, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-netconf-https-notif-08 == Outdated reference: A later version (-12) exists of draft-ietf-netconf-udp-notif-01 Summary: 1 error (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETCONF Working Group Q. Wu 3 Internet-Draft Q. Ma 4 Intended status: Standards Track Huawei 5 Expires: January 13, 2022 P. Liu 6 China Mobile 7 W. Wang 8 China Telecom 9 July 12, 2021 11 Telemetry Data Export capability 12 draft-tao-netconf-data-export-capabilities-05 14 Abstract 16 This document proposes a YANG module for telemetry data export 17 capabilities which augments system Capabilities model and provides 18 additional telemetry data export attributes associated with system 19 capabilities for transport specific Notification. This YANG module 20 can be used by the client to learn capability information from the 21 server at run-time or implementation- time, per the YANG Instance 22 Data File Format. 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 January 13, 2022. 41 Copyright Notice 43 Copyright (c) 2021 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 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Data Export capability . . . . . . . . . . . . . . . . . . . 3 61 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 62 3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 64 4.1. Updates to the IETF XML Registry . . . . . . . . . . . . 10 65 4.2. Updates to the YANG Module Names Registry . . . . . . . . 10 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 67 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 69 7.1. Normative References . . . . . . . . . . . . . . . . . . 12 70 7.2. Informative References . . . . . . . . . . . . . . . . . 13 71 Appendix A. Usage Example of interaction with UDP Notif and HTTP 72 Notif for Configured Subscription . . . . . . . . . 14 73 Appendix B. Usage Example of interaction with Adaptive 74 Subscription . . . . . . . . . . . . . . . . . . . . 15 75 Appendix C. Changes between Revisions . . . . . . . . . . . . . 18 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 78 1. Introduction 80 Notification capabilities model defined in [I-D.netconf-notification- 81 capabilities] allows a client to discover a set of capabilities 82 supported by the server (e.g., basic system capabilities and YANG- 83 Push related capabilities) both at implementation-time and run-time. 84 These capabilities allow the client adjust its behavior to take 85 advantage of the features exposed by the device. 87 However the client and the server may still support various different 88 transport specific parameters (e.g., transport protocol, encoding 89 format, encryption). As described in section 3.1 of [RFC8641], a 90 simple negotiation (i.e., inserting hints into error responses to a 91 failed RPC request) between subscribers and publishers for 92 subscription parameters increases the likelihood of success for 93 subsequent RPC requests, but not guaranteed, which may cause 94 unexpected failure or additional message exchange between client and 95 server. 97 This document defines a corresponding solution that is built on top 98 of [I-D.netconf-notification-capabilities]. Supplementing that work 99 are YANG data model augmentations for transport specific 100 notification. The module can be used by the client to discover 101 capability information from the server at run-time or implementation- 102 time, per the YANG Instance Data File Format. 104 1.1. Terminology 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 108 "OPTIONAL" in this document are to be interpreted as described in BCP 109 14 [RFC2119] [RFC8174] when, and only when, they appear in all 110 capitals, as shown here. 112 2. Data Export capability 114 The YANG module ietf-notification-capabilities defined in [I- 115 D.netconf-notification-capabilities] specify the following server 116 capabilities related to YANG Push: 118 o A set of capabilities related to the amount of notifications the 119 server can send out 121 o Specification of which data nodes support on-change notifications. 123 o Capability values can be specified on server level, datastore 124 level or on specific data nodes (and their contained sub-tree) of 125 a specific datastore. Capability values on a smaller, more 126 specific part of the server's data always override more generic 127 values. 129 o On-change capability is not specified on a server level as 130 different datastores usually have different on-change 131 capabilities. On a datastore level on-change capability for 132 configuration and state data can be specified separately. 134 These server capabilities are transport independent, session level 135 capabilities. They can be provided either at the implementation time 136 or reported at the run time. 138 This document augments system Capabilities model and provides 139 additional data export attributes associated with system 140 capabilities: 142 o Specification of transport protocol the client can use to 143 establish a transport connection; 145 o Specification of the encoding selection used (e.g., XML or JSON, 146 Binary) for Data Modeled with YANG; 148 o Specification of secure transport mechanisms that are needed by 149 the client to communicate with the server; 151 o Specification of the type of data compression algorithm (e.g., 152 lossless data compression) the client can use for file compression 153 and decompression 155 o Specification of the notification message encapsulation type, 156 either one notification per message or multiple notifications per 157 message. 159 o Specification of the update trigger type such as adaptive interval 160 trigger, timer event based trigger, count threshold trigger, 161 redundant suppression. 163 2.1. Tree Diagram 165 The following tree diagram [RFC8340] provides an overview of the data 166 model. 168 module: ietf-data-export-capabilities 169 augment /sysc:system-capabilities: 170 +--ro data-export-capabilities* [] 171 +--ro transport-protocol? identityref 172 +--ro encoding-format*? identityref 173 +--ro security-protocol? identityref 174 +--ro compression-mode*? identityref 175 +--ro message-bundling-support? empty 177 augment /sysc:system-capabilities/sysc:datastore-capabilities/sysc:per-node-capabilities: 178 +--ro data-export-capabilities 179 +--ro adaptive-interval-support? empty 180 +--ro timer-event-support? empty 181 +--ro counter-threshold-support? empty 182 +--ro suppress-redundant? empty 184 3. YANG Module 186 file "ietf-data-export-capabilities.yang" 187 module ietf-data-export-capabilities { 188 yang-version 1.1; 189 namespace "urn:ietf:params:xml:ns:yang:ietf-data-export-capabilities"; 190 prefix dec; 192 import ietf-system-capabilities { 193 prefix sysc; 194 } 195 import ietf-notification-capabilities { 196 prefix inc; 197 } 198 organization 199 "IETF NETCONF (Network Configuration) Working Group"; 200 contact 201 "WG Web: 202 WG List: 203 Editor: Qin Wu 204 Editor: Qiufang Ma 205 Editor: Peng Liu 206 Editor: Wei Wang "; 207 description 208 "This module defines an extension to System Capability and YANG Push 209 Notification Capabilities model and provides additional data export 210 attributes for transport specific notification. 212 Copyright (c) 2019 IETF Trust and the persons identified as 213 authors of the code. All rights reserved. 215 Redistribution and use in source and binary forms, with or 216 without modification, is permitted pursuant to, and subject 217 to the license terms contained in, the Simplified BSD License 218 set forth in Section 4.c of the IETF Trust's Legal Provisions 219 Relating to IETF Documents 220 (http://trustee.ietf.org/license-info). 222 This version of this YANG module is part of RFC XXXX; 223 see the RFC itself for full legal notices."; 225 revision 2020-07-03 { 226 description 227 "Initial revision."; 228 reference 229 "RFC XXXX: Telemetry Data Export capability"; 230 } 232 identity transport-protocol { 233 description 234 "Base identity for transport protocol type."; 235 } 237 identity tcp { 238 base transport-protocol; 239 description 240 "Identity for tcp as transport protocol."; 242 } 244 identity udp-notif { 245 base transport-protocol; 246 description 247 "Identity for udp notif as transport protocol."; 248 reference 249 "draft-ietf-netconf-udp-notif:UDP-based Transport 250 for Configured Subscriptions"; 251 } 253 identity http-notif { 254 base transport-protocol; 255 description 256 "Identity for http notif as transport protocol."; 257 reference 258 "draft-ietf-netconf-https-notif: An HTTPS-based 259 Transport for Configured Subscriptions"; 260 } 262 identity grpc { 263 base transport-protocol; 264 description 265 "Identity for grpc as transport protocol."; 266 } 268 identity security-protocol { 269 description 270 "Base identity for security protocol type."; 271 } 273 identity tls { 274 base security-protocol; 275 description 276 "Identity for tls security protocol."; 277 } 279 identity ssh { 280 base security-protocol; 281 description 282 "Identity for ssh transport protocol."; 283 } 285 identity encoding-format { 286 description 287 "Base identity for encoding format type."; 288 } 289 identity xml { 290 base encoding-format; 291 description 292 "Identity for xml encoding format."; 293 } 295 identity json { 296 base encoding-format; 297 description 298 "Identity for json encoding format."; 299 } 301 identity binary { 302 base encoding-format; 303 description 304 "Identity for binary encoding format."; 305 } 307 identity gpb { 308 base binary; 309 description 310 "Identity for gpb encoding format."; 311 } 313 identity cbor { 314 base binary; 315 description 316 "Identity for cbor encoding format."; 317 } 319 identity compression-mode { 320 description 321 "Base identity for compression mode."; 322 } 324 identity gzip { 325 base compression-mode; 326 description 327 "Identity for gzip compression mode."; 328 } 330 identity deflate { 331 base compression-mode; 332 description 333 "Identity for deflate compression mode."; 334 } 336 identity subscription-mode { 337 description 338 "Base identity for subscription mode."; 339 } 341 identity periodic { 342 base subscription-mode; 343 description 344 "Identity for periodic subscription mode."; 345 } 347 identity on-change { 348 base subscription-mode; 349 description 350 "Identity for on change subscription mode."; 351 } 353 identity event { 354 base subscription-mode; 355 description 356 "Identity for event based subscription mode."; 357 } 359 typedef centiseconds { 360 type uint32; 361 description 362 "A period of time, measured in units of 0.01 seconds."; 363 } 365 augment "/sysc:system-capabilities" { 366 description 367 "Add system level capability."; 368 list data-export-capabilities { 369 description 370 "Capabilities related to telemetry data export capabilities negotiation."; 371 leaf transport-protocol { 372 type identityref { 373 base transport-protocol; 374 } 375 description 376 "Type of transport protocol."; 377 } 378 leaf-list encoding-format { 379 type identityref { 380 base encoding-format; 381 } 382 description 383 "Type of encoding format."; 384 } 385 leaf security-protocol { 386 type identityref { 387 base security-protocol; 388 } 389 description 390 "Type of secure transport."; 391 } 392 leaf-list compression-mode { 393 type identityref { 394 base compression-mode; 395 } 396 description 397 "Type of compression mode."; 398 } 399 leaf message-bundling-support { 400 type empty; 401 description 402 "Enables message bundling support."; 403 } 404 } 405 } 407 augment "/sysc:system-capabilities/sysc:datastore-capabilities/sysc:per-node-capabilities" { 408 description 409 "Add datastore and node level capability."; 410 container data-export-capabilities { 411 description 412 "Capabilities related to telemetry data export capability negotiation."; 413 leaf adaptive-interval-support { 414 type empty; 415 description 416 "Present if one event stream supports multiple period intervals and 417 allows period interval switching. Absent if the event stream doesn't 418 support period interval switching."; 419 } 420 leaf timer-event-support { 421 type empty; 422 description 423 "Present if timer event is supported, i.e.,, schedule a specific event 424 periodically with specified start time, duration, repeat option, repeat 425 interval."; 426 } 427 leaf counter-threshold-support { 428 type empty; 429 description 430 "Present if the subscription mode is counter based 431 trigger is support (i.e., named counter crosses a 432 specified threshold). Absent if coutner based 433 trigger mode is not supported. "; 434 } 435 leaf suppress-redundant { 436 type empty; 437 description 438 "Suppress dupplicated data objects to be sent during each update interval."; 439 } 440 } 441 } 442 } 443 445 4. IANA Considerations 447 4.1. Updates to the IETF XML Registry 449 This document registers a URI in the "IETF XML Registry" [RFC3688]. 450 Following the format in [RFC3688], the following registration has 451 been made: 453 URI: 454 urn:ietf:params:xml:ns:yang:ietf-data-export-capabilities 455 Registrant Contact: 456 The IESG. 457 XML: 458 N/A; the requested URI is an XML namespace. 460 4.2. Updates to the YANG Module Names Registry 462 This document registers one YANG module in the "YANG Module Names" 463 registry [RFC6020]. Following the format in [RFC6020], the following 464 registration has been made: 466 name: 467 ietf-data-export-capabilities 468 namespace: 469 urn:ietf:params:xml:ns:yang:ietf-data-export-capabilities 470 prefix: 471 dec 472 reference: 473 RFC XXXX (RFC Ed.: replace XXX with actual RFC number and remove 474 this note.) 476 5. Security Considerations 478 The YANG module specified in this document defines a schema for data 479 that is designed to be accessed via network management protocols such 480 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 481 is the secure transport layer, and the mandatory-to-implement secure 482 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 483 is HTTPS, and the mandatory-to-implement secure transport is TLS 484 [RFC8446]. 486 The NETCONF Configuration Access Control Model (NACM) [RFC8341] 487 provides the means to restrict access for particular NETCONF or 488 RESTCONF users to a preconfigured subset of all available NETCONF or 489 RESTCONF protocol operations and content. 491 There are a number of data nodes defined in this YANG module that are 492 writable/creatable/deletable (i.e., config true, which is the 493 default). These data nodes may be considered sensitive in some 494 network environments. Write operations (e.g., edit-config) to these 495 data nodes without proper protection can have a negative effect on 496 network operations. These are the subtrees and data nodes and their 497 sensitivity/vulnerability: 499 o /sysc:system-capabilities/dec:transport-protocol 501 o /sysc:system-capabilities/dec:encoding-format 503 o /sysc:system-capabilities/dec:security-protocol 505 o /sysc:system-capabilities/dec:compression-mode 507 o /sysc:system-capabilities/inc:subscription-capabilities/ 508 dec:message-bundling-support 510 6. Contributors 511 Ran Tao 512 Huawei 513 101 Software Avenue, Yuhua District 514 Nanjing, Jiangsu 210012 515 China 516 Email: taoran20@huawei.com 518 Liang Geng 519 China Mobile 520 32 Xuanwumen West St, Xicheng District 521 Beijing 10053 523 Email: gengliang@chinamobile.com 525 Thomas Graf 526 Swisscom 527 Binzring 17 528 Zuerich 8045 529 Switzerland 531 Email: thomas.graf@swisscom.com 533 7. References 535 7.1. Normative References 537 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 538 Requirement Levels", BCP 14, RFC 2119, 539 DOI 10.17487/RFC2119, March 1997, 540 . 542 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 543 and A. Bierman, Ed., "Network Configuration Protocol 544 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 545 . 547 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 548 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 549 . 551 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 552 RFC 7950, DOI 10.17487/RFC7950, August 2016, 553 . 555 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 556 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 557 . 559 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 560 Writing an IANA Considerations Section in RFCs", BCP 26, 561 RFC 8126, DOI 10.17487/RFC8126, June 2017, 562 . 564 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 565 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 566 May 2017, . 568 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 569 Access Control Model", STD 91, RFC 8341, 570 DOI 10.17487/RFC8341, March 2018, 571 . 573 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 574 and R. Wilton, "Network Management Datastore Architecture 575 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 576 . 578 [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of 579 Documents Containing YANG Data Models", BCP 216, RFC 8407, 580 DOI 10.17487/RFC8407, October 2018, 581 . 583 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 584 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 585 . 587 7.2. Informative References 589 [I-D.ietf-netconf-https-notif] 590 Jethanandani, M. and K. Watsen, "An HTTPS-based Transport 591 for YANG Notifications", draft-ietf-netconf-https-notif-08 592 (work in progress), February 2021. 594 [I-D.ietf-netconf-udp-notif] 595 Zheng, G., Zhou, T., Graf, T., Francois, P., and P. 596 Lucente, "UDP-based Transport for Configured 597 Subscriptions", draft-ietf-netconf-udp-notif-01 (work in 598 progress), November 2020. 600 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 601 DOI 10.17487/RFC3688, January 2004, 602 . 604 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 605 the Network Configuration Protocol (NETCONF)", RFC 6020, 606 DOI 10.17487/RFC6020, October 2010, 607 . 609 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 610 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 611 . 613 Appendix A. Usage Example of interaction with UDP Notif and HTTP Notif 614 for Configured Subscription 616 The following instance-data example describes the Data Export 617 Notification capabilities of a hypothetical "acme-router". 619 620 622 acme-router-notification-capabilities 623 624 ietf-system-capabilities@2020-03-23 625 ietf-notification-capabilities@2020-03-23 626 ietf-data-export-capabilities@2020-03-23 627 628 629 Server Capability Discovery 630 631 635 636 http-notif 637 json 638 xml 639 640 641 udp-notif 642 binary 643 644 645 646 648 In addition, the client could also query data export capability from 649 the server. For example, the client sends request message to 650 the the server to query data export capability from the server. 652 653 654 655 656 657 658 659 660 662 The server returns server data export capability using as 663 follows: 665 666 667 668 669 http-notif 670 json 671 672 673 udp-notif 674 binary 675 676 677 678 680 Appendix B. Usage Example of interaction with Adaptive Subscription 682 The following instance-data example describes the Data Export 683 Notification capabilities of a hypothetical "acme-router". The 684 router implements the running, and operational datastores. Every 685 change can be reported on-change from running, but only config = true 686 nodes and some config = false data from operational. Interface 687 statistics are reported only when both adaptive-interval-support and 688 count-threshold-support are present. 690 691 693 acme-router-notification-capabilities 694 695 ietf-system-capabilities@2020-03-23 696 ietf-notification-capabilities@2020-03-23 697 ietf-data-export-capabilities@2020-03-23 698 699 700 Defines the notification capabilities of an acme-router. 701 The router only has running, and operational datastores. 702 Every change can be reported on-change from running, but 703 only config=true nodes and some config=false data from operational. 704 Statistics are not reported based on timer based trigger and counter 705 threshold based trigger. 706 707 708 714 716 ds:operational 717 718 719 /if:interfaces/if:interface/if:statistics 720 721 722 5 723 724 725 state-changes 726 727 728 729 730 731 /if:interfaces/if:interface/if:statistics/if:out-octets 732 733 734 735 736 737 /if:interfaces/if:interface/if:statistics/if:in-errors 738 739 740 741 742 743 744 745 746 747 748 The client configures adaptive subscription parameters on the server. 749 The adaptive subscription configuration parameters require the server 750 to scan all interface of specific type every 5 seconds if the value 751 of interface in-errors is greater than 1000; If the interface in- 752 errors value is less than 1000, switch to 60 seconds period value, 753 and then scan all client every 60 seconds. 755 757 758 759 760 761 762 765 767 ds:running 768 769 771 /if:ietf-interfaces 772 773 776 /if:interfaces/if:interface/if:statistics 777 in-errors 778 779 in-errors > 1000 780 1000 781 5 782 783 784 in-errors < 1000 785 1000 786 60 787 788 789 790 791 792 794 Appendix C. Changes between Revisions 796 v04 - v05 798 o Change per-node-capabilities related parameters into empty type. 800 o Revise abstract and introduction section to only focus on 801 capability fetching mechanism from the client to the server. 803 o Update Usage Example of interaction with HTTP-Notif and UDP-Notif 804 for Configured Subscription. 806 v03 - v04 808 o Add interface namespace in the Adaptive Subscription usage 809 example. 811 o subtrees and data nodes changes in the security section. 813 o Two compression mode related identities change. 815 o Move message-bundling-support parameer to system capabilities 816 level. 818 o Add an example to discuss report reciever capability from the 819 client per yang instance file format. 821 o Change encoding format from leaf to leaf-list and support multiple 822 encoding formats for the same transport specific notif. 824 v02 - v03 826 o Change 'data-export-capabilities' into list type to support 827 multiple transport protocol, encoding on the server. 829 o Add Usage Example of interaction with UDP based Transport for 830 Configured Subscription. 832 o Add Thomas Graf as a contributor; 834 o Update motivation in the introduction to clarify why this work is 835 needed. 837 o Support udp notif and http notif as two optional transport in the 838 YANG data model. 840 Authors' Addresses 842 Qin Wu 843 Huawei 844 101 Software Avenue, Yuhua District 845 Nanjing, Jiangsu 210012 846 China 848 Email: bill.wu@huawei.com 850 Qiufang Ma 851 Huawei 852 101 Software Avenue, Yuhua District 853 Nanjing, Jiangsu 210012 854 China 856 Email: maqiufang1@huawei.com 858 Peng Liu 859 China Mobile 860 Beiqijia Town, Changping District 861 Beijing 10053 863 Email: liupengyjy@chinamobile.com 865 Wei Wang 866 China Telecom 867 32 Xuanwumen West St, Xicheng District 868 Beijing 102209 870 Email: wangw36@chinatelecom.cn