idnits 2.17.1 draft-ietf-core-yang-library-03.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 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 154 has weird spacing: '...ntifier sid...' == Line 159 has weird spacing: '...ntifier sid...' == Line 165 has weird spacing: '...ntifier sid...' == Line 170 has weird spacing: '...ntifier sid...' == Line 177 has weird spacing: '...ntifier ds:...' -- The document date (January 11, 2021) is 1200 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) == Unused Reference: 'RFC6991' is defined on line 706, but no explicit reference was found in the text == Outdated reference: A later version (-17) exists of draft-ietf-core-comi-10 == Outdated reference: A later version (-24) exists of draft-ietf-core-sid-14 ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147) Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force M. Veillette, Ed. 3 Internet-Draft Trilliant Networks Inc. 4 Intended status: Standards Track I. Petrov, Ed. 5 Expires: July 15, 2021 Acklio 6 January 11, 2021 8 Constrained YANG Module Library 9 draft-ietf-core-yang-library-03 11 Abstract 13 This document describes a constrained version of the YANG library 14 that provides information about the YANG modules, datastores, and 15 datastore schemas used by a constrained network management server 16 (e.g., a CORECONF server). 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on July 15, 2021. 35 Copyright Notice 37 Copyright (c) 2021 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 2 54 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 4 56 3.2. Major differences between ietf-constrained-yang-library 57 and ietf-yang-library . . . . . . . . . . . . . . . . . . 4 58 4. YANG Module "ietf-constrained-yang-library" . . . . . . . . . 5 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 60 5.1. YANG Module Registration . . . . . . . . . . . . . . . . 13 61 5.2. YANG Namespace Registration . . . . . . . . . . . . . . . 13 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 63 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 65 8.1. Normative References . . . . . . . . . . . . . . . . . . 15 66 8.2. Informative References . . . . . . . . . . . . . . . . . 16 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 69 1. Introduction 71 There is a need for a standard mechanism to expose which YANG 72 modules, datastores and datastore schemas are in use by a constrained 73 network management server. This document defines the YANG module 74 'ietf-constrained-yang-library' that provides this information. 76 YANG module 'ietf-constrained-yang-library' shares the same data 77 model and objectives as 'ietf-yang-library', only datatypes and 78 mandatory requirements have been updated to minimize its size to 79 allow its implementation by Constrained Nodes and/or Constrained 80 Networks as defined by [RFC7228]. To review the list of objectives 81 and the proposed data model, please refer to [RFC8525] section 2 and 82 3. 84 2. Terminology and Notation 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 88 "OPTIONAL" in this document are to be interpreted as described in BCP 89 14 [RFC2119] [RFC8174] when, and only when, they appear in all 90 capitals, as shown here. 92 The following terms are defined in [RFC7950]: client, deviation, 93 feature, module, submodule, and server. 95 The following term is defined in [I-D.ietf-core-sid]: YANG Schema 96 Item iDentifier (SID). 98 The following terms are defined in [RFC8525]: YANG library and YANG 99 library checksum. 101 3. Overview 103 The conceptual model of the YANG library is depicted in Figure 1. 105 +-----------+ 106 | datastore | 107 +-----------+ 108 | 109 | has a 110 V 111 +-----------+ +--------+ +------------+ 112 | datastore | union of | module | consists of | modules + | 113 | schema |----------->| set |--------------->| submodules | 114 +-----------+ +--------+ +------------+ 116 Figure 1: Conceptual model of the YANG library 118 It's expected that most constrained network management servers have 119 one datastore (e.g. a unified datastore). However, some servers may 120 have multiples datastore as described by NMDA [RFC8342]. The YANG 121 library data model supports both cases. 123 In this model, every datastore has an associated datastore schema, 124 which is the union of module sets, which is a collection of modules. 125 Multiple datastores may refer to the same datastore schema and 126 individual datastore schemas may share module sets. 128 For each module, the YANG library provides: 130 o the YANG module identifier (i.e., SID) 132 o its revision 134 o its list of submodules 136 o its list of imported modules 138 o its set of features and deviations 140 YANG module namespace and location are also supported, but their 141 implementation is not recommended for constrained servers. 143 3.1. Tree diagram 145 The tree diagram of YANG module ietf-constrained-yang-library is 146 provided below. This graphical representation of a YANG module is 147 defined in [RFC8340]. 149 module: ietf-constrained-yang-library 150 +--ro yang-library 151 +--ro module-set* [index] 152 | +--ro index uint8 153 | +--ro module* [identifier] 154 | | +--ro identifier sid:sid 155 | | +--ro revision? revision-identifier 156 | | +--ro namespace? inet:uri 157 | | +--ro location* inet:uri 158 | | +--ro submodule* [identifier] 159 | | | +--ro identifier sid:sid 160 | | | +--ro revision? revision-identifier 161 | | | +--ro location* inet:uri 162 | | +--ro feature* sid:sid 163 | | +--ro deviation* -> ../../module/identifier 164 | +--ro import-only-module* [identifier revision] 165 | +--ro identifier sid:sid 166 | +--ro revision union 167 | +--ro namespace? inet:uri 168 | +--ro location* inet:uri 169 | +--ro submodule* [identifier] 170 | +--ro identifier sid:sid 171 | +--ro revision? revision-identifier 172 | +--ro location* inet:uri 173 +--ro schema* [index] 174 | +--ro index uint8 175 | +--ro module-set* -> ../../module-set/index 176 +--ro datastore* [identifier] 177 | +--ro identifier ds:datastore-ref 178 | +--ro schema -> ../../schema/index 179 +--ro checksum binary 181 notifications: 182 +---n yang-library-update 183 +--ro checksum -> /yang-library/checksum 185 3.2. Major differences between ietf-constrained-yang-library and ietf- 186 yang-library 188 The changes between the reference data model 'ietf-yang-library' and 189 its constrained version 'ietf-constrained-yang-library' are listed 190 below: 192 o module-set 'name' and schema 'name' are implemented using 8 bits 193 unsigned integers and renamed 'index'. 195 o module 'name', submodule 'name' and datastore 'name' are 196 implemented using a SID (i.e. an unsigned integer) and renamed 197 'identifier'. 199 o 'feature' and 'deviation' are implemented using a SID (i.e. an 200 unsigned integer). 202 o 'revision' fields are implemented using a 4 bytes binary string. 204 o the mandatory requirement of the 'namespace' fields is removed, 205 and implementation is not recommended. SIDs used by constrained 206 devices and protocols don't require namespaces. 208 o the implementation of the 'location' fields are not recommended, 209 the use of the module SID as the handle to retrieve the associated 210 YANG module is proposed instead. 212 4. YANG Module "ietf-constrained-yang-library" 214 RFC Ed.: update the date below with the date of RFC publication and 215 remove this note. 217 file "ietf-constrained-yang-library@2019-03-28.yang" 218 module ietf-constrained-yang-library { 219 yang-version 1.1; 220 namespace 221 "urn:ietf:params:xml:ns:yang:ietf-constrained-yang-library"; 222 prefix "yanglib"; 224 // RFC Ed.: update ietf-core-sid reference. 226 import ietf-sid-file { 227 prefix sid; 228 reference "RFC YYYY: YANG Schema Item iDentifier (SID)"; 229 // RFC Editor: Please replace YYYY with RFC number of I-D.ietf-core-sid. 230 } 231 import ietf-inet-types { 232 prefix inet; 233 reference "RFC 6991: Common YANG Data Types."; 234 } 235 import ietf-datastores { 236 prefix ds; 237 reference 238 "RFC 8342: Network Management Datastore Architecture (NMDA)."; 239 } 240 organization 241 "IETF CoRE Working Group"; 243 contact 244 "WG Web: 246 WG List: 248 Editor: Michel Veillette 249 251 Editor: Ivaylo Petrov 252 "; 254 description 255 "Copyright (c) 2021 IETF Trust and the persons identified as 256 authors of the code. All rights reserved. 258 Redistribution and use in source and binary forms, with or 259 without modification, is permitted pursuant to, and subject to 260 the license terms contained in, the Simplified BSD License set 261 forth in Section 4.c of the IETF Trust's Legal Provisions 262 Relating to IETF Documents 263 (https://trustee.ietf.org/license-info). 265 This version of this YANG module is part of RFC XXXX 266 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself 267 for full legal notices. 269 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 270 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 271 'MAY', and 'OPTIONAL' in this document are to be interpreted as 272 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 273 they appear in all capitals, as shown here. 275 This module provides information about the YANG modules, 276 datastores, and datastore schemas implemented by a 277 constrained network management server."; 279 // RFC Editor: Please replace XXXX with RFC number and remove this note 281 revision 2019-03-28 { 282 description 283 "Second revision."; 284 reference 285 "RFC XXXX: Constrained YANG Module Library"; 286 // RFC Editor: Please replace XXXX with RFC number and remove this note 287 } 288 /* 289 * Typedefs 290 */ 292 typedef revision-identifier { 293 type binary { 294 length "4"; 295 } 296 description 297 "Revision date encoded as a binary string, each nibble 298 representing a digit of the revision date. For example, 299 revision 2018-09-21 is encoded as 0x20 0x18 0x09 0x21."; 300 } 302 /* 303 * Groupings 304 */ 306 grouping module-identification-leafs { 307 description 308 "Parameters for identifying YANG modules and submodules."; 310 leaf identifier { 311 type sid:sid; 312 mandatory true; 313 description 314 "SID assigned to this module or submodule."; 315 } 316 leaf revision { 317 type revision-identifier; 318 description 319 "The YANG module or submodule revision date. If no 320 revision statement is present in the YANG module 321 or submodule, this leaf is not instantiated."; 322 } 323 } 325 grouping location-leaf-list { 326 description 327 "Common location leaf list parameter for modules and 328 submodules."; 330 leaf-list location { 331 type inet:uri; 332 description 333 "Contains a URL that represents the YANG schema resource 334 for this module or submodule. 336 This leaf is present in the model to keep the alignment 337 with 'ietf-yang-library'. Support of this leaf in 338 constrained devices is not necessarily required, nor 339 expected. It is recommended that clients used the module 340 or sub-module SID as the handle used to retrieve the 341 corresponding YANG module"; 342 } 343 } 345 grouping implementation-parameters { 346 description 347 "Parameters for describing the implementation of a module."; 349 leaf-list feature { 350 type sid:sid; 351 description 352 "List of all YANG feature names from this module that are 353 supported by the server, regardless whether they are 354 defined in the module or any included submodule."; 355 } 356 leaf-list deviation { 357 type leafref { 358 path "../../module/identifier"; 359 } 360 description 361 "List of all YANG deviation modules used by this server to 362 modify the conformance of the module associated with this 363 entry. Note that the same module can be used for 364 deviations for multiple modules, so the same entry MAY 365 appear within multiple 'module' entries. 367 This reference MUST NOT (directly or indirectly) 368 refer to the module being deviated. 370 Robust clients may want to make sure that they handle a 371 situation where a module deviates itself (directly or 372 indirectly) gracefully."; 373 } 374 } 376 grouping module-set-parameters { 377 description 378 "A set of parameters that describe a module set."; 380 leaf index { 381 type uint8; 382 description 383 "An arbitrary number assigned of the module set."; 385 } 386 list module { 387 key "identifier"; 388 description 389 "An entry in this list represents a module implemented 390 by the server, as per RFC 7950 section 5.6.5, with a 391 particular set of supported features and deviations."; 392 reference 393 "RFC 7950: The YANG 1.1 Data Modeling Language."; 395 uses module-identification-leafs; 397 leaf namespace { 398 type inet:uri; 399 description 400 "The XML namespace identifier for this module. 401 This leaf is present in the model to keep the alignment 402 with 'ietf-yang-library'. Support of this leaf in 403 constrained devices is not required, nor expected."; 404 } 406 uses location-leaf-list; 408 list submodule { 409 key "identifier"; 410 description 411 "Each entry represents one submodule within the parent 412 module."; 413 uses module-identification-leafs; 414 uses location-leaf-list; 415 } 417 uses implementation-parameters; 418 } 419 list import-only-module { 420 key "identifier revision"; 421 description 422 "An entry in this list indicates that the server imports 423 reusable definitions from the specified revision of the 424 module, but does not implement any protocol accessible 425 objects from this revision. 427 Multiple entries for the same module name MAY exist. 428 This can occur if multiple modules import the same 429 module, but specify different revision-dates in the 430 import statements."; 432 leaf identifier { 433 type sid:sid; 434 description 435 "The YANG module name."; 436 } 437 leaf revision { 438 type union { 439 type revision-identifier; 440 type string { 441 length 0; 442 } 443 } 444 description 445 "The YANG module revision date."; 446 } 447 leaf namespace { 448 type inet:uri; 449 description 450 "The XML namespace identifier for this module. 451 This leaf is present in the model to keep the alignment 452 with 'ietf-yang-library'. Support of this leaf in 453 constrained devices is not required, nor expected."; 454 } 456 uses location-leaf-list; 458 list submodule { 459 key "identifier"; 460 description 461 "Each entry represents one submodule within the 462 parent module."; 464 uses module-identification-leafs; 465 uses location-leaf-list; 466 } 467 } 468 } 470 grouping yang-library-parameters { 471 description 472 "The YANG library data structure is represented as a grouping 473 so it can be reused in configuration or another monitoring 474 data structure."; 476 list module-set { 477 key index; 478 description 479 "A set of modules that may be used by one or more schemas. 481 A module set does not have to be referentially complete, 482 i.e., it may define modules that contain import statements 483 for other modules not included in the module set."; 485 uses module-set-parameters; 486 } 488 list schema { 489 key "index"; 490 description 491 "A datastore schema that may be used by one or more 492 datastores. 494 The schema must be valid and referentially complete, 495 i.e., it must contain modules to satisfy all used import 496 statements for all modules specified in the schema."; 498 leaf index { 499 type uint8; 500 description 501 "An arbitrary reference number assigned to the schema."; 502 } 503 leaf-list module-set { 504 type leafref { 505 path "../../module-set/index"; 506 } 507 description 508 "A set of module-sets that are included in this schema. 509 If a non import-only module appears in multiple module 510 sets, then the module revision and the associated 511 features and deviations must be identical."; 512 } 513 } 515 list datastore { 516 key "identifier"; 517 description 518 "A datastore supported by this server. 520 Each datastore indicates which schema it supports. 522 The server MUST instantiate one entry in this list 523 per specific datastore it supports. 525 Each datstore entry with the same datastore schema 526 SHOULD reference the same schema."; 528 leaf identifier { 529 type ds:datastore-ref; 530 description 531 "The identity of the datastore."; 532 } 533 leaf schema { 534 type leafref { 535 path "../../schema/index"; 536 } 537 mandatory true; 538 description 539 "A reference to the schema supported by this datastore. 540 All non import-only modules of the schema are 541 implemented with their associated features and 542 deviations."; 543 } 544 } 545 } 547 /* 548 * Top-level container 549 */ 551 container yang-library { 552 config false; 553 description 554 "Container holding the entire YANG library of this server."; 556 uses yang-library-parameters; 558 leaf checksum { 559 type binary; 560 mandatory true; 561 description 562 "A server-generated checksum or digest of the contents of 563 the 'yang-library' tree. The server MUST change the 564 value of this leaf if the information represented by 565 the 'yang-library' tree, except 'yang-library/checksum', 566 has changed."; 567 } 568 } 570 /* 571 * Notifications 572 */ 574 notification yang-library-update { 575 description 576 "Generated when any YANG library information on the 577 server has changed."; 579 leaf checksum { 580 type leafref { 581 path "/yanglib:yang-library/yanglib:checksum"; 582 } 583 mandatory true; 584 description 585 "Contains the YANG library checksum or digest for the 586 updated YANG library at the time the notification is 587 generated."; 588 } 589 } 590 } 591 593 5. IANA Considerations 595 5.1. YANG Module Registration 597 This document registers one YANG module in the YANG Module Names 598 registry [RFC7950]. 600 name: ietf-constrained-yang-library 602 namespace: urn:ietf:params:xml:ns:yang:ietf-constrained-yang-library 604 prefix: lib 606 reference: RFC XXXX 608 // RFC Ed.: replace XXXX with RFC number and remove this note 610 5.2. YANG Namespace Registration 612 This document registers the following XML namespace URN in the "IETF 613 XML Registry", following the format defined in [RFC3688]: 615 URI: please assign urn:ietf:params:xml:ns:yang:ietf-constrained-yang- 616 library 618 Registrant Contact: The IESG. 620 XML: N/A, the requested URI is an XML namespace. 622 Reference: RFC XXXX 624 // RFC Ed.: replace XXXX with RFC number and remove this note 626 6. Security Considerations 628 The YANG module specified in this document defines a schema for data 629 that is designed to be accessed via network management protocols such 630 as NETCONF [RFC6241], RESTCONF [RFC8040] or CORECONF 631 [I-D.ietf-core-comi]. The lowest NETCONF layer is the secure 632 transport layer, and the mandatory-to-implement secure transport is 633 Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, 634 and the mandatory-to-implement secure transport is TLS [RFC8446]. 635 The lowest CORECONF layer is CoAP [RFC7252] and the mandatory-to- 636 implement security transport is any one of DTLS [RFC6347] and OSCORE 637 [RFC8613]. 639 The Network Configuration Access Control Model (NACM) [RFC8341] 640 provides the means to restrict access for particular NETCONF or 641 RESTCONF users to a preconfigured subset of all available NETCONF or 642 RESTCONF protocol operations and content. 644 Some of the readable data nodes in this YANG module may be considered 645 sensitive or vulnerable in some network environments. It is thus 646 important to control read access (e.g., via get, get-config, or 647 notification) to these data nodes. 649 Specifically, the 'module' list may help an attacker to identify the 650 server capabilities and server implementations with known bugs. 651 Server vulnerabilities may be specific to particular modules, module 652 revisions, module features, or even module deviations. This 653 information is included in each module entry. For example, if a 654 particular operation on a particular data node is known to cause a 655 server to crash or significantly degrade device performance, then the 656 module list information will help an attacker to identify server 657 implementations with such a defect, in order to launch a denial of 658 service attack on these devices. 660 7. Acknowledgments 662 The YANG module defined by this memo has been derived from an already 663 existing YANG module, ietf-yang-library [RFC8525], we will like to 664 thank the authors of this YANG module. A special thank also to Andy 665 Bierman for his initial recommendations for the creation of this YANG 666 module. The authors would also like to thank Tom Petch for his help 667 during the development of this document and his useful comments 668 during the review process. 670 8. References 672 8.1. Normative References 674 [I-D.ietf-core-comi] 675 Veillette, M., Stok, P., Pelov, A., Bierman, A., and I. 676 Petrov, "CoAP Management Interface (CORECONF)", draft- 677 ietf-core-comi-10 (work in progress), July 2020. 679 [I-D.ietf-core-sid] 680 Veillette, M., Pelov, A., and I. Petrov, "YANG Schema Item 681 iDentifier (YANG SID)", draft-ietf-core-sid-14 (work in 682 progress), July 2020. 684 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 685 Requirement Levels", BCP 14, RFC 2119, 686 DOI 10.17487/RFC2119, March 1997, 687 . 689 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 690 DOI 10.17487/RFC3688, January 2004, 691 . 693 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 694 and A. Bierman, Ed., "Network Configuration Protocol 695 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 696 . 698 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 699 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 700 . 702 [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer 703 Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, 704 January 2012, . 706 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 707 RFC 6991, DOI 10.17487/RFC6991, July 2013, 708 . 710 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 711 Application Protocol (CoAP)", RFC 7252, 712 DOI 10.17487/RFC7252, June 2014, 713 . 715 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 716 RFC 7950, DOI 10.17487/RFC7950, August 2016, 717 . 719 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 720 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 721 . 723 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 724 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 725 May 2017, . 727 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 728 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 729 . 731 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 732 Access Control Model", STD 91, RFC 8341, 733 DOI 10.17487/RFC8341, March 2018, 734 . 736 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 737 and R. Wilton, "Network Management Datastore Architecture 738 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 739 . 741 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 742 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 743 . 745 [RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., 746 and R. Wilton, "YANG Library", RFC 8525, 747 DOI 10.17487/RFC8525, March 2019, 748 . 750 [RFC8613] Selander, G., Mattsson, J., Palombini, F., and L. Seitz, 751 "Object Security for Constrained RESTful Environments 752 (OSCORE)", RFC 8613, DOI 10.17487/RFC8613, July 2019, 753 . 755 8.2. Informative References 757 [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for 758 Constrained-Node Networks", RFC 7228, 759 DOI 10.17487/RFC7228, May 2014, 760 . 762 Authors' Addresses 763 Michel Veillette (editor) 764 Trilliant Networks Inc. 765 610 Rue du Luxembourg 766 Granby, Quebec J2J 2V2 767 Canada 769 Email: michel.veillette@trilliantinc.com 771 Ivaylo Petrov (editor) 772 Acklio 773 1137A avenue des Champs Blancs 774 Cesson-Sevigne, Bretagne 35510 775 France 777 Email: ivaylo@ackl.io