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