idnits 2.17.1 draft-ietf-core-sid-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 30, 2017) is 2368 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: 'DONE' is mentioned on line 282, but not defined ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) == Outdated reference: A later version (-17) exists of draft-ietf-core-comi-01 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 7223 (Obsoleted by RFC 8343) -- Obsolete informational reference (is this intentional?): RFC 7277 (Obsoleted by RFC 8344) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). 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 A. Pelov, Ed. 5 Expires: May 3, 2018 Acklio 6 October 30, 2017 8 YANG Schema Item iDentifier (SID) 9 draft-ietf-core-sid-02 11 Abstract 13 YANG Schema Item iDentifiers (SID) are globally unique 64-bit 14 unsigned numbers used to identify YANG items. This document defines 15 the semantics, the registration, and assignment processes of SIDs. 16 To enable the implementation of these processes, this document also 17 defines a file format used to persist and publish assigned SIDs. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on May 3, 2018. 36 Copyright Notice 38 Copyright (c) 2017 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 55 3. ".sid" file lifecycle . . . . . . . . . . . . . . . . . . . . 4 56 4. ".sid" file format . . . . . . . . . . . . . . . . . . . . . 7 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 59 6.1. "SID mega-range" registry . . . . . . . . . . . . . . . . 10 60 6.1.1. IANA SID Mega-Range Registry . . . . . . . . . . . . 10 61 6.1.2. IANA "RFC SID range assignment" sub-registries . . . 11 62 6.2. "YANG module assignment" registry . . . . . . . . . . . . 12 63 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 65 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 66 8.2. Informative References . . . . . . . . . . . . . . . . . 13 67 Appendix A. ".sid" file example . . . . . . . . . . . . . . . . 14 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 70 1. Introduction 72 Some of the items defined in YANG [RFC7950] require the use of a 73 unique identifier. In both NETCONF [RFC6241] and RESTCONF [RFC8040], 74 these identifiers are implemented using names. To allow the 75 implementation of data models defined in YANG in constrained devices 76 and constrained networks, a more compact method to identify YANG 77 items is required. This compact identifier, called SID, is encoded 78 using a 64-bit unsigned integer. The following items are identified 79 using SIDs: 81 o identities 83 o data nodes 85 o RPCs and associated input(s) and output(s) 87 o actions and associated input(s) and output(s) 89 o notifications and associated information 91 o YANG modules, submodules and features 93 To minimize their size, SIDs are often represented as a difference 94 between the current SID and a reference SID. Such difference is 95 called "delta", shorthand for "delta-encoded SID". Conversion from 96 SIDs to deltas and back to SIDs is a stateless process. Each 97 protocol implementing deltas must unambiguously define the reference 98 SID for each YANG item. 100 SIDs are globally unique numbers, a registration system is used in 101 order to guarantee their uniqueness. SIDs are registered in blocks 102 called "SID ranges". 104 Assignment of SIDs to YANG items can be automated, the recommended 105 process to assign SIDs is as follows: 107 1. A tool extracts the different items defined for a specific YANG 108 module. 110 2. The list of items is ordered in alphabetical order by type and 111 label. Valid types and label formats are described within the 112 'ietf-sid-file' YANG module defined in Section 4. 114 3. SIDs are assigned sequentially from the entry point up to the 115 size of the registered SID range. This approach is recommended 116 to minimize the serialization overhead, especially when delta 117 encoding is implemented. 119 4. If the number of items exceeds the SID range(s) allocated to a 120 YANG module, an extra range is added for subsequent assignments. 122 SIDs are assigned permanently, items introduced by a new revision of 123 a YANG module are added to the list of SIDs already assigned. This 124 process can also be automated using the same method described above, 125 only unassigned YANG items are processed at step #3. 127 Section 3 provides more details about the registration process of 128 YANG modules and associated SIDs. To enable the implementation of 129 this registry, Section 4 defines a standard file format used to store 130 and publish SIDs. 132 2. Terminology and Notation 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in [RFC2119]. 138 The following terms are defined in [RFC7950]: 140 o action 142 o feature 143 o module 145 o notification 147 o RPC 149 o schema node 151 o schema tree 153 o submodule 155 This specification also makes use of the following terminology: 157 o delta : Difference between the current SID and a reference SID. A 158 reference SID is defined for each context for which deltas are 159 used. 161 o item: A schema node, an identity, a module, a submodule or a 162 feature defined using the YANG modeling language. 164 o path: A path is a string that identifies a schema node within the 165 schema tree. A path consists of the list of schema node 166 identifier(s) separated by slashes ("/"). Schema node 167 identifier(s) are always listed from the top-level schema node up 168 to the targeted schema node. (e.g. "/system-state/clock/current- 169 datetime") 171 o YANG Schema Item iDentifier (SID): Unsigned integer used to 172 identify different YANG items. 174 3. ".sid" file lifecycle 176 YANG is a language designed to model data sent between clients and 177 servers using one of the compatible protocol (e.g. NETCONF 178 [RFC6241], RESCONF [RFC8040] and CoMI [I-D.ietf-core-comi]). A YANG 179 module defines hierarchies of data, including configuration, state 180 data, RPCs, actions and notifications. 182 YANG modules are not necessary created in the context of constrained 183 applications. YANG modules can be implemented using NETCONF 184 [RFC6241] or RESTCONF [RFC8040] without the need to assign SIDs. 186 As needed, authors of YANG modules can assign SIDs to their YANG 187 modules. This process starts by the registration of a SID range. 188 Once a SID range is registered, the owner of this range assigns sub- 189 ranges to each YANG module in order to generate the associated ".sid" 190 files. Generation of ".sid" files SHOULD be performed using an 191 automated tool. 193 Registration of the .sid file associated to a YANG module is optional 194 but recommended to promote interoperability between devices and to 195 avoid duplicate allocation of SIDs to a single YANG module. 197 The following activity diagram summarizes the creation of a YANG 198 module and its associated .sid file. 200 +---------------+ 201 O | Creation of a | 202 -|- ->| YANG module | 203 / \ +---------------+ 204 | 205 V 206 /-------------\ 207 / Standardized \ yes 208 \ YANG module ? /-------------+ 209 \-------------/ | 210 | no | 211 V V 212 /-------------\ +---------------+ 213 / Constrained \ yes | SID range | 214 +-->\ application ? /---->| registration | 215 | \-------------/ +---------------+ 216 | | no | 217 | V V 218 | +---------------+ +---------------+ 219 +---| YANG module | | SID sub-range | 220 | update | | assignment | 221 +---------------+ +---------------+ 222 | 223 V 224 +---------------+ 225 | .sid file | 226 | generation | 227 +---------------+ 228 | 229 V 230 /-------------\ +---------------+ 231 / Publicly \ yes | YANG module | 232 \ available ? /---->| registration | 233 \-------------/ +---------------+ 234 | no | 235 +---------------------+ 236 | 237 [DONE] 239 Each time a YANG module or one of its imported module(s) or included 240 sub-module(s) is updated, the ".sid" file MAY need to be updated. 241 This update SHOULD also be performed using an automated tool. 243 If a new revision requires more SIDs than initially allocated, a new 244 SID range MUST be added to the "assignment-ranges" as defined in the 245 ".sid" file header. These extra SIDs are used for subsequent 246 assignements. 248 The following activity diagram summarizes the update of a YANG module 249 and its associated .sid file. 251 +---------------+ 252 O | Update of the | 253 -|- ->| YANG module | 254 / \ | or include(s) | 255 | or import(s) | 256 +---------------+ 257 | 258 V 259 /-------------\ +----------------+ 260 / More SIDs \ yes | Extra sub-range| 261 \ required ? /---->| assignment | 262 \-------------/ +----------------+ 263 | no | 264 +---------------------+ 265 | 266 V 267 +---------------+ 268 | .sid file | 269 | update based | 270 | on previous | 271 | .sid file | 272 +---------------+ 273 | 274 V 275 /-------------\ +---------------+ 276 / Publicly \ yes | YANG module | 277 \ available ? /---->| registration | 278 \-------------/ +---------------+ 279 | no | 280 +---------------------+ 281 | 282 [DONE] 284 4. ".sid" file format 286 ".sid" files are used to persist and publish SIDs assigned to the 287 different YANG items of a specific YANG module. The following YANG 288 module defined the structure of this file, encoding is performed 289 using the rules defined in [RFC7951]. 291 file "ietf-sid-file@2015-12-16.yang" 292 module ietf-sid-file { 293 namespace "urn:ietf:params:xml:ns:yang:ietf-sid-file"; 294 prefix sid; 296 organization 297 "IETF Core Working Group"; 299 contact 300 "Michel Veillette 301 303 Alexander Pelov 304 "; 306 description 307 "This module define the structure of the .sid files. 308 .sid files contains the identifiers (SIDs) assigned 309 to the different items defined in a YANG module."; 311 revision 2015-12-16 { 312 description 313 "Initial revision."; 314 reference 315 "RFC XXXX"; 316 // RFC Ed.: replace XXXX with RFC number assigned to 317 // draft-ietf-core-yang-cbor and remove this note 318 } 320 typedef yang-identifier { 321 type string { 322 length "1..max"; 323 pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*'; 324 pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*'; 325 } 326 description 327 "A YANG identifier string as defined by the 'identifier' 328 rule in Section 12 of RFC 6020."; 329 } 331 typedef revision-identifier { 332 type string { 333 pattern '\d{4}-\d{2}-\d{2}'; 334 } 335 description 336 "Represents a date in YYYY-MM-DD format."; 337 } 339 leaf module-name { 340 type yang-identifier; 341 description 342 "Name of the module associated with this .sid file."; 343 } 345 leaf module-revision { 346 type revision-identifier; 347 description 348 "Revision of the module associated with this .sid file. 349 This leaf is not present if no revision statement is 350 defined in the YANG module."; 351 } 353 list assigment-ranges { 354 key "entry-point"; 355 description 356 "Range(s) of SIDs available for assignment to the 357 different items defined by the associated module."; 359 leaf entry-point { 360 type uint64; 361 mandatory true; 362 description 363 "Lowest SID available for assignment."; 364 } 366 leaf size { 367 type uint16; 368 mandatory true; 369 description 370 "Number of SIDs available for assignment."; 371 } 372 } 374 list items { 375 key "type label"; 376 description 377 "List of items defined by the associated YANG module."; 379 leaf type { 380 type string { 381 pattern 'Module|Submodule|feature|' + 382 'identity$|node$|notification$|rpc$|action$'; 383 } 384 mandatory true; 385 description 386 "Item type assigned, this field can be set to: 387 - 'Module' 388 - 'Submodule' 389 - 'feature' 390 - 'identity' 391 - 'node' 392 - 'notification' 393 - 'rpc' 394 - 'action'"; 395 } 397 leaf label { 398 type string; 399 mandatory true; 400 description 401 "Label associated to this item, can be set to: 402 - a module name 403 - a submodule name 404 - a feature name 405 - a base identity encoded as 406 '/' 407 - an identity encoded as 408 '//' 409 - a data node path"; 410 } 412 leaf sid { 413 type uint64; 414 mandatory true; 415 description "Identifier assigned to this YANG item."; 416 } 417 } 418 } 419 421 5. Security Considerations 423 The security considerations of [RFC7049] and [RFC7950] apply. 425 This document defines a new type of identifier used to encode data 426 models defined in YANG [RFC7950]. As such, this identifier does not 427 contribute to any new security issues in addition of those identified 428 for the specific protocols or contexts for which it is used. 430 6. IANA Considerations 432 6.1. "SID mega-range" registry 434 The name of this registry is "SID mega-range". This registry is used 435 to delegate the management of block of SIDs for third party's (e.g. 436 SDO, registrar). 438 Each entry in this registry must include: 440 o The entry point (first entry) of the registered SID range. 442 o The size of the registered SID range. 444 o The contact information of the requesting organization including: 446 * Organization name 448 * Primary contact name, email address, and phone number 450 * Secondary contact name, email address, and phone number 452 The initial entry in this registry is allocated to IANA: 454 +-------------+---------+-------------------+ 455 | Entry Point | Size | Organization name | 456 +-------------+---------+-------------------+ 457 | 0 | 1000000 | IANA | 458 +-------------+---------+-------------------+ 460 The IANA policies for future additions to this registry are 461 "Hierarchical Allocation, Expert Review" [RFC5226]. Prior to a first 462 allocation, the requesting organization must demonstrate a functional 463 registry infrastructure. On subsequent allocation request(s), the 464 organization must demonstrate the exhaustion of the prior range. 465 These conditions need to be asserted by the assigned expert(s). 467 6.1.1. IANA SID Mega-Range Registry 469 The first million SIDs assigned to IANA is sub-divided as follow: 471 o The range of 0 to 999 is reserved for future extensions. The IANA 472 policy for this range is "IETF review" [RFC5226]. 474 o The range of 1000 to 59,999 is reserved for YANG modules defined 475 in RFCs. The IANA policy for future additions to this sub- 476 registry is "RFC required" [RFC5226]. Allocation within this 477 range requires publishing of the associated ".yang" and ".sid" 478 files in the YANG module registry. 480 o The range of 60,000 to 99,999 is reserved for experimental YANG 481 modules. This range MUST NOT be used in operational deployments 482 since these SIDs are not globally unique which limit their 483 interoperability. The IANA policy for this range is "Experimental 484 use" [RFC5226]. 486 o The range of 100,000 to 999,999 is reserved for standardized YANG 487 modules. The IANA policy for future additions to this sub- 488 registry is "Specification Required" [RFC5226]. Allocation within 489 this range requires publishing of the associated ".yang" and 490 ".sid" files in the YANG module registry. 492 +-------------+---------------+------------------------+ 493 | Entry Point | Size | IANA policy | 494 +-------------+---------------+------------------------+ 495 | 0 | 1,000 | IETF review | 496 | 1,000 | 59,000 | RFC required | 497 | 60,000 | 40,000 | Experimental use | 498 | 100,000 | 1,000,000,000 | Specification Required | 499 +-------------+---------------+------------------------+ 501 The size of SID range assigned to a YANG module should be at least 502 33% above the current number of YANG items. This headroom allows 503 assignment within the same range of new YANG items introduced by 504 subsequent revisions. A larger SID range size may be requested by 505 the authors if this recommendation is considered insufficient. It is 506 important to note that an extra SID range can be allocated to an 507 existing YANG module if the initial range is exhausted. 509 6.1.2. IANA "RFC SID range assignment" sub-registries 511 The name of this sub-registry is "RFC SID range assignment". This 512 sub-registry corresponds to the SID entry point 1000, size 59000. 513 Each entry in this sub-registry must include the SID range entry 514 point, the SID range size, the YANG module name, the RFC number. 516 Initial entries in this registry are as follows: 518 +------------+------+-----------------+-----------------------------+ 519 | Entry | Size | Module name | RFC number | 520 | Point | | | | 521 +------------+------+-----------------+-----------------------------+ 522 | 1000 | 100 | | Reserved for | 523 | | | | [I-D.ietf-core-comi] | 524 | 1100 | 400 | iana-if-type | [RFC7224] | 525 | 1500 | 100 | ietf-interfaces | [RFC7223] | 526 | 1600 | 100 | ietf-ip | [RFC7277] | 527 | 1700 | 100 | ietf-system | [RFC7317] | 528 +------------+------+-----------------+-----------------------------+ 530 6.2. "YANG module assignment" registry 532 The name of this registry is "YANG module assignment". This registry 533 is used to track which YANG modules have been assigned and the 534 specific YANG items assignment. Each entry in this sub-registry must 535 include: 537 o The YANG module name 539 o The associated ".yang" file(s) 541 o The associated ".sid" file 543 The validity of the ".yang" and ".sid" files added to this registry 544 MUST be verified. 546 o The syntax of the registered ".yang" and ".sid" files must be 547 valid. 549 o Each YANG item defined by the registered ".yang" file must have a 550 corresponding SID assigned in the ".sid" file. 552 o Each SID is assigned to a single YANG item, duplicate assignment 553 is not allowed. 555 o The SID range(s) defined in the ".sid" file must be unique, must 556 not conflict with any other SID ranges defined in already 557 registered ".sid" files. 559 o The ownership of the SID range(s) should be verify. 561 The IANA policy for future additions to this registry is "First Come 562 First Served" as described in [RFC5226]. 564 7. Acknowledgments 566 The authors would like to thank Andy Bierman, Carsten Bormann, 567 Abhinav Somaraju, Laurent Toutain and Randy Turner for their help 568 during the development of this document and their useful comments 569 during the review process. 571 8. References 573 8.1. Normative References 575 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 576 Requirement Levels", BCP 14, RFC 2119, 577 DOI 10.17487/RFC2119, March 1997, 578 . 580 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 581 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 582 October 2013, . 584 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 585 RFC 7950, DOI 10.17487/RFC7950, August 2016, 586 . 588 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 589 RFC 7951, DOI 10.17487/RFC7951, August 2016, 590 . 592 8.2. Informative References 594 [I-D.ietf-core-comi] 595 Veillette, M., Stok, P., Pelov, A., and A. Bierman, "CoAP 596 Management Interface", draft-ietf-core-comi-01 (work in 597 progress), July 2017. 599 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 600 IANA Considerations Section in RFCs", RFC 5226, 601 DOI 10.17487/RFC5226, May 2008, 602 . 604 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 605 and A. Bierman, Ed., "Network Configuration Protocol 606 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 607 . 609 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 610 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 611 . 613 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 614 RFC 7224, DOI 10.17487/RFC7224, May 2014, 615 . 617 [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", 618 RFC 7277, DOI 10.17487/RFC7277, June 2014, 619 . 621 [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for 622 System Management", RFC 7317, DOI 10.17487/RFC7317, August 623 2014, . 625 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 626 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 627 . 629 Appendix A. ".sid" file example 631 The following .sid file (ietf-system@2014-08-06.sid) have been 632 generated using the following yang modules: 634 o ietf-system@2014-08-06.yang 636 o ietf-yang-types@2013-07-15.yang 638 o ietf-inet-types@2013-07-15.yang 640 o ietf-netconf-acm@2012-02-22.yang 642 o iana-crypt-hash@2014-04-04.yang 644 { 645 "assignment-ranges": [ 646 { 647 "entry-point": 1700, 648 "size": 100 649 } 650 ], 651 "module-name": "ietf-system", 652 "module-revision": "2014-08-06", 653 "items": [ 654 { 655 "type": "Module", 656 "label": "ietf-system", 657 "sid": 1700 658 }, 659 { 660 "type": "feature", 661 "label": "authentication", 662 "sid": 1701 663 }, 664 { 665 "type": "feature", 666 "label": "dns-udp-tcp-port", 667 "sid": 1702 668 }, 669 { 670 "type": "feature", 671 "label": "local-users", 672 "sid": 1703 673 }, 674 { 675 "type": "feature", 676 "label": "ntp", 677 "sid": 1704 678 }, 679 { 680 "type": "feature", 681 "label": "ntp-udp-port", 682 "sid": 1705 683 }, 684 { 685 "type": "feature", 686 "label": "radius", 687 "sid": 1706 688 }, 689 { 690 "type": "feature", 691 "label": "radius-authentication", 692 "sid": 1707 693 }, 694 { 695 "type": "feature", 696 "label": "timezone-name", 697 "sid": 1708 698 }, 699 { 700 "type": "identity", 701 "label": "/authentication-method", 702 "sid": 1709 703 }, 704 { 705 "type": "identity", 706 "label": "/authentication-method/local-users", 707 "sid": 1710 708 }, 709 { 710 "type": "identity", 711 "label": "/authentication-method/radius", 712 "sid": 1711 713 }, 714 { 715 "type": "identity", 716 "label": "/radius-authentication-type", 717 "sid": 1712 718 }, 719 { 720 "type": "identity", 721 "label": "/radius-authentication-type/radius-chap", 722 "sid": 1713 723 }, 724 { 725 "type": "identity", 726 "label": "/radius-authentication-type/radius-pap", 727 "sid": 1714 728 }, 729 { 730 "type": "node", 731 "label": "/system", 732 "sid": 1715 733 }, 734 { 735 "type": "node", 736 "label": "/system-state", 737 "sid": 1716 738 }, 739 { 740 "type": "node", 741 "label": "/system-state/clock", 742 "sid": 1717 743 }, 744 { 745 "type": "node", 746 "label": "/system-state/clock/boot-datetime", 747 "sid": 1718 748 }, 749 { 750 "type": "node", 751 "label": "/system-state/clock/current-datetime", 752 "sid": 1719 753 }, 754 { 755 "type": "node", 756 "label": "/system-state/platform", 757 "sid": 1720 758 }, 759 { 760 "type": "node", 761 "label": "/system-state/platform/machine", 762 "sid": 1721 763 }, 764 { 765 "type": "node", 766 "label": "/system-state/platform/os-name", 767 "sid": 1722 768 }, 769 { 770 "type": "node", 771 "label": "/system-state/platform/os-release", 772 "sid": 1723 773 }, 774 { 775 "type": "node", 776 "label": "/system-state/platform/os-version", 777 "sid": 1724 778 }, 779 { 780 "type": "node", 781 "label": "/system/authentication", 782 "sid": 1725 783 }, 784 { 785 "type": "node", 786 "label": "/system/authentication/user", 787 "sid": 1726 788 }, 789 { 790 "type": "node", 791 "label": "/system/authentication/user-authentication-order", 792 "sid": 1727 793 }, 794 { 795 "type": "node", 796 "label": "/system/authentication/user/authorized-key", 797 "sid": 1728 798 }, 799 { 800 "type": "node", 801 "label": "/system/authentication/user/authorized-key/algorithm", 802 "sid": 1729 803 }, 804 { 805 "type": "node", 806 "label": "/system/authentication/user/authorized-key/key-data", 807 "sid": 1730 808 }, 809 { 810 "type": "node", 811 "label": "/system/authentication/user/authorized-key/name", 812 "sid": 1731 813 }, 814 { 815 "type": "node", 816 "label": "/system/authentication/user/name", 817 "sid": 1732 818 }, 819 { 820 "type": "node", 821 "label": "/system/authentication/user/password", 822 "sid": 1733 823 }, 824 { 825 "type": "node", 826 "label": "/system/clock", 827 "sid": 1734 828 }, 829 { 830 "type": "node", 831 "label": "/system/clock/timezone-name", 832 "sid": 1735 833 }, 834 { 835 "type": "node", 836 "label": "/system/clock/timezone-utc-offset", 837 "sid": 1736 838 }, 839 { 840 "type": "node", 841 "label": "/system/contact", 842 "sid": 1737 843 }, 844 { 845 "type": "node", 846 "label": "/system/dns-resolver", 847 "sid": 1738 848 }, 849 { 850 "type": "node", 851 "label": "/system/dns-resolver/options", 852 "sid": 1739 854 }, 855 { 856 "type": "node", 857 "label": "/system/dns-resolver/options/attempts", 858 "sid": 1740 859 }, 860 { 861 "type": "node", 862 "label": "/system/dns-resolver/options/timeout", 863 "sid": 1741 864 }, 865 { 866 "type": "node", 867 "label": "/system/dns-resolver/search", 868 "sid": 1742 869 }, 870 { 871 "type": "node", 872 "label": "/system/dns-resolver/server", 873 "sid": 1743 874 }, 875 { 876 "type": "node", 877 "label": "/system/dns-resolver/server/name", 878 "sid": 1744 879 }, 880 { 881 "type": "node", 882 "label": "/system/dns-resolver/server/udp-and-tcp", 883 "sid": 1745 884 }, 885 { 886 "type": "node", 887 "label": "/system/dns-resolver/server/udp-and-tcp/address", 888 "sid": 1746 889 }, 890 { 891 "type": "node", 892 "label": "/system/dns-resolver/server/udp-and-tcp/port", 893 "sid": 1747 894 }, 895 { 896 "type": "node", 897 "label": "/system/hostname", 898 "sid": 1748 899 }, 900 { 901 "type": "node", 902 "label": "/system/location", 903 "sid": 1749 904 }, 905 { 906 "type": "node", 907 "label": "/system/ntp", 908 "sid": 1750 909 }, 910 { 911 "type": "node", 912 "label": "/system/ntp/enabled", 913 "sid": 1751 914 }, 915 { 916 "type": "node", 917 "label": "/system/ntp/server", 918 "sid": 1752 919 }, 920 { 921 "type": "node", 922 "label": "/system/ntp/server/association-type", 923 "sid": 1753 924 }, 925 { 926 "type": "node", 927 "label": "/system/ntp/server/iburst", 928 "sid": 1754 929 }, 930 { 931 "type": "node", 932 "label": "/system/ntp/server/name", 933 "sid": 1755 934 }, 935 { 936 "type": "node", 937 "label": "/system/ntp/server/prefer", 938 "sid": 1756 939 }, 940 { 941 "type": "node", 942 "label": "/system/ntp/server/udp", 943 "sid": 1757 944 }, 945 { 946 "type": "node", 947 "label": "/system/ntp/server/udp/address", 948 "sid": 1758 949 }, 950 { 951 "type": "node", 952 "label": "/system/ntp/server/udp/port", 953 "sid": 1759 954 }, 955 { 956 "type": "node", 957 "label": "/system/radius", 958 "sid": 1760 959 }, 960 { 961 "type": "node", 962 "label": "/system/radius/options", 963 "sid": 1761 964 }, 965 { 966 "type": "node", 967 "label": "/system/radius/options/attempts", 968 "sid": 1762 969 }, 970 { 971 "type": "node", 972 "label": "/system/radius/options/timeout", 973 "sid": 1763 974 }, 975 { 976 "type": "node", 977 "label": "/system/radius/server", 978 "sid": 1764 979 }, 980 { 981 "type": "node", 982 "label": "/system/radius/server/authentication-type", 983 "sid": 1765 984 }, 985 { 986 "type": "node", 987 "label": "/system/radius/server/name", 988 "sid": 1766 989 }, 990 { 991 "type": "node", 992 "label": "/system/radius/server/udp", 993 "sid": 1767 994 }, 995 { 996 "type": "node", 997 "label": "/system/radius/server/udp/address", 998 "sid": 1768 999 }, 1000 { 1001 "type": "node", 1002 "label": "/system/radius/server/udp/authentication-port", 1003 "sid": 1769 1004 }, 1005 { 1006 "type": "node", 1007 "label": "/system/radius/server/udp/shared-secret", 1008 "sid": 1770 1009 }, 1010 { 1011 "type": "rpc", 1012 "label": "/set-current-datetime", 1013 "sid": 1771 1014 }, 1015 { 1016 "type": "rpc", 1017 "label": "/set-current-datetime/input/current-datetime", 1018 "sid": 1772 1019 }, 1020 { 1021 "type": "rpc", 1022 "label": "/system-restart", 1023 "sid": 1773 1024 }, 1025 { 1026 "type": "rpc", 1027 "label": "/system-shutdown", 1028 "sid": 1774 1029 } 1030 ] 1031 } 1033 Authors' Addresses 1035 Michel Veillette (editor) 1036 Trilliant Networks Inc. 1037 610 Rue du Luxembourg 1038 Granby, Quebec J2J 2V2 1039 Canada 1041 Phone: +14503750556 1042 Email: michel.veillette@trilliantinc.com 1043 Alexander Pelov (editor) 1044 Acklio 1045 2bis rue de la Chataigneraie 1046 Cesson-Sevigne, Bretagne 35510 1047 France 1049 Email: a@ackl.io