idnits 2.17.1 draft-ietf-core-yang-cbor-07.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC7049]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 14, 2018) is 2050 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: '-2' is mentioned on line 924, but not defined -- Looks like a reference, but probably isn't: '257' on line 924 == Missing Reference: '0-9' is mentioned on line 1190, but not defined == Missing Reference: '1-9' is mentioned on line 1181, but not defined == Missing Reference: '0-4' is mentioned on line 1190, but not defined == Missing Reference: '0-5' is mentioned on line 1190, but not defined == Missing Reference: '0-9a-fA-F' is mentioned on line 1189, but not defined -- Looks like a reference, but probably isn't: '01' on line 1190 ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) == Outdated reference: A later version (-17) exists of draft-ietf-core-comi-03 == Outdated reference: A later version (-24) exists of draft-ietf-core-sid-04 -- Obsolete informational reference (is this intentional?): RFC 7159 (Obsoleted by RFC 8259) -- 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 (~~), 9 warnings (==), 6 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: March 18, 2019 Acklio 6 A. Somaraju 7 Tridonic GmbH & Co KG 8 R. Turner 9 Landis+Gyr 10 A. Minaburo 11 Acklio 12 September 14, 2018 14 CBOR Encoding of Data Modeled with YANG 15 draft-ietf-core-yang-cbor-07 17 Abstract 19 This document defines encoding rules for serializing configuration 20 data, state data, RPC input and RPC output, Action input, Action 21 output and notifications defined within YANG modules using the 22 Concise Binary Object Representation (CBOR) [RFC7049]. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on March 18, 2019. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 60 2.1. YANG Schema Item iDentifier (SID) . . . . . . . . . . . . 5 61 2.2. CBOR diagnostic notation . . . . . . . . . . . . . . . . 5 62 3. Properties of the CBOR Encoding . . . . . . . . . . . . . . . 6 63 4. Encoding of YANG Schema Node Instances . . . . . . . . . . . 7 64 4.1. The 'leaf' . . . . . . . . . . . . . . . . . . . . . . . 7 65 4.2. The 'container' and other collections . . . . . . . . . . 8 66 4.2.1. SIDs as keys . . . . . . . . . . . . . . . . . . . . 8 67 4.2.2. Member names as keys . . . . . . . . . . . . . . . . 9 68 4.3. The 'leaf-list' . . . . . . . . . . . . . . . . . . . . . 11 69 4.4. The 'list' and 'list' instance(s) . . . . . . . . . . . . 11 70 4.4.1. SIDs as keys . . . . . . . . . . . . . . . . . . . . 12 71 4.4.2. Member names as keys . . . . . . . . . . . . . . . . 14 72 4.5. The 'anydata' . . . . . . . . . . . . . . . . . . . . . . 15 73 4.6. The 'anyxml' . . . . . . . . . . . . . . . . . . . . . . 17 74 5. Encoding of YANG data templates . . . . . . . . . . . . . . . 17 75 5.1. SIDs as keys . . . . . . . . . . . . . . . . . . . . . . 18 76 5.2. Member names as keys . . . . . . . . . . . . . . . . . . 19 77 6. Representing YANG Data Types in CBOR . . . . . . . . . . . . 20 78 6.1. The unsigned integer Types . . . . . . . . . . . . . . . 20 79 6.2. The integer Types . . . . . . . . . . . . . . . . . . . . 21 80 6.3. The 'decimal64' Type . . . . . . . . . . . . . . . . . . 21 81 6.4. The 'string' Type . . . . . . . . . . . . . . . . . . . . 22 82 6.5. The 'boolean' Type . . . . . . . . . . . . . . . . . . . 22 83 6.6. The 'enumeration' Type . . . . . . . . . . . . . . . . . 22 84 6.7. The 'bits' Type . . . . . . . . . . . . . . . . . . . . . 23 85 6.8. The 'binary' Type . . . . . . . . . . . . . . . . . . . . 24 86 6.9. The 'leafref' Type . . . . . . . . . . . . . . . . . . . 24 87 6.10. The 'identityref' Type . . . . . . . . . . . . . . . . . 25 88 6.10.1. SIDs as identityref . . . . . . . . . . . . . . . . 25 89 6.10.2. Name as identityref . . . . . . . . . . . . . . . . 26 90 6.11. The 'empty' Type . . . . . . . . . . . . . . . . . . . . 26 91 6.12. The 'union' Type . . . . . . . . . . . . . . . . . . . . 27 92 6.13. The 'instance-identifier' Type . . . . . . . . . . . . . 28 93 6.13.1. SIDs as instance-identifier . . . . . . . . . . . . 28 94 6.13.2. Names as instance-identifier . . . . . . . . . . . . 31 95 7. Security Considerations . . . . . . . . . . . . . . . . . . . 32 96 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 97 8.1. Tags Registry . . . . . . . . . . . . . . . . . . . . . . 32 98 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 99 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 100 10.1. Normative References . . . . . . . . . . . . . . . . . . 33 101 10.2. Informative References . . . . . . . . . . . . . . . . . 34 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 104 1. Introduction 106 The specification of the YANG 1.1 data modelling language [RFC7950] 107 defines an XML encoding for data instances, i.e. contents of 108 configuration datastores, state data, RPC inputs and outputs, action 109 inputs and outputs, and event notifications. 111 A new set of encoding rules has been defined to allow the use of the 112 same data models in environments based on the JavaScript Object 113 Notation (JSON) Data Interchange Format [RFC7159]. This is 114 accomplished in the JSON Encoding of Data Modeled with YANG 115 specification [RFC7951]. 117 The aim of this document is to define a set of encoding rules for the 118 Concise Binary Object Representation (CBOR) [RFC7049]. The resulting 119 encoding is more compact compared to XML and JSON and more suitable 120 for Constrained Nodes and/or Constrained Networks as defined by 121 [RFC7228]. 123 2. Terminology and Notation 125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 127 document are to be interpreted as described in [RFC2119]. 129 The following terms are defined in [RFC7950]: 131 o action 133 o anydata 135 o anyxml 137 o data node 139 o data tree 141 o datastore 143 o feature 144 o identity 146 o module 148 o notification 150 o RPC 152 o schema node 154 o schema tree 156 o submodule 158 The following terms are defined in [RFC7951]: 160 o member name 162 o name of an identity 164 o namespace-qualified 166 The following terms are defined in [RFC8040]: 168 o yang-data (YANG extension) 170 o YANG data template 172 This specification also makes use of the following terminology: 174 o child: A schema node defined within a collection such as a 175 container, a list, a case, a notification, an RPC input, an RPC 176 output, an action input, an action output. 178 o delta: Difference between the current SID and a reference SID. A 179 reference SID is defined for each context for which deltas are 180 used. 182 o item: A schema node, an identity, a module, a submodule or a 183 feature defined using the YANG modeling language. 185 o parent: The collection in which a schema node is defined. 187 o YANG Schema Item iDentifier (SID): Unsigned integer used to 188 identify different YANG items. 190 2.1. YANG Schema Item iDentifier (SID) 192 Some of the items defined in YANG [RFC7950] require the use of a 193 unique identifier. In both NETCONF [RFC6241] and RESTCONF [RFC8040], 194 these identifiers are implemented using names. To allow the 195 implementation of data models defined in YANG in constrained devices 196 and constrained networks, a more compact method to identify YANG 197 items is required. This compact identifier, called YANG Schema Item 198 iDentifier (SID), is encoded using an unsigned integer. The 199 following items are identified using SIDs: 201 o identities 203 o data nodes 205 o RPCs and associated input(s) and output(s) 207 o actions and associated input(s) and output(s) 209 o notifications and associated information 211 o YANG modules, submodules and features 213 To minimize its size, in certain positions, SIDs are represented 214 using a (signed) delta from a reference SID and the current SID. 215 Conversion from SIDs to deltas and back to SIDs are stateless 216 processes solely based on the data serialized or deserialized. 218 Mechanisms and processes used to assign SIDs to YANG items and to 219 guarantee their uniqueness is outside the scope of the present 220 specification. If SIDs are to be used, the present specification is 221 used in conjunction with a specification defining this management. 222 One example for such a specification is under development as 223 [I-D.ietf-core-sid]. 225 2.2. CBOR diagnostic notation 227 Within this document, CBOR binary contents are represented using an 228 equivalent textual form called CBOR diagnostic notation as defined in 229 [RFC7049] section 6. This notation is used strictly for 230 documentation purposes and is never used in the data serialization. 231 Table 1 below provides a summary of this notation. 233 +----------+------+--------------------------+-----------+----------+ 234 | CBOR | CBOR | Diagnostic notation | Example | CBOR | 235 | content | type | | | encoding | 236 +----------+------+--------------------------+-----------+----------+ 237 | Unsigned | 0 | Decimal digits | 123 | 18 7B | 238 | integer | | | | | 239 | Negative | 1 | Decimal digits prefixed | -123 | 38 7A | 240 | integer | | by a minus sign | | | 241 | Byte | 2 | Hexadecimal value | h'F15C' | 42 f15C | 242 | string | | enclosed between single | | | 243 | | | quotes and prefixed by | | | 244 | | | an 'h' | | | 245 | Text | 3 | String of Unicode | "txt" | 63 | 246 | string | | characters enclosed | | 747874 | 247 | | | between double quotes | | | 248 | Array | 4 | Comma-separated list of | [ 1, 2 ] | 82 01 02 | 249 | | | values within square | | | 250 | | | brackets | | | 251 | Map | 5 | Comma-separated list of | { 1: 123, | a2 | 252 | | | key : value pairs within | 2: 456 } | 01187B | 253 | | | curly braces | | 021901C8 | 254 | Boolean | 7/20 | false | false | F4 | 255 | | 7/21 | true | true | F5 | 256 | Null | 7/22 | null | null | F6 | 257 | Not | 7/23 | undefined | undefined | F7 | 258 | assigned | | | | | 259 +----------+------+--------------------------+-----------+----------+ 261 Table 1: CBOR diagnostic notation summary 263 The following extensions to the CBOR diagnostic notation are 264 supported: 266 o Any text within and including a pair of slashes is considered a 267 comment. 269 o Deltas are visualized as numbers preceded by a '+' or '-' sign. 270 The use of the '+' sign for positive deltas represents an 271 extension to the CBOR diagnostic notation as defined by [RFC7049] 272 section 6. 274 3. Properties of the CBOR Encoding 276 This document defines CBOR encoding rules for YANG schema trees and 277 their subtrees. 279 A collection such as container, list instance, notification, RPC 280 input, RPC output, action input and action output is serialized using 281 a CBOR map in which each child schema node is encoded using a key and 282 a value. This specification supports two type of CBOR keys; YANG 283 Schema Item iDentifier (SID) as defined in Section 2.1 and member 284 names as defined in [RFC7951]. Each of these key types is encoded 285 using a specific CBOR type which allows their interpretation during 286 the deserialization process. Protocols or mechanisms implementing 287 this specification can mandate the use of a specific key type. 289 In order to minimize the size of the encoded data, the proposed 290 mapping avoids any unnecessary meta-information beyond those natively 291 supported by CBOR. For instance, CBOR tags are used solely in the 292 case of anyxml schema nodes and the union datatype to distinguish 293 explicitly the use of different YANG datatypes encoded using the same 294 CBOR major type. 296 Unless specified otherwise by the protocol or mechanism implementing 297 this specification, the infinite lengths encoding as defined in 298 [RFC7049] section 2.2 SHALL be supported by CBOR decoders. 300 Data nodes implemented using a CBOR array, map, byte string, and text 301 string can be instantiated but empty. In this case, they are encoded 302 with a length of zero. 304 Application payloads carrying a value serialized using the rules 305 defined by this specification (e.g. CoAP Content-Format) SHOULD 306 include the identifier (e.g. SID, namespace-qualified member name, 307 instance-identifier) of this value. When SIDs are used as 308 identifiers, the reference SID SHALL be included in the payload to 309 allow stateless conversion of delta values to SIDs. Formats of these 310 application payloads are not defined by the current specification and 311 are not shown in the examples. 313 4. Encoding of YANG Schema Node Instances 315 Schema node instances defined using the YANG modeling language are 316 encoded using CBOR [RFC7049] based on the rules defined in this 317 section. We assume that the reader is already familiar with both 318 YANG [RFC7950] and CBOR [RFC7049]. 320 4.1. The 'leaf' 322 A 'leaf' MUST be encoded accordingly to its datatype using one of the 323 encoding rules specified in Section 6. 325 4.2. The 'container' and other collections 327 Collections such as containers, list instances, notification 328 contents, rpc inputs, rpc outputs, action inputs and action outputs 329 MUST be encoded using a CBOR map data item (major type 5). A map is 330 comprised of pairs of data items, with each data item consisting of a 331 key and a value. Each key within the CBOR map is set to a schema 332 node identifier, each value is set to the value of this schema node 333 instance according to the instance datatype. 335 This specification supports two type of CBOR keys; SID as defined in 336 Section 2.1 and member names as defined in [RFC7951]. 338 The following examples shows the encoding of a 'system-state' 339 container instance using SIDs or member names. 341 Definition example from [RFC7317]: 343 typedef date-and-time { 344 type string { 345 pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?(Z|[\+\-] 346 \d{2}:\d{2})'; 347 } 348 } 350 container system-state { 352 container clock { 353 leaf current-datetime { 354 type date-and-time; 355 } 357 leaf boot-datetime { 358 type date-and-time; 359 } 360 } 361 } 363 4.2.1. SIDs as keys 365 CBOR map keys implemented using SIDs MUST be encoded using a CBOR 366 unsigned integer (major type 0) or CBOR negative integer (major type 367 1), depending on the actual delta value. Delta values are computed 368 as follows: 370 o In the case of a 'container', deltas are equal to the SID of the 371 current schema node minus the SID of the parent 'container'. 373 o In the case of an 'rpc input' or 'rcp output', deltas are equal to 374 the SID of the current schema node minus the SID of the 'rpc'. 376 o In the case of an 'action input' or 'action output', deltas are 377 equal to the SID of the current schema node minus the SID of the 378 'action'. 380 CBOR diagnostic notation: 382 { / system-state (SID 1720) / 383 +1 : { / clock (SID 1721) / 384 +2 : "2015-10-02T14:47:24Z-05:00", / current-datetime (SID 1723)/ 385 +1 : "2015-09-15T09:12:58Z-05:00" / boot-datetime (SID 1722) / 386 } 387 } 389 CBOR encoding: 391 A1 # map(1) 392 01 # unsigned(1) 393 A2 # map(2) 394 02 # unsigned(2) 395 78 1A # text(26) 396 323031352d31302d30325431343a34373a32345a2d30353a3030 397 01 # unsigned(1) 398 78 1a # text(26) 399 323031352d30392d31355430393a31323a35385a2d30353a3030 401 4.2.2. Member names as keys 403 CBOR map keys implemented using member names MUST be encoded using a 404 CBOR text string data item (major type 3). A namespace-qualified 405 member name MUST be used each time the namespace of a schema node and 406 its parent differ. In all other cases, the simple form of the member 407 name MUST be used. Names and namespaces are defined in [RFC7951] 408 section 4. 410 The following example shows the encoding of a 'system' container 411 instance using names. 413 Definition example from [RFC7317]: 415 typedef date-and-time { 416 type string { 417 pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?(Z|[\+\-] 418 \d{2}:\d{2})'; 419 } 420 } 422 container system-state { 424 container clock { 425 leaf current-datetime { 426 type date-and-time; 427 } 429 leaf boot-datetime { 430 type date-and-time; 431 } 432 } 433 } 435 CBOR diagnostic notation: 437 { 438 "ietf-system:clock" : { 439 "current-datetime" : "2015-10-02T14:47:24Z-05:00", 440 "boot-datetime" : "2015-09-15T09:12:58Z-05:00" 441 } 442 } 444 CBOR encoding: 446 A1 # map(1) 447 71 # text(17) 448 696574662D73797374656D3A636C6F636B # "ietf-system:clock" 449 A2 # map(2) 450 70 # text(16) 451 63757272656E742D6461746574696D65 # "current-datetime" 452 78 1A # text(26) 453 323031352D31302D30325431343A34373A32345A2D30353A3030 454 6D # text(13) 455 626F6F742D6461746574696D65 # "boot-datetime" 456 78 1A # text(26) 457 323031352D30392D31355430393A31323A35385A2D30353A3030 459 4.3. The 'leaf-list' 461 A leaf-list MUST be encoded using a CBOR array data item (major type 462 4). Each entry of this array MUST be encoded accordingly to its 463 datatype using one of the encoding rules specified in Section 6. 465 The following example shows the encoding of the 'search' leaf-list 466 instance containing two entries, "ietf.org" and "ieee.org". 468 Definition example [RFC7317]: 470 typedef domain-name { 471 type string { 472 length "1..253"; 473 pattern '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9].) 474 *([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.? 475 )|\.'; 476 } 477 } 479 leaf-list search { 480 type domain-name; 481 ordered-by user; 482 } 484 CBOR diagnostic notation: [ "ietf.org", "ieee.org" ] 486 CBOR encoding: 82 68 696574662E6F7267 68 696565652E6F7267 488 4.4. The 'list' and 'list' instance(s) 490 A list or a subset of a list MUST be encoded using a CBOR array data 491 item (major type 4). Each list instance within this CBOR array is 492 encoded using a CBOR map data item (major type 5) based on the 493 encoding rules of a collection as defined in Section 4.2. 495 It is important to note that this encoding rule also apply to a 496 single 'list' instance. 498 The following examples show the encoding of a 'server' list using 499 SIDs or member names. 501 Definition example from [RFC7317]: 503 list server { 504 key name; 506 leaf name { 507 type string; 508 } 509 choice transport { 510 case udp { 511 container udp { 512 leaf address { 513 type host; 514 mandatory true; 515 } 516 leaf port { 517 type port-number; 518 } 519 } 520 } 521 } 522 leaf association-type { 523 type enumeration { 524 enum server; 525 enum peer; 526 enum pool; 527 } 528 default server; 529 } 530 leaf iburst { 531 type boolean; 532 default false; 533 } 534 leaf prefer { 535 type boolean; 536 default false; 537 } 538 } 540 4.4.1. SIDs as keys 542 The encoding rules of each 'list' instance are defined in 543 Section 4.2.1. Deltas of list members are equal to the SID of the 544 current schema node minus the SID of the 'list'. 546 CBOR diagnostic notation: 548 [ / server (SID 1756) / 549 { 550 +3 : "NRC TIC server", / name (SID 1759) / 551 +5 : { / udp (SID 1761) / 552 +1 : "tic.nrc.ca", / address (SID 1762) / 553 +2 : 123 / port (SID 1763) / 554 }, 555 +1 : 0, / association-type (SID 1757) / 556 +2 : false, / iburst (SID 1758) / 557 +4 : true / prefer (SID 1760) / 558 }, 559 { 560 +3 : "NRC TAC server", / name (SID 1759) / 561 +5 : { / udp (SID 1761) / 562 +1 : "tac.nrc.ca" / address (SID 1762) / 563 } 564 } 565 ] 567 CBOR encoding: 569 82 # array(2) 570 A5 # map(5) 571 03 # unsigned(3) 572 6E # text(14) 573 4E52432054494320736572766572 # "NRC TIC server" 574 05 # unsigned(5) 575 A2 # map(2) 576 01 # unsigned(1) 577 6A # text(10) 578 7469632E6E72632E6361 # "tic.nrc.ca" 579 02 # unsigned(2) 580 18 7B # unsigned(123) 581 01 # unsigned(1) 582 00 # unsigned(0) 583 02 # unsigned(2) 584 F4 # primitive(20) 585 04 # unsigned(4) 586 F5 # primitive(21) 587 A2 # map(2) 588 03 # unsigned(3) 589 6E # text(14) 590 4E52432054414320736572766572 # "NRC TAC server" 591 05 # unsigned(5) 592 A1 # map(1) 593 01 # unsigned(1) 594 6A # text(10) 595 7461632E6E72632E6361 # "tac.nrc.ca" 597 4.4.2. Member names as keys 599 The encoding rules of each 'list' instance are defined in 600 Section 4.2.2. 602 CBOR diagnostic notation: 604 [ 605 { 606 "ietf-system:name" : "NRC TIC server", 607 "ietf-system:udp" : { 608 "address" : "tic.nrc.ca", 609 "port" : 123 610 }, 611 "ietf-system:association-type" : 0, 612 "ietf-system:iburst" : false, 613 "ietf-system:prefer" : true 614 }, 615 { 616 "ietf-system:name" : "NRC TAC server", 617 "ietf-system:udp" : { 618 "address" : "tac.nrc.ca" 619 } 620 } 621 ] 623 CBOR encoding: 625 82 # array(2) 626 A5 # map(5) 627 70 # text(16) 628 696574662D73797374656D3A6E616D65 # "ietf-system:name" 629 6E # text(14) 630 4E52432054494320736572766572 # "NRC TIC server" 631 6F # text(15) 632 696574662D73797374656D3A756470 # "ietf-system:udp" 633 A2 # map(2) 634 67 # text(7) 635 61646472657373 # "address" 636 6A # text(10) 637 7469632E6E72632E6361 # "tic.nrc.ca" 638 64 # text(4) 639 706F7274 # "port" 640 18 7B # unsigned(123) 641 78 1C # text(28) 642 696574662D73797374656D3A6173736F63696174696F6E2D74797065 643 00 # unsigned(0) 644 72 # text(18) 645 696574662D73797374656D3A696275727374 # "ietf-system:iburst" 646 F4 # primitive(20) 647 72 # text(18) 648 696574662D73797374656D3A707265666572 # "ietf-system:prefer" 649 F5 # primitive(21) 650 A2 # map(2) 651 70 # text(16) 652 696574662D73797374656D3A6E616D65 # "ietf-system:name" 653 6E # text(14) 654 4E52432054414320736572766572 # "NRC TAC server" 655 6F # text(15) 656 696574662D73797374656D3A756470 # "ietf-system:udp" 657 A1 # map(1) 658 67 # text(7) 659 61646472657373 # "address" 660 6A # text(10) 661 7461632E6E72632E6361 # "tac.nrc.ca" 663 4.5. The 'anydata' 665 An anydata serves as a container for an arbitrary set of schema nodes 666 that otherwise appear as normal YANG-modeled data. An anydata 667 instance is encoded using the same rules as a container, i.e., CBOR 668 map. The requirement that anydata content can be modeled by YANG 669 implies the following: 671 o CBOR map keys of any inner schema nodes MUST be set to valid 672 deltas or member names. 674 o The CBOR array MUST contain either unique scalar values (as a 675 leaf-list, see Section 4.3), or maps (as a list, see Section 4.4). 677 o CBOR map values MUST follow the encoding rules of one of the 678 datatypes listed in Section 4. 680 The following example shows a possible use of an anydata. In this 681 example, an anydata is used to define a schema node containing a 682 notification event, this schema node can be part of a YANG list to 683 create an event logger. 685 Definition example: 687 module event-log { 688 ... 689 anydata event; # SID 60123 691 This example also assumes the assistance of the following 692 notification. 694 module example-port { 695 ... 697 notification example-port-fault { # SID 60200 698 leaf port-name { # SID 60201 699 type string; 700 } 701 leaf port-fault { # SID 60202 702 type string; 703 } 704 } 705 } 707 CBOR diagnostic notation: 709 { / event (SID=60123) / 710 +78 : "0/4/21", / port-name (SID=60201) / 711 +79 : "Open pin 2" / port-fault (SID=60202) / 712 } 714 CBOR encoding: 716 A2 # map(2) 717 18 4E # unsigned(78) 718 66 # text(6) 719 302F342F3231 # "0/4/21" 720 18 4F # unsigned(79) 721 6A # text(10) 722 4F70656E2070696E2032 # "Open pin 2" 724 4.6. The 'anyxml' 726 An anyxml schema node is used to serialize an arbitrary CBOR content, 727 i.e., its value can be any CBOR binary object. anyxml value MAY 728 contain CBOR data items tagged with one of the tag listed in 729 Section 8.1, these tags shall be supported. 731 The following example shows a valid CBOR encoded instance consisting 732 of a CBOR array containing the CBOR simple values 'true', 'null' and 733 'true'. 735 Definition example from [RFC7951]: 737 anyxml bar; 739 CBOR diagnostic notation: [true, null, true] 741 CBOR encoding: 83 f5 f6 f5 743 5. Encoding of YANG data templates 745 YANG data templates are data structures defined in YANG but not 746 intended to be implemented as part of a datastore. YANG data 747 templates are defined using the 'yang-data' extension as described by 748 RFC 8040. 750 YANG data templates SHOULD be encoded using the encoding rules of a 751 collection as defined in Section 4.2. 753 Just like YANG containers, YANG data templates can be encoded using 754 either SIDs or names. 756 Definition example from [I-D.ietf-core-comi]: 758 import ietf-restconf { 759 prefix rc; 760 } 762 rc:yang-data yang-errors { 763 container error { 764 leaf error-tag { 765 type identityref { 766 base error-tag; 767 } 768 } 769 leaf error-app-tag { 770 type identityref { 771 base error-app-tag; 772 } 773 } 774 leaf error-data-node { 775 type instance-identifier; 776 } 777 leaf error-message { 778 type string; 779 } 780 } 781 } 783 5.1. SIDs as keys 785 This example shows a serialization example of the yang-errors 786 template using SIDs as CBOR map key. The reference SID of a YANG 787 data template is zero, this imply that the CBOR map keys of the top 788 level members of the template are set to SIDs. 790 CBOR diagnostic notation: 792 { 793 1024 : { / error (SID 1024) / 794 +4 : 1011, / error-tag (SID 1028) / 795 / = invalid-value (SID 1011) / 796 +1 : 1018, / error-app-tag (SID 1025) / 797 / = not-in-range (SID 1018) / 798 +2 : 1740, / error-data-node (SID 1026) / 799 / = timezone-utc-offset (SID 1740) / 800 +3 : "Maximum exceeded" / error-message (SID 1027) / 801 } 802 } 804 CBOR encoding: 806 A1 # map(1) 807 19 0400 # unsigned(1024) 808 A4 # map(4) 809 04 # unsigned(4) 810 19 03F3 # unsigned(1011) 811 01 # unsigned(1) 812 19 03FA # unsigned(1018) 813 02 # unsigned(2) 814 19 06CC # unsigned(1740) 815 03 # unsigned(3) 816 70 # text(16) 817 4D6178696D756D206578636565646564 819 5.2. Member names as keys 821 This example shows a serialization example of the yang-errors 822 template using member names as CBOR map key. 824 CBOR diagnostic notation: 826 { 827 "ietf-comi:error" : { 828 "error-tag" : "invalid-value", 829 "error-app-tag" : "not-in-range", 830 "error-data-node" : "timezone-utc-offset", 831 "error-message" : "Maximum exceeded" 832 } 833 } 835 CBOR encoding: 837 A1 # map(1) 838 6F # text(15) 839 696574662D636F6D693A6572726F72 # "ietf-comi:error" 840 A4 # map(4) 841 69 # text(9) 842 6572726F722D746167 # "error-tag" 843 6D # text(13) 844 696E76616C69642D76616C7565 # "invalid-value" 845 6D # text(13) 846 6572726F722D6170702D746167 # "error-app-tag" 847 6C # text(12) 848 6E6F742D696E2D72616E6765 # "not-in-range" 849 6F # text(15) 850 6572726F722D646174612D6E6F6465 # "error-data-node" 851 73 # text(19) 852 74696D657A6F6E652D7574632D6F6666736574 # "timezone-utc-offset" 853 6D # text(13) 854 6572726F722D6D657373616765 # "error-message" 855 70 # text(16) 856 4D6178696D756D206578636565646564 858 6. Representing YANG Data Types in CBOR 860 The CBOR encoding of an instance of a leaf or leaf-list schema node 861 depends on the built-in type of that schema node. The following sub- 862 section defined the CBOR encoding of each built-in type supported by 863 YANG as listed in [RFC7950] section 4.2.4. Each subsection shows an 864 example value assigned to a schema node instance of the discussed 865 built-in type. 867 6.1. The unsigned integer Types 869 Leafs of type uint8, uint16, uint32 and uint64 MUST be encoded using 870 a CBOR unsigned integer data item (major type 0). 872 The following example shows the encoding of a 'mtu' leaf instance set 873 to 1280 bytes. 875 Definition example from [RFC7277]: 877 leaf mtu { 878 type uint16 { 879 range "68..max"; 880 } 881 } 883 CBOR diagnostic notation: 1280 884 CBOR encoding: 19 0500 886 6.2. The integer Types 888 Leafs of type int8, int16, int32 and int64 MUST be encoded using 889 either CBOR unsigned integer (major type 0) or CBOR negative integer 890 (major type 1), depending on the actual value. 892 The following example shows the encoding of a 'timezone-utc-offset' 893 leaf instance set to -300 minutes. 895 Definition example from [RFC7317]: 897 leaf timezone-utc-offset { 898 type int16 { 899 range "-1500 .. 1500"; 900 } 901 } 903 CBOR diagnostic notation: -300 905 CBOR encoding: 39 012B 907 6.3. The 'decimal64' Type 909 Leafs of type decimal64 MUST be encoded using a decimal fraction as 910 defined in [RFC7049] section 2.4.3. 912 The following example shows the encoding of a 'my-decimal' leaf 913 instance set to 2.57. 915 Definition example from [RFC7317]: 917 leaf my-decimal { 918 type decimal64 { 919 fraction-digits 2; 920 range "1 .. 3.14 | 10 | 20..max"; 921 } 922 } 924 CBOR diagnostic notation: 4([-2, 257]) 926 CBOR encoding: C4 82 21 19 0101 928 6.4. The 'string' Type 930 Leafs of type string MUST be encoded using a CBOR text string data 931 item (major type 3). 933 The following example shows the encoding of a 'name' leaf instance 934 set to "eth0". 936 Definition example from [RFC7223]: 938 leaf name { 939 type string; 940 } 942 CBOR diagnostic notation: "eth0" 944 CBOR encoding: 64 65746830 946 6.5. The 'boolean' Type 948 Leafs of type boolean MUST be encoded using a CBOR simple value 949 'true' (major type 7, additional information 21) or 'false' (major 950 type 7, additional information 20). 952 The following example shows the encoding of an 'enabled' leaf 953 instance set to 'true'. 955 Definition example from [RFC7317]: 957 leaf enabled { 958 type boolean; 959 } 961 CBOR diagnostic notation: true 963 CBOR encoding: F5 965 6.6. The 'enumeration' Type 967 Leafs of type enumeration MUST be encoded using a CBOR unsigned 968 integer (major type 0) or CBOR negative integer (major type 1), 969 depending on the actual value. Enumeration values are either 970 explicitly assigned using the YANG statement 'value' or automatically 971 assigned based on the algorithm defined in [RFC7950] section 9.6.4.2. 973 The following example shows the encoding of an 'oper-status' leaf 974 instance set to 'testing'. 976 Definition example from [RFC7317]: 978 leaf oper-status { 979 type enumeration { 980 enum up { value 1; } 981 enum down { value 2; } 982 enum testing { value 3; } 983 enum unknown { value 4; } 984 enum dormant { value 5; } 985 enum not-present { value 6; } 986 enum lower-layer-down { value 7; } 987 } 988 } 990 CBOR diagnostic notation: 3 992 CBOR encoding: 03 994 6.7. The 'bits' Type 996 Leafs of type bits MUST be encoded using a CBOR byte string data item 997 (major type 2). Bits position are either explicitly assigned using 998 the YANG statement 'position' or automatically assigned based on the 999 algorithm defined in [RFC7950] section 9.7.4.2. 1001 Bits position 0 to 7 are assigned to the first byte within the byte 1002 string, bits 8 to 15 to the second byte, and subsequent bytes are 1003 assigned similarly. Within each byte, bits are assigned from least 1004 to most significant. 1006 The following example shows the encoding of a 'mybits' leaf instance 1007 with the 'disable-nagle' and '10-Mb-only' flags set. 1009 Definition example from [RFC7950]: 1011 leaf mybits { 1012 type bits { 1013 bit disable-nagle { 1014 position 0; 1015 } 1016 bit auto-sense-speed { 1017 position 1; 1018 } 1019 bit 10-Mb-only { 1020 position 2; 1021 } 1022 } 1023 } 1024 CBOR diagnostic notation: h'05' 1026 CBOR encoding: 41 05 1028 6.8. The 'binary' Type 1030 Leafs of type binary MUST be encoded using a CBOR byte string data 1031 item (major type 2). 1033 The following example shows the encoding of an 'aes128-key' leaf 1034 instance set to 0x1f1ce6a3f42660d888d92a4d8030476e. 1036 Definition example: 1038 leaf aes128-key { 1039 type binary { 1040 length 16; 1041 } 1042 } 1044 CBOR diagnostic notation: h'1F1CE6A3F42660D888D92A4D8030476E' 1046 CBOR encoding: 50 1F1CE6A3F42660D888D92A4D8030476E 1048 6.9. The 'leafref' Type 1050 Leafs of type leafref MUST be encoded using the rules of the schema 1051 node referenced by the 'path' YANG statement. 1053 The following example shows the encoding of an 'interface-state-ref' 1054 leaf instance set to "eth1". 1056 Definition example from [RFC7223]: 1058 typedef interface-state-ref { 1059 type leafref { 1060 path "/interfaces-state/interface/name"; 1061 } 1062 } 1064 container interfaces-state { 1065 list interface { 1066 key "name"; 1067 leaf name { 1068 type string; 1069 } 1070 leaf-list higher-layer-if { 1071 type interface-state-ref; 1072 } 1073 } 1074 } 1076 CBOR diagnostic notation: "eth1" 1078 CBOR encoding: 64 65746831 1080 6.10. The 'identityref' Type 1082 This specification supports two approaches for encoding identityref, 1083 a YANG Schema Item iDentifier (SID) as defined in Section 2.1 or a 1084 name as defined in [RFC7951] section 6.8. 1086 6.10.1. SIDs as identityref 1088 When schema nodes of type identityref are implemented using SIDs, 1089 they MUST be encoded using a CBOR unsigned integer data item (major 1090 type 0). (Note that no delta mechanism is employed for SIDs as 1091 identityref.) 1093 The following example shows the encoding of a 'type' leaf instance 1094 set to the value 'iana-if-type:ethernetCsmacd' (SID 1880). 1096 Definition example from [RFC7317]: 1098 identity interface-type { 1099 } 1101 identity iana-interface-type { 1102 base interface-type; 1103 } 1105 identity ethernetCsmacd { 1106 base iana-interface-type; 1107 } 1109 leaf type { 1110 type identityref { 1111 base interface-type; 1112 } 1113 } 1115 CBOR diagnostic notation: 1880 1117 CBOR encoding: 19 0758 1119 6.10.2. Name as identityref 1121 Alternatively, an identityref MAY be encoded using a name as defined 1122 in [RFC7951] section 6.8. When names are used, identityref MUST be 1123 encoded using a CBOR text string data item (major type 3). If the 1124 identity is defined in different module than the leaf node containing 1125 the identityref value, the namespace-qualified form MUST be used. 1126 Otherwise, both the simple and namespace-qualified forms are 1127 permitted. Names and namespaces are defined in [RFC7951] section 4. 1129 The following example shows the encoding of the identity 'iana-if- 1130 type:ethernetCsmacd' using its name. This example is described in 1131 Section 6.10.1. 1133 CBOR diagnostic notation: "iana-if-type:ethernetCsmacd" 1135 CBOR encoding: 78 1b 1136 69616E612D69662D747970653A65746865726E657443736D616364 1138 6.11. The 'empty' Type 1140 Leafs of type empty MUST be encoded using the CBOR null value (major 1141 type 7, additional information 22). 1143 The following example shows the encoding of a 'is-router' leaf 1144 instance when present. 1146 Definition example from [RFC7277]: 1148 leaf is-router { 1149 type empty; 1150 } 1152 CBOR diagnostic notation: null 1154 CBOR encoding: F6 1156 6.12. The 'union' Type 1158 Leafs of type union MUST be encoded using the rules associated with 1159 one of the types listed. When used in a union, the following YANG 1160 datatypes are prefixed by CBOR tag to avoid confusion between 1161 different YANG datatypes encoded using the same CBOR major type. 1163 o bits 1165 o enumeration 1167 o identityref 1169 o instance-identifier 1171 See Section 8.1 for the assigned value of these CBOR tags. 1173 The following example shows the encoding of an 'ip-address' leaf 1174 instance when set to "2001:db8:a0b:12f0::1". 1176 Definition example from [RFC7317]: 1178 typedef ipv4-address { 1179 type string { 1180 pattern '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3} 1181 ([0-9][1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])(%[\p{N} 1182 \p{L}]+)?'; 1183 } 1184 } 1186 typedef ipv6-address { 1187 type string { 1188 pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}((([0-9a 1189 -fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|(((25[0-5]|2[0-4][0 1190 -9]|[01]?[0-9]?[0-9])\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0 1191 -9]?[0-9])))(%[\p{N}\p{L}]+)?'; 1192 pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|((([^:]+:)*[^:]+) 1193 ?::(([^:]+:)*[^:]+)?)(%.+)?'; 1194 } 1195 } 1197 typedef ip-address { 1198 type union { 1199 type ipv4-address; 1200 type ipv6-address; 1201 } 1202 } 1204 leaf address { 1205 type inet:ip-address; 1206 } 1208 CBOR diagnostic notation: "2001:db8:a0b:12f0::1" 1210 CBOR encoding: 74 323030313A6462383A6130623A313266303A3A31 1212 6.13. The 'instance-identifier' Type 1214 This specification supports two approaches for encoding an instance- 1215 identifier, one based on YANG Schema Item iDentifier (SID) as defined 1216 in Section 2.1 and one based on names as defined in [RFC7951] section 1217 6.11. 1219 6.13.1. SIDs as instance-identifier 1221 SIDs uniquely identify a schema node. In the case of a single 1222 instance schema node, i.e. a schema node defined at the root of a 1223 YANG module or submodule or schema nodes defined within a container, 1224 the SID is sufficient to identify this instance. 1226 In the case of a schema node member of a YANG list, a SID is combined 1227 with the list key(s) to identify each instance within the YANG 1228 list(s). 1230 Single instance schema nodes MUST be encoded using a CBOR unsigned 1231 integer data item (major type 0) and set to the targeted schema node 1232 SID. 1234 Schema nodes member of a YANG list MUST be encoded using a CBOR array 1235 data item (major type 4) containing the following entries: 1237 o The first entry MUST be encoded as a CBOR unsigned integer data 1238 item (major type 0) and set to the targeted schema node SID. 1240 o The following entries MUST contain the value of each key required 1241 to identify the instance of the targeted schema node. These keys 1242 MUST be ordered as defined in the 'key' YANG statement, starting 1243 from top level list, and follow by each of the subordinate 1244 list(s). 1246 Examples within this section assume the definition of a schema node 1247 of type 'instance-identifier': 1249 Definition example from [RFC7950]: 1251 container system { 1252 ... 1253 leaf reporting-entity { 1254 type instance-identifier; 1255 } 1257 leaf contact { type string; } 1259 leaf hostname { type inet:domain-name; } } ~~~~ 1261 *First example:* 1263 The following example shows the encoding of the 'reporting-entity' 1264 value referencing data node instance "/system/contact" (SID 1741). 1266 Definition example from [RFC7317]: 1268 container system { 1270 leaf contact { 1271 type string; 1272 } 1274 leaf hostname { 1275 type inet:domain-name; 1276 } 1277 } 1279 CBOR diagnostic notation: 1741 1281 CBOR encoding: 19 06CD 1283 *Second example:* 1285 The following example shows the encoding of the 'reporting-entity' 1286 value referencing list instance "/system/authentication/user/ 1287 authorized-key/key-data" (SID 1734) for user name "bob" and 1288 authorized-key "admin". 1290 Definition example from [RFC7317]: 1292 list user { 1293 key name; 1295 leaf name { 1296 type string; 1297 } 1298 leaf password { 1299 type ianach:crypt-hash; 1300 } 1302 list authorized-key { 1303 key name; 1305 leaf name { 1306 type string; 1307 } 1308 leaf algorithm { 1309 type string; 1310 } 1311 leaf key-data { 1312 type binary; 1313 } 1314 } 1315 CBOR diagnostic notation: [1734, "bob", "admin"] 1317 CBOR encoding: 1319 83 # array(3) 1320 19 06C6 # unsigned(1734) 1321 63 # text(3) 1322 626F62 # "bob" 1323 65 # text(5) 1324 61646D696E # "admin" 1326 *Third example:* 1328 The following example shows the encoding of the 'reporting-entity' 1329 value referencing the list instance "/system/authentication/user" 1330 (SID 1730) corresponding to user name "jack". 1332 CBOR diagnostic notation: [1730, "jack"] 1334 CBOR encoding: 1336 82 # array(2) 1337 19 06C2 # unsigned(1730) 1338 64 # text(4) 1339 6A61636B # "jack" 1341 6.13.2. Names as instance-identifier 1343 The use of names as instance-identifier is defined in [RFC7951] 1344 section 6.11. The resulting xpath MUST be encoded using a CBOR text 1345 string data item (major type 3). 1347 *First example:* 1349 This example is described in Section 6.13.1. 1351 CBOR diagnostic notation: "/ietf-system:system/contact" 1353 CBOR encoding: 1355 78 1c 2F696574662D73797374656D3A73797374656D2F636F6E74616374 1357 *Second example:* 1359 This example is described in Section 6.13.1. 1361 CBOR diagnostic notation: 1363 "/ietf-system:system/authentication/user[name='bob']/authorized-key 1364 [name='admin']/key-data" 1366 CBOR encoding: 1368 78 59 1369 2F696574662D73797374656D3A73797374656D2F61757468656E74696361 1370 74696F6E2F757365725B6E616D653D27626F62275D2F617574686F72697A 1371 65642D6B65790D0A5B6E616D653D2761646D696E275D2F6B65792D64617461 1373 *Third example:* 1375 This example is described in Section 6.13.1. 1377 CBOR diagnostic notation: 1379 "/ietf-system:system/authentication/user[name='bob']" 1381 CBOR encoding: 1383 78 33 1384 2F696574662D73797374656D3A73797374656D2F61757468656E74696361 1385 74696F6E2F757365725B6E616D653D27626F62275D 1387 7. Security Considerations 1389 The security considerations of [RFC7049] and [RFC7950] apply. 1391 This document defines an alternative encoding for data modeled in the 1392 YANG data modeling language. As such, this encoding does not 1393 contribute any new security issues in addition of those identified 1394 for the specific protocol or context for which it is used. 1396 To minimize security risks, software on the receiving side SHOULD 1397 reject all messages that do not comply to the rules of this document 1398 and reply with an appropriate error message to the sender. 1400 8. IANA Considerations 1402 8.1. Tags Registry 1404 This specification requires the assignment of CBOR tags for the 1405 following YANG datatypes. These tags are added to the Tags Registry 1406 as defined in section 7.2 of [RFC7049]. 1408 +-----+---------------------+---------------------------+-----------+ 1409 | Tag | Data Item | Semantics | Reference | 1410 +-----+---------------------+---------------------------+-----------+ 1411 | xx | bits | YANG bits datatype | RFC XXXX | 1412 | xx | enumeration | YANG enumeration datatype | RFC XXXX | 1413 | xx | identityref | YANG identityref datatype | RFC XXXX | 1414 | xx | instance-identifier | YANG instance-identifier | RFC XXXX | 1415 | | | datatype | | 1416 +-----+---------------------+---------------------------+-----------+ 1418 // RFC Ed.: update Tag values using allocated tags and remove this 1419 note // RFC Ed.: replace XXXX with RFC number and remove this note 1421 9. Acknowledgments 1423 This document has been largely inspired by the extensive works done 1424 by Andy Bierman and Peter van der Stok on [I-D.ietf-core-comi]. 1425 [RFC7951] has also been a critical input to this work. The authors 1426 would like to thank the authors and contributors to these two drafts. 1428 The authors would also like to acknowledge the review, feedback, and 1429 comments from Ladislav Lhotka and Juergen Schoenwaelder. 1431 10. References 1433 10.1. Normative References 1435 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1436 Requirement Levels", BCP 14, RFC 2119, 1437 DOI 10.17487/RFC2119, March 1997, 1438 . 1440 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1441 and A. Bierman, Ed., "Network Configuration Protocol 1442 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1443 . 1445 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 1446 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 1447 October 2013, . 1449 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1450 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1451 . 1453 10.2. Informative References 1455 [I-D.ietf-core-comi] 1456 Veillette, M., Stok, P., Pelov, A., and A. Bierman, "CoAP 1457 Management Interface", draft-ietf-core-comi-03 (work in 1458 progress), June 2018. 1460 [I-D.ietf-core-sid] 1461 Veillette, M. and A. Pelov, "YANG Schema Item iDentifier 1462 (SID)", draft-ietf-core-sid-04 (work in progress), June 1463 2018. 1465 [RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1466 Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March 1467 2014, . 1469 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 1470 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 1471 . 1473 [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for 1474 Constrained-Node Networks", RFC 7228, 1475 DOI 10.17487/RFC7228, May 2014, 1476 . 1478 [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", 1479 RFC 7277, DOI 10.17487/RFC7277, June 2014, 1480 . 1482 [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for 1483 System Management", RFC 7317, DOI 10.17487/RFC7317, August 1484 2014, . 1486 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 1487 RFC 7951, DOI 10.17487/RFC7951, August 2016, 1488 . 1490 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1491 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1492 . 1494 Authors' Addresses 1495 Michel Veillette (editor) 1496 Trilliant Networks Inc. 1497 610 Rue du Luxembourg 1498 Granby, Quebec J2J 2V2 1499 Canada 1501 Phone: +14503750556 1502 Email: michel.veillette@trilliantinc.com 1504 Alexander Pelov (editor) 1505 Acklio 1506 2bis rue de la Chataigneraie 1507 Cesson-Sevigne, Bretagne 35510 1508 France 1510 Email: a@ackl.io 1512 Abhinav Somaraju 1513 Tridonic GmbH & Co KG 1514 Farbergasse 15 1515 Dornbirn, Vorarlberg 6850 1516 Austria 1518 Phone: +43664808926169 1519 Email: abhinav.somaraju@tridonic.com 1521 Randy Turner 1522 Landis+Gyr 1523 30000 Mill Creek Ave 1524 Suite 100 1525 Alpharetta, GA 30022 1526 US 1528 Phone: ++16782581292 1529 Email: randy.turner@landisgyr.com 1530 URI: http://www.landisgyr.com/ 1532 Ana Minaburo 1533 Acklio 1534 2bis rue de la chataigneraie 1535 Cesson-Sevigne, Bretagne 35510 1536 France 1538 Email: ana@ackl.io