idnits 2.17.1 draft-ietf-core-yang-library-02.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 (July 10, 2020) is 1379 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 700, 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: January 11, 2021 Acklio 6 July 10, 2020 8 Constrained YANG Module Library 9 draft-ietf-core-yang-library-02 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 January 11, 2021. 35 Copyright Notice 37 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . 13 63 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 65 8.1. Normative References . . . . . . . . . . . . . . . . . . 14 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 "This module provides information about the YANG modules, 256 datastores, and datastore schemas implemented by a 257 constrained network management server. 259 Copyright (c) 2018 IETF Trust and the persons identified as 260 authors of the code. All rights reserved. 262 Redistribution and use in source and binary forms, with or 263 without modification, is permitted pursuant to, and subject 264 to the license terms contained in, the Simplified BSD License 265 set forth in Section 4.c of the IETF Trust's Legal Provisions 266 Relating to IETF Documents 267 (http://trustee.ietf.org/license-info). 269 This version of this YANG module is part of RFC XXXX; see 270 the RFC itself for full legal notices."; 272 // RFC Editor: Please replace XXXX with RFC number and remove this note 274 revision 2019-03-28 { 275 description 276 "Second revision."; 277 reference 278 "RFC XXXX: Constrained YANG Module Library"; 279 // RFC Editor: Please replace XXXX with RFC number and remove this note 280 } 282 /* 283 * Typedefs 284 */ 286 typedef revision-identifier { 287 type binary { 288 length "4"; 289 } 290 description 291 "Revision date encoded as a binary string, each nibble 292 representing a digit of the revision date. For example, 293 revision 2018-09-21 is encoded as 0x20 0x18 0x09 0x21."; 294 } 296 /* 297 * Groupings 298 */ 300 grouping module-identification-leafs { 301 description 302 "Parameters for identifying YANG modules and submodules."; 304 leaf identifier { 305 type sid:sid; 306 mandatory true; 307 description 308 "SID assigned to this module or submodule."; 309 } 310 leaf revision { 311 type revision-identifier; 312 description 313 "The YANG module or submodule revision date. If no 314 revision statement is present in the YANG module 315 or submodule, this leaf is not instantiated."; 316 } 317 } 319 grouping location-leaf-list { 320 description 321 "Common location leaf list parameter for modules and 322 submodules."; 324 leaf-list location { 325 type inet:uri; 326 description 327 "Contains a URL that represents the YANG schema resource 328 for this module or submodule. 330 This leaf is present in the model to keep the alignment 331 with 'ietf-yang-library'. Support of this leaf in 332 constrained devices is not necessarily required, nor 333 expected. It is recommended that clients used the module 334 or sub-module SID as the handle used to retrieve the 335 corresponding YANG module"; 337 } 338 } 340 grouping implementation-parameters { 341 description 342 "Parameters for describing the implementation of a module."; 344 leaf-list feature { 345 type sid:sid; 346 description 347 "List of all YANG feature names from this module that are 348 supported by the server, regardless whether they are 349 defined in the module or any included submodule."; 350 } 351 leaf-list deviation { 352 type leafref { 353 path "../../module/identifier"; 354 } 355 description 356 "List of all YANG deviation modules used by this server to 357 modify the conformance of the module associated with this 358 entry. Note that the same module can be used for 359 deviations for multiple modules, so the same entry MAY 360 appear within multiple 'module' entries. 362 This reference MUST NOT (directly or indirectly) 363 refer to the module being deviated. 365 Robust clients may want to make sure that they handle a 366 situation where a module deviates itself (directly or 367 indirectly) gracefully."; 368 } 369 } 371 grouping module-set-parameters { 372 description 373 "A set of parameters that describe a module set."; 375 leaf index { 376 type uint8; 377 description 378 "An arbitrary number assigned of the module set."; 379 } 380 list module { 381 key "identifier"; 382 description 383 "An entry in this list represents a module implemented 384 by the server, as per RFC 7950 section 5.6.5, with a 385 particular set of supported features and deviations."; 386 reference 387 "RFC 7950: The YANG 1.1 Data Modeling Language."; 389 uses module-identification-leafs; 391 leaf namespace { 392 type inet:uri; 393 description 394 "The XML namespace identifier for this module. 395 This leaf is present in the model to keep the alignment 396 with 'ietf-yang-library'. Support of this leaf in 397 constrained devices is not required, nor expected."; 398 } 400 uses location-leaf-list; 402 list submodule { 403 key "identifier"; 404 description 405 "Each entry represents one submodule within the parent 406 module."; 407 uses module-identification-leafs; 408 uses location-leaf-list; 409 } 411 uses implementation-parameters; 412 } 413 list import-only-module { 414 key "identifier revision"; 415 description 416 "An entry in this list indicates that the server imports 417 reusable definitions from the specified revision of the 418 module, but does not implement any protocol accessible 419 objects from this revision. 421 Multiple entries for the same module name MAY exist. 422 This can occur if multiple modules import the same 423 module, but specify different revision-dates in the 424 import statements."; 426 leaf identifier { 427 type sid:sid; 428 description 429 "The YANG module name."; 430 } 431 leaf revision { 432 type union { 433 type revision-identifier; 434 type string { 435 length 0; 436 } 437 } 438 description 439 "The YANG module revision date."; 440 } 441 leaf namespace { 442 type inet:uri; 443 description 444 "The XML namespace identifier for this module. 445 This leaf is present in the model to keep the alignment 446 with 'ietf-yang-library'. Support of this leaf in 447 constrained devices is not required, nor expected."; 448 } 450 uses location-leaf-list; 452 list submodule { 453 key "identifier"; 454 description 455 "Each entry represents one submodule within the 456 parent module."; 458 uses module-identification-leafs; 459 uses location-leaf-list; 460 } 461 } 462 } 464 grouping yang-library-parameters { 465 description 466 "The YANG library data structure is represented as a grouping 467 so it can be reused in configuration or another monitoring 468 data structure."; 470 list module-set { 471 key index; 472 description 473 "A set of modules that may be used by one or more schemas. 475 A module set does not have to be referentially complete, 476 i.e., it may define modules that contain import statements 477 for other modules not included in the module set."; 479 uses module-set-parameters; 480 } 481 list schema { 482 key "index"; 483 description 484 "A datastore schema that may be used by one or more 485 datastores. 487 The schema must be valid and referentially complete, 488 i.e., it must contain modules to satisfy all used import 489 statements for all modules specified in the schema."; 491 leaf index { 492 type uint8; 493 description 494 "An arbitrary reference number assigned to the schema."; 495 } 496 leaf-list module-set { 497 type leafref { 498 path "../../module-set/index"; 499 } 500 description 501 "A set of module-sets that are included in this schema. 502 If a non import-only module appears in multiple module 503 sets, then the module revision and the associated 504 features and deviations must be identical."; 505 } 506 } 508 list datastore { 509 key "identifier"; 510 description 511 "A datastore supported by this server. 513 Each datastore indicates which schema it supports. 515 The server MUST instantiate one entry in this list 516 per specific datastore it supports. 518 Each datstore entry with the same datastore schema 519 SHOULD reference the same schema."; 521 leaf identifier { 522 type ds:datastore-ref; 523 description 524 "The identity of the datastore."; 525 } 526 leaf schema { 527 type leafref { 528 path "../../schema/index"; 530 } 531 mandatory true; 532 description 533 "A reference to the schema supported by this datastore. 534 All non import-only modules of the schema are 535 implementedwith their associated features and 536 deviations."; 537 } 538 } 539 } 541 /* 542 * Top-level container 543 */ 545 container yang-library { 546 config false; 547 description 548 "Container holding the entire YANG library of this server."; 550 uses yang-library-parameters; 552 leaf checksum { 553 type binary; 554 mandatory true; 555 description 556 "A server-generated checksum or digest of the contents of 557 the 'yang-library' tree. The server MUST change the 558 value of this leaf if the information represented by 559 the 'yang-library' tree, except 'yang-library/checksum', 560 has changed."; 561 } 562 } 564 /* 565 * Notifications 566 */ 568 notification yang-library-update { 569 description 570 "Generated when any YANG library information on the 571 server has changed."; 573 leaf checksum { 574 type leafref { 575 path "/yanglib:yang-library/yanglib:checksum"; 576 } 577 mandatory true; 578 description 579 "Contains the YANG library checksum or digest for the 580 updated YANG library at the time the notification is 581 generated."; 582 } 583 } 584 } 585 587 5. IANA Considerations 589 5.1. YANG Module Registration 591 This document registers one YANG module in the YANG Module Names 592 registry [RFC7950]. 594 name: ietf-constrained-yang-library 596 namespace: urn:ietf:params:xml:ns:yang:ietf-constrained-yang-library 598 prefix: lib 600 reference: RFC XXXX 602 // RFC Ed.: replace XXXX with RFC number and remove this note 604 5.2. YANG Namespace Registration 606 This document registers the following XML namespace URN in the "IETF 607 XML Registry", following the format defined in [RFC3688]: 609 URI: please assign urn:ietf:params:xml:ns:yang:ietf-constrained-yang- 610 library 612 Registrant Contact: The IESG. 614 XML: N/A, the requested URI is an XML namespace. 616 Reference: RFC XXXX 618 // RFC Ed.: replace XXXX with RFC number and remove this note 620 6. Security Considerations 622 The YANG module specified in this document defines a schema for data 623 that is designed to be accessed via network management protocols such 624 as NETCONF [RFC6241], RESTCONF [RFC8040] or CORECONF 625 [I-D.ietf-core-comi]. The lowest NETCONF layer is the secure 626 transport layer, and the mandatory-to-implement secure transport is 627 Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, 628 and the mandatory-to-implement secure transport is TLS [RFC8446]. 629 The lowest CORECONF layer is CoAP [RFC7252] and the mandatory-to- 630 implement security transport is any one of DTLS [RFC6347] and OSCORE 631 [RFC8613]. 633 The Network Configuration Access Control Model (NACM) [RFC8341] 634 provides the means to restrict access for particular NETCONF or 635 RESTCONF users to a preconfigured subset of all available NETCONF or 636 RESTCONF protocol operations and content. 638 Some of the readable data nodes in this YANG module may be considered 639 sensitive or vulnerable in some network environments. It is thus 640 important to control read access (e.g., via get, get-config, or 641 notification) to these data nodes. 643 Specifically, the 'module' list may help an attacker to identify the 644 server capabilities and server implementations with known bugs. 645 Server vulnerabilities may be specific to particular modules, module 646 revisions, module features, or even module deviations. This 647 information is included in each module entry. For example, if a 648 particular operation on a particular data node is known to cause a 649 server to crash or significantly degrade device performance, then the 650 module list information will help an attacker to identify server 651 implementations with such a defect, in order to launch a denial of 652 service attack on these devices. 654 7. Acknowledgments 656 The YANG module defined by this memo has been derived from an already 657 existing YANG module, ietf-yang-library [RFC8525], we will like to 658 thank the authors of this YANG module. A special thank also to Andy 659 Bierman for his initial recommendations for the creation of this YANG 660 module. The authors would also like to thank Tom Petch for his help 661 during the development of this document and his useful comments 662 during the review process. 664 8. References 666 8.1. Normative References 668 [I-D.ietf-core-comi] 669 Veillette, M., Stok, P., Pelov, A., Bierman, A., and I. 670 Petrov, "CoAP Management Interface (CORECONF)", draft- 671 ietf-core-comi-10 (work in progress), July 2020. 673 [I-D.ietf-core-sid] 674 Veillette, M., Pelov, A., and I. Petrov, "YANG Schema Item 675 iDentifier (YANG SID)", draft-ietf-core-sid-14 (work in 676 progress), July 2020. 678 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 679 Requirement Levels", BCP 14, RFC 2119, 680 DOI 10.17487/RFC2119, March 1997, 681 . 683 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 684 DOI 10.17487/RFC3688, January 2004, 685 . 687 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 688 and A. Bierman, Ed., "Network Configuration Protocol 689 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 690 . 692 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 693 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 694 . 696 [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer 697 Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, 698 January 2012, . 700 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 701 RFC 6991, DOI 10.17487/RFC6991, July 2013, 702 . 704 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 705 Application Protocol (CoAP)", RFC 7252, 706 DOI 10.17487/RFC7252, June 2014, 707 . 709 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 710 RFC 7950, DOI 10.17487/RFC7950, August 2016, 711 . 713 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 714 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 715 . 717 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 718 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 719 May 2017, . 721 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 722 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 723 . 725 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 726 Access Control Model", STD 91, RFC 8341, 727 DOI 10.17487/RFC8341, March 2018, 728 . 730 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 731 and R. Wilton, "Network Management Datastore Architecture 732 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 733 . 735 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 736 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 737 . 739 [RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., 740 and R. Wilton, "YANG Library", RFC 8525, 741 DOI 10.17487/RFC8525, March 2019, 742 . 744 [RFC8613] Selander, G., Mattsson, J., Palombini, F., and L. Seitz, 745 "Object Security for Constrained RESTful Environments 746 (OSCORE)", RFC 8613, DOI 10.17487/RFC8613, July 2019, 747 . 749 8.2. Informative References 751 [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for 752 Constrained-Node Networks", RFC 7228, 753 DOI 10.17487/RFC7228, May 2014, 754 . 756 Authors' Addresses 758 Michel Veillette (editor) 759 Trilliant Networks Inc. 760 610 Rue du Luxembourg 761 Granby, Quebec J2J 2V2 762 Canada 764 Email: michel.veillette@trilliantinc.com 765 Ivaylo Petrov (editor) 766 Acklio 767 1137A avenue des Champs Blancs 768 Cesson-Sevigne, Bretagne 35510 769 France 771 Email: ivaylo@ackl.io