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