idnits 2.17.1 draft-ietf-core-sid-00.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 7 instances of too long lines in the document, the longest one being 33 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 26, 2016) is 2738 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: 'I-D.ietf-netconf-restconf' is defined on line 539, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 544, but no explicit reference was found in the text ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) == Outdated reference: A later version (-18) exists of draft-ietf-netconf-restconf-17 -- 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: 2 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force A. Somaraju, Ed. 3 Internet-Draft Tridonic GmbH & Co KG 4 Intended status: Standards Track M. Veillette, Ed. 5 Expires: April 29, 2017 Trilliant Networks Inc. 6 A. Pelov 7 Acklio 8 R. Turner 9 Landis+Gyr 10 A. Minaburo 11 Acklio 12 October 26, 2016 14 YANG Schema Item iDentifier (SID) 15 draft-ietf-core-sid-00 17 Abstract 19 YANG Schema Item iDentifiers (SID) are used to identify different 20 YANG items using a numeric identifier. This document defines the 21 registration and assignment processes of SIDs. To enable the 22 implementation of these processes, this document also defines a file 23 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 April 29, 2017. 42 Copyright Notice 44 Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . 2 61 3. YANG Schema Item iDentifier (SID) . . . . . . . . . . . . . . 3 62 4. ".sid" file lifecycle . . . . . . . . . . . . . . . . . . . . 4 63 5. ".sid" file format . . . . . . . . . . . . . . . . . . . . . 6 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 65 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 66 7.1. "SID" range registry . . . . . . . . . . . . . . . . . . 9 67 7.2. YANG module registry . . . . . . . . . . . . . . . . . . 11 68 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 71 9.2. Informative References . . . . . . . . . . . . . . . . . 12 72 Appendix A. ".sid" file example . . . . . . . . . . . . . . . . 13 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 75 1. Introduction 77 This document describes the registries required to manage SIDs and a 78 file format used to persist and publish the assigned SIDs. 80 2. Terminology and Notation 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in [RFC2119]. 86 The following terms are defined in [RFC7950]: 88 o action 90 o feature 92 o module 94 o notification 96 o RPC 97 o schema node 99 o schema tree 101 o submodule 103 This specification also makes use of the following terminology: 105 o identifier: An identifier embodies the information required to 106 distinguish what is being identified from all other things within 107 its scope of identification. 109 o delta : Difference between the current SID and a reference SID. A 110 reference SID is defined for each context for which deltas are 111 used. 113 o item: A schema node, an identity, a module, a submodule or a 114 feature defined using the YANG modeling language. 116 o path: A path is a string that identifies a schema node within the 117 schema tree. A path consists of the list of schema node 118 identifier(s) separated by slashes ("/"). Schema node 119 identifier(s) are always listed from the top-level schema node up 120 to the targeted schema node. (e.g. "/system-state/clock/current- 121 datetime") 123 3. YANG Schema Item iDentifier (SID) 125 Some of the items defined in YANG [RFC7950] require the use of a 126 unique identifier. In both NETCONF and RESTCONF, these identifiers 127 are implemented using names. To allow the implementation of data 128 models defined in YANG in constrained devices and constrained 129 networks, a more compact method to identify YANG items is required. 131 This compact identifier, called SID, is encoded using an unsigned 132 integer. To minimize its size, SIDs are often implemented using a 133 delta from a reference SID and the current SID. To guaranty the 134 uniqueness of each assigned SID, SID ranges MUST be registered. 135 Section 7.1 provide more details about the registration process of 136 SID range(s). 138 To avoid duplicate assignment of SIDs, the registration of the SIDs 139 assigned to YANG module(s) is recommended. Section 7.2 provide more 140 details about the registration process of YANG modules. 142 The following items are identified using SIDs: 144 o identities 145 o data nodes 147 o RPCs and associated input(s) and output(s) 149 o actions and associated input(s) and output(s) 151 o notifications and associated information 153 o YANG modules, submodules and features 155 Assignment of SIDs can be automated, the recommended process to 156 assign SIDs is as follows: 158 o A tool extracts the different items defined for a specific YANG 159 module. 161 o The list of items is ordered by type and label. 163 o SIDs are assigned sequentially for the entry point up to the size 164 of the registered SID range. This approach is recommended to 165 minimize the serialization overhead, especially when delta 166 encoding is implemented. 168 o If the number of items exceeds the SID range(s) allocated to a 169 YANG module, an extra range is added for subsequent assignments. 171 SIDs are assigned permanently, items introduced by a new revision of 172 a YANG module are added to the list of SIDs already assigned. This 173 process can also be automated using the same method described above 174 except that the assignment need to be restarted from the highest SID 175 already assigned. 177 Section 5 defines a standard file format used to store and publish 178 SIDs. 180 4. ".sid" file lifecycle 182 The following activity diagram summarize the life cycle of ".sid" 183 files. 185 +---------------+ 186 O | Creation of a | 187 -|- ->| YANG module | 188 / \ +---------------+ 189 | 190 V 191 /-------------\ 192 / Standardized \ yes 193 \ YANG module ? /-------------+ 194 \-------------/ | 195 | no | 196 V V 197 /-------------\ +---------------+ 198 / Constrained \ yes | SID range | 199 +-->\ application ? /---->| registration | 200 | \-------------/ +---------------+ 201 | | no | 202 | V V 203 | +---------------+ +---------------+ 204 +---| YANG module | | .sid file | 205 | update | | generation | 206 +---------------+ +---------------+ 207 | 208 V 209 /-------------\ +---------------+ 210 / Publicly \ yes | YANG module | 211 +------------>\ available ? /---->| registration | 212 | \-------------/ +---------------+ 213 | | no | 214 | +---------------------+ 215 | V 216 +---------------+ +---------------+ 217 | .sid file | | Update of the | 218 | update based | | YANG module | 219 | on previous | | or include(s) | 220 | .sid file | | or import(s) | 221 +---------------+ +---------------+ 222 ^ | 223 | V 224 | /-------------\ +---------------+ 225 | / More SIDs \ yes | Extra range | 226 | \ required ? /---->| assignment | 227 | \-------------/ +---------------+ 228 | | no | 229 +---------------------+---------------------+ 231 YANG modules are not necessary created in the context of constrained 232 applications. YANG modules can be implemented using NETCONF or 233 RESTCONF without the need to assign SIDs. 235 As needed, authors of YANG modules can assign SIDs to their modules. 236 This process starts by the registration of a SID range. Once a SID 237 range is registered, the owner of this range assigns sub-ranges to 238 each YANG module in order to generate the associated ".sid" files. 239 Generation of ".sid" files SHOULD be performed using an automated 240 tool. 242 Registration of the .sid file associated to a YANG module is optional 243 but recommended to promote interoperability between devices and to 244 avoid duplicate allocation of SIDs to a single YANG module. 246 Each time a YANG module or one of its imported module(s) or included 247 sub-module(s) is updated, the ".sid" file MAY need to be updated. 248 This update SHOULD also be performed using an automated tool. 250 If a new revision requires more SIDs than initially allocated, a new 251 SID range MUST be added to the assignment ranges as defined in the 252 ".sid" file header. These extra SIDs are used for subsequent 253 assignments. 255 5. ".sid" file format 257 ".sid" files are used to persist and publish SIDs assigned to the 258 different YANG items of a specific YANG module. The following YANG 259 module defined the structure of this file, encoding is performed 260 using the rules defined in [RFC7951]. 262 file "ietf-sid-file@2015-12-16.yang" 263 module ietf-sid-file { 264 namespace "urn:ietf:params:xml:ns:yang:ietf-sid-file"; 265 prefix sid; 267 organization 268 "IETF Core Working Group"; 270 contact 271 "Ana Minaburo 272 274 Alexander Pelov 275 277 Abhinav Somaraju 278 279 Laurent Toutain 280 282 Randy Turner 283 285 Michel Veillette 286 "; 288 description 289 "This module define the structure of the .sid files. 290 .sid files contains the identifiers (SIDs) assigned 291 to the different items defined in a YANG module. 292 SIDs are used to encode a data model defined in YANG 293 using CBOR."; 295 revision 2015-12-16 { 296 description 297 "Initial revision."; 298 reference 299 "RFC XXXX"; 300 // RFC Ed.: replace XXXX with RFC number assigned to draft-ietf-core-yang-cbor and remove this note 301 } 303 typedef yang-identifier { 304 type string { 305 length "1..max"; 306 pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*'; 307 pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*'; 308 } 309 description 310 "A YANG identifier string as defined by the 'identifier' 311 rule in Section 12 of RFC 6020."; 312 } 314 typedef revision-identifier { 315 type string { 316 pattern '\d{4}-\d{2}-\d{2}'; 317 } 318 description 319 "Represents a date in YYYY-MM-DD format."; 320 } 322 leaf module-name { 323 type yang-identifier; 324 description 325 "Name of the module associated with this .sid file."; 326 } 327 leaf module-revision { 328 type revision-identifier; 329 description 330 "Revision of the module associated with this .sid file. 331 This leaf is not present if no revision statement is 332 defined in the YANG module."; 333 } 335 list assigment-ranges { 336 key "entry-point"; 337 description 338 "Range(s) of SIDs available for assignment to the 339 different items defined by the associated module."; 341 leaf entry-point { 342 type uint32; 343 mandatory true; 344 description 345 "Lowest SID available for assignment."; 346 } 348 leaf size { 349 type uint16; 350 mandatory true; 351 description 352 "Number of SIDs available for assignment."; 353 } 354 } 356 list items { 357 key "type label"; 358 description 359 "List of items defined by the associated YANG module."; 361 leaf type { 362 type string { 363 pattern 'Module|Submodule|feature|' + 364 'identity$|node$|notification$|rpc$|action$'; 365 } 366 mandatory true; 367 description 368 "Item type assigned, this field can be set to: 369 - 'Module' 370 - 'Submodule' 371 - 'feature' 372 - 'identity' 373 - 'node' 374 - 'notification' 375 - 'rpc' 376 - 'action'"; 377 } 379 leaf label { 380 type string; 381 mandatory true; 382 description 383 "Label associated to this item, can be set to: 384 - a module name 385 - a submodule name 386 - a feature name 387 - a base identity encoded as '/' 388 - an identity encoded as '//' 389 - a schema node path"; 390 } 392 leaf sid { 393 type uint32; 394 mandatory true; 395 description "Identifier assigned to this YANG item."; 396 } 397 } 398 } 399 401 6. Security Considerations 403 The security considerations of [RFC7049] and [RFC7950] apply. 405 This document defines an new type of identifier used to encode data 406 models defined in YANG [RFC7950]. As such, this identifier does not 407 contribute to any new security issues in addition of those identified 408 for the specific protocols or contexts for which it is used. 410 7. IANA Considerations 412 7.1. "SID" range registry 414 IANA is requested to create a registry for YANG Schema Item 415 iDentifier (SID) ranges. This registry needs to guarantee that the 416 ranges registered do not overlap. The registry SHALL record for each 417 entry: 419 o The entry point (first entry) of the registered SID range. 421 o The size of the registered SID range. 423 o The contact information of the owner of the range such as name, 424 email address, and phone number. 426 The IANA policy for this registry is split into four tiers as 427 follows: 429 o The range of 0 to 999 and 0x40000000 to 0xFFFFFFFFFFFFFFFF are 430 reserved for future extensions of this protocol. Allocation 431 within these ranges require IETF review or IESG approval. 433 o The range of 1000 to 59999 is reserved for standardized YANG 434 modules. Allocation within this range requires publishing of the 435 associated ".yang" and ".sid" files. (Specification required.) 437 o The range of 60000 to 99999 is reserved for experimental YANG 438 modules. Use of this range MUST NOT be used in operational 439 deployments since these SIDs are not globally unique which limit 440 their interoperability. 442 o The range of 100000 to 0x3FFFFFFF is available on a first come 443 first served basis. The only information required from the 444 registrant is a valid contact information. The recommended size 445 of the SID ranges allocated is 1,000 for private use and 10,000 446 for standard development organizations (SDOs). Registrants MAY 447 request fewer or more SIDs based on their expected, sat needs. 448 Allocation of a significantly larger SID range MAY required IETF 449 review or IESG approval. IANA MAY delegate this registration 450 process to one or multiple sub-registries. The recommended size 451 of the SID range allocation for a sub-registry is 1,000,000. 453 +------------+-----------------+------------------------------------+ 454 | Entry | Size | Registration Procedures | 455 | Point | | | 456 +------------+-----------------+------------------------------------+ 457 | 0 | 1,000 | IETF review or IESG approval | 458 | 1,000 | 59,000 | Specification and associated | 459 | | | ".yang" and ".sid" files required | 460 | 60,000 | 40,000 | Experimental use | 461 | 100,000 | 0x3ffe7960 | Contact information is required. | 462 | | | Registration of the module name(s) | 463 | | | and associated ".yang" and ".sid" | 464 | | | files are optional. | 465 | 0x40000000 | 2^64-0x40000000 | Specification required, expert | 466 | | | review | 467 +------------+-----------------+------------------------------------+ 469 7.2. YANG module registry 471 Each registered SID range can be used to assign SIDs to one or more 472 YANG modules. To track which YANG modules have been assigned and to 473 avoid duplicate allocation, IANA is requested to provide a method to 474 register and query the following information: 476 o The YANG module name 478 o The contact information of the author 480 o The specification reference 482 o The associated ".yang" file(s) (Optional) 484 o The associated ".sid" file (Optional) 486 Registration of YANG modules is optional. When a YANG module is 487 registered, the registrant MUST provide the module name and contact 488 information and/or a specification reference. 490 The registration of the associated ".yang" and ".sid" files is 491 optional. When provided, the validity of the files MUST be verified. 492 This can be accomplished by a YANG validation tool specially modified 493 to support ".sid" file verification. The SID range specified within 494 the ".sid" file SHOULD also be checked against the "SID" range 495 registry (Section 7.1) and against the other YANG modules registered 496 to detect any duplicate use of SIDs. 498 Initial entries in this registry are as follows: 500 +-------------+------+-----------------+-------------------+ 501 | Entry Point | Size | Module name | Reference | 502 +-------------+------+-----------------+-------------------+ 503 | 1000 | 100 | | Reserved for CoMI | 504 | 1100 | 400 | iana-if-type | [RFC7224] | 505 | 1500 | 100 | ietf-interfaces | [RFC7223] | 506 | 1600 | 100 | ietf-ip | [RFC7277] | 507 | 1700 | 100 | ietf-system | [RFC7317] | 508 +-------------+------+-----------------+-------------------+ 510 8. Acknowledgments 512 The authors would like to thank Carsten Bormann for his help during 513 the development of this document and his useful comments during the 514 review process. 516 9. References 518 9.1. Normative References 520 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 521 Requirement Levels", BCP 14, RFC 2119, 522 DOI 10.17487/RFC2119, March 1997, 523 . 525 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 526 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 527 October 2013, . 529 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 530 RFC 7950, DOI 10.17487/RFC7950, August 2016, 531 . 533 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 534 RFC 7951, DOI 10.17487/RFC7951, August 2016, 535 . 537 9.2. Informative References 539 [I-D.ietf-netconf-restconf] 540 Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 541 Protocol", draft-ietf-netconf-restconf-17 (work in 542 progress), September 2016. 544 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 545 and A. Bierman, Ed., "Network Configuration Protocol 546 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 547 . 549 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 550 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 551 . 553 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 554 RFC 7224, DOI 10.17487/RFC7224, May 2014, 555 . 557 [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", 558 RFC 7277, DOI 10.17487/RFC7277, June 2014, 559 . 561 [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for 562 System Management", RFC 7317, DOI 10.17487/RFC7317, August 563 2014, . 565 Appendix A. ".sid" file example 567 The following .sid file (ietf-system@2014-08-06.sid) have been 568 generated using the following yang modules: 570 o ietf-system@2014-08-06.yang 572 o ietf-yang-types@2013-07-15.yang 574 o ietf-inet-types@2013-07-15.yang 576 o ietf-netconf-acm@2012-02-22.yang 578 o iana-crypt-hash@2014-04-04.yang 580 { 581 "assignment-ranges": [ 582 { 583 "entry-point": 1700, 584 "size": 100 585 } 586 ], 587 "module-name": "ietf-system", 588 "module-revision": "2014-08-06", 589 "items": [ 590 { 591 "type": "Module", 592 "label": "ietf-system", 593 "sid": 1700 594 }, 595 { 596 "type": "feature", 597 "label": "authentication", 598 "sid": 1701 599 }, 600 { 601 "type": "feature", 602 "label": "dns-udp-tcp-port", 603 "sid": 1702 604 }, 605 { 606 "type": "feature", 607 "label": "local-users", 608 "sid": 1703 609 }, 610 { 611 "type": "feature", 612 "label": "ntp", 613 "sid": 1704 614 }, 615 { 616 "type": "feature", 617 "label": "ntp-udp-port", 618 "sid": 1705 619 }, 620 { 621 "type": "feature", 622 "label": "radius", 623 "sid": 1706 624 }, 625 { 626 "type": "feature", 627 "label": "radius-authentication", 628 "sid": 1707 629 }, 630 { 631 "type": "feature", 632 "label": "timezone-name", 633 "sid": 1708 634 }, 635 { 636 "type": "identity", 637 "label": "/authentication-method", 638 "sid": 1709 639 }, 640 { 641 "type": "identity", 642 "label": "/authentication-method/local-users", 643 "sid": 1710 644 }, 645 { 646 "type": "identity", 647 "label": "/authentication-method/radius", 648 "sid": 1711 649 }, 650 { 651 "type": "identity", 652 "label": "/radius-authentication-type", 653 "sid": 1712 654 }, 655 { 656 "type": "identity", 657 "label": "/radius-authentication-type/radius-chap", 658 "sid": 1713 659 }, 660 { 661 "type": "identity", 662 "label": "/radius-authentication-type/radius-pap", 663 "sid": 1714 664 }, 665 { 666 "type": "node", 667 "label": "/system", 668 "sid": 1715 669 }, 670 { 671 "type": "node", 672 "label": "/system-state", 673 "sid": 1716 674 }, 675 { 676 "type": "node", 677 "label": "/system-state/clock", 678 "sid": 1717 679 }, 680 { 681 "type": "node", 682 "label": "/system-state/clock/boot-datetime", 683 "sid": 1718 684 }, 685 { 686 "type": "node", 687 "label": "/system-state/clock/current-datetime", 688 "sid": 1719 689 }, 690 { 691 "type": "node", 692 "label": "/system-state/platform", 693 "sid": 1720 694 }, 695 { 696 "type": "node", 697 "label": "/system-state/platform/machine", 698 "sid": 1721 699 }, 700 { 701 "type": "node", 702 "label": "/system-state/platform/os-name", 703 "sid": 1722 704 }, 705 { 706 "type": "node", 707 "label": "/system-state/platform/os-release", 708 "sid": 1723 710 }, 711 { 712 "type": "node", 713 "label": "/system-state/platform/os-version", 714 "sid": 1724 715 }, 716 { 717 "type": "node", 718 "label": "/system/authentication", 719 "sid": 1725 720 }, 721 { 722 "type": "node", 723 "label": "/system/authentication/user", 724 "sid": 1726 725 }, 726 { 727 "type": "node", 728 "label": "/system/authentication/user-authentication-order", 729 "sid": 1727 730 }, 731 { 732 "type": "node", 733 "label": "/system/authentication/user/authorized-key", 734 "sid": 1728 735 }, 736 { 737 "type": "node", 738 "label": "/system/authentication/user/authorized-key/algorithm", 739 "sid": 1729 740 }, 741 { 742 "type": "node", 743 "label": "/system/authentication/user/authorized-key/key-data", 744 "sid": 1730 745 }, 746 { 747 "type": "node", 748 "label": "/system/authentication/user/authorized-key/name", 749 "sid": 1731 750 }, 751 { 752 "type": "node", 753 "label": "/system/authentication/user/name", 754 "sid": 1732 755 }, 756 { 757 "type": "node", 758 "label": "/system/authentication/user/password", 759 "sid": 1733 760 }, 761 { 762 "type": "node", 763 "label": "/system/clock", 764 "sid": 1734 765 }, 766 { 767 "type": "node", 768 "label": "/system/clock/timezone/timezone-name/timezone-name", 769 "sid": 1735 770 }, 771 { 772 "type": "node", 773 "label": "/system/clock/timezone/timezone-utc-offset/timezone-utc-offset", 774 "sid": 1736 775 }, 776 { 777 "type": "node", 778 "label": "/system/contact", 779 "sid": 1737 780 }, 781 { 782 "type": "node", 783 "label": "/system/dns-resolver", 784 "sid": 1738 785 }, 786 { 787 "type": "node", 788 "label": "/system/dns-resolver/options", 789 "sid": 1739 790 }, 791 { 792 "type": "node", 793 "label": "/system/dns-resolver/options/attempts", 794 "sid": 1740 795 }, 796 { 797 "type": "node", 798 "label": "/system/dns-resolver/options/timeout", 799 "sid": 1741 800 }, 801 { 802 "type": "node", 803 "label": "/system/dns-resolver/search", 804 "sid": 1742 805 }, 806 { 807 "type": "node", 808 "label": "/system/dns-resolver/server", 809 "sid": 1743 810 }, 811 { 812 "type": "node", 813 "label": "/system/dns-resolver/server/name", 814 "sid": 1744 815 }, 816 { 817 "type": "node", 818 "label": "/system/dns-resolver/server/transport/udp-and-tcp/udp-and-tcp", 819 "sid": 1745 820 }, 821 { 822 "type": "node", 823 "label": "/system/dns-resolver/server/transport/udp-and-tcp/udp-and-tcp/address", 824 "sid": 1746 825 }, 826 { 827 "type": "node", 828 "label": "/system/dns-resolver/server/transport/udp-and-tcp/udp-and-tcp/port", 829 "sid": 1747 830 }, 831 { 832 "type": "node", 833 "label": "/system/hostname", 834 "sid": 1748 835 }, 836 { 837 "type": "node", 838 "label": "/system/location", 839 "sid": 1749 840 }, 841 { 842 "type": "node", 843 "label": "/system/ntp", 844 "sid": 1750 845 }, 846 { 847 "type": "node", 848 "label": "/system/ntp/enabled", 849 "sid": 1751 850 }, 851 { 852 "type": "node", 853 "label": "/system/ntp/server", 854 "sid": 1752 855 }, 856 { 857 "type": "node", 858 "label": "/system/ntp/server/association-type", 859 "sid": 1753 860 }, 861 { 862 "type": "node", 863 "label": "/system/ntp/server/iburst", 864 "sid": 1754 865 }, 866 { 867 "type": "node", 868 "label": "/system/ntp/server/name", 869 "sid": 1755 870 }, 871 { 872 "type": "node", 873 "label": "/system/ntp/server/prefer", 874 "sid": 1756 875 }, 876 { 877 "type": "node", 878 "label": "/system/ntp/server/transport/udp/udp", 879 "sid": 1757 880 }, 881 { 882 "type": "node", 883 "label": "/system/ntp/server/transport/udp/udp/address", 884 "sid": 1758 885 }, 886 { 887 "type": "node", 888 "label": "/system/ntp/server/transport/udp/udp/port", 889 "sid": 1759 890 }, 891 { 892 "type": "node", 893 "label": "/system/radius", 894 "sid": 1760 895 }, 896 { 897 "type": "node", 898 "label": "/system/radius/options", 899 "sid": 1761 900 }, 901 { 902 "type": "node", 903 "label": "/system/radius/options/attempts", 904 "sid": 1762 905 }, 906 { 907 "type": "node", 908 "label": "/system/radius/options/timeout", 909 "sid": 1763 910 }, 911 { 912 "type": "node", 913 "label": "/system/radius/server", 914 "sid": 1764 915 }, 916 { 917 "type": "node", 918 "label": "/system/radius/server/authentication-type", 919 "sid": 1765 920 }, 921 { 922 "type": "node", 923 "label": "/system/radius/server/name", 924 "sid": 1766 925 }, 926 { 927 "type": "node", 928 "label": "/system/radius/server/transport/udp/udp", 929 "sid": 1767 930 }, 931 { 932 "type": "node", 933 "label": "/system/radius/server/transport/udp/udp/address", 934 "sid": 1768 935 }, 936 { 937 "type": "node", 938 "label": "/system/radius/server/transport/udp/udp/authentication-port", 939 "sid": 1769 940 }, 941 { 942 "type": "node", 943 "label": "/system/radius/server/transport/udp/udp/shared-secret", 944 "sid": 1770 945 }, 946 { 947 "type": "rpc", 948 "label": "/set-current-datetime", 949 "sid": 1771 951 }, 952 { 953 "type": "rpc", 954 "label": "/set-current-datetime/input/current-datetime", 955 "sid": 1772 956 }, 957 { 958 "type": "rpc", 959 "label": "/system-restart", 960 "sid": 1773 961 }, 962 { 963 "type": "rpc", 964 "label": "/system-shutdown", 965 "sid": 1774 966 } 967 ] 968 } 970 Authors' Addresses 972 Abhinav Somaraju (editor) 973 Tridonic GmbH & Co KG 974 Farbergasse 15 975 Dornbirn, Vorarlberg 6850 976 Austria 978 Phone: +43664808926169 979 Email: abhinav.somaraju@tridonic.com 981 Michel Veillette (editor) 982 Trilliant Networks Inc. 983 610 Rue du Luxembourg 984 Granby, Quebec J2J 2V2 985 Canada 987 Phone: +14503750556 988 Email: michel.veillette@trilliantinc.com 990 Alexander Pelov 991 Acklio 992 2bis rue de la Chataigneraie 993 Cesson-Sevigne, Bretagne 35510 994 France 996 Email: a@ackl.io 997 Randy Turner 998 Landis+Gyr 999 30000 Mill Creek Ave 1000 Suite 100 1001 Alpharetta, GA 30022 1002 US 1004 Phone: ++16782581292 1005 Email: randy.turner@landisgyr.com 1006 URI: http://www.landisgyr.com/ 1008 Ana Minaburo 1009 Acklio 1010 2bis rue de la chataigneraie 1011 Cesson-Sevigne, Bretagne 35510 1012 France 1014 Email: ana@ackl.io