idnits 2.17.1 draft-jlx-tictoc-1588v2-yang-04.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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 14, 2016) is 2962 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE1588' == Outdated reference: A later version (-12) exists of draft-ietf-tictoc-ptp-mib-08 == Outdated reference: A later version (-18) exists of draft-ietf-netconf-restconf-09 -- Obsolete informational reference (is this intentional?): RFC 6536 (Obsoleted by RFC 8341) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Working Group Y. Jiang, Ed. 2 X. Liu 3 Internet Draft J. Xu 4 Huawei 5 Intended status: Standards Track R. Cummings, Ed. 6 National Instruments 7 Expires: September 2015 March 14, 2016 9 YANG Data Model for IEEE 1588v2 10 draft-jlx-tictoc-1588v2-yang-04.txt 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with 15 the provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other 24 documents at any time. It is inappropriate to use Internet-Drafts 25 as reference material or to cite them other than as "work in 26 progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 This Internet-Draft will expire on September 14, 2016. 36 Copyright Notice 38 Copyright (c) 2016 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with 46 respect to this document. Code Components extracted from this 47 document must include Simplified BSD License text as described in 48 Section 4.e of the Trust Legal Provisions and are provided without 49 warranty as described in the Simplified BSD License. 51 Abstract 53 This document defines a YANG data model for the configuration of 54 IEEE 1588-2008 devices and clocks, and also retrieval of the 55 configuration information, data set and running states of IEEE 56 1588-2008 clocks. 58 Table of Contents 60 1. Introduction .............................................. 2 61 2. Conventions used in this document ......................... 4 62 3. Terminology ............................................... 4 63 4. IEEE 1588-2008 YANG Model hierarchy ....................... 5 64 5. IEEE 1588-2008 YANG Module ................................ 8 65 6. Security Considerations .................................. 20 66 7. IANA Considerations ...................................... 20 67 8. References ............................................... 20 68 8.1. Normative References .................................. 20 69 8.2. Informative References ................................ 21 70 9. Acknowledgments .......................................... 21 72 1. Introduction 74 As a synchronization protocol, IEEE 1588-2008 (also known as IEEE 75 1588v2) [IEEE1588] is widely supported in the carrier networks, 76 industrial networks, automotive networks, and many other 77 applications. It can provide high precision time synchronization as 78 high as nano-seconds. The protocol depends on a Precision Time 79 Protocol (PTP) engine to automatically decide its state, and a PTP 80 transportation layer to carry the PTP timing and various quality 81 messages. The configuration parameters and state data sets of IEEE 82 1588-2008 are numerous. 84 According to the concepts described in [RFC3444], IEEE 1588-2008 85 itself provides an information model in its normative 86 specifications for the data sets (in IEEE 1588-2008 clause 8). Some 87 standardization organizations including the IETF have specified 88 data models in MIBs (Management Information Bases) for IEEE 1588- 89 2008 data sets (e.g. [PTP-MIB], [IEEE8021AS]). Since these MIBs are 90 typically focused on retrieval of state data using the Simple 91 Network Management Protocol (SNMP), configuration is not considered. 93 Some service providers and applications require that the management 94 of the IEEE 1588-2008 synchronization network be flexible and more 95 Internet-based (typically overlaid on their transport networks). 96 Software Defined Network (SDN) is another driving factor which 97 demands an improved configuration capability of synchronization 98 networks. 100 YANG [RFC6020] is a data modeling language used to model 101 configuration and state data manipulated by network management 102 protocols like the Network Configuration Protocol (NETCONF) 103 [RFC6241]. A small set of built-in data types are defined in 104 [RFC6020], and a collection of common data types are further 105 defined in [RFC6991]. Advantages of YANG include Internet based 106 configuration capability, validation, roll-back and so on. All of 107 these characteristics make it attractive to become another 108 candidate modeling language for IEEE 1588-2008. 110 This document defines a YANG [RFC6020] data model for the 111 configuration of IEEE 1588-2008 devices and clocks, and also 112 retrieval of the state data of IEEE 1588-2008 clocks. It defines 113 PTP system information, PTP data sets and running states following 114 the structure and definitions in IEEE 1588-2008, and compatible 115 with [PTP-MIB]. The router specific 1588-2008 information is out of 116 scope of this document. 118 When used in practice, network products in support of 119 synchronization typically conform to one or more IEEE 1588-2008 120 profiles. Each profile specifies how IEEE 1588-2008 is used in a 121 given industry (e.g. telecom, automotive) and application. A 122 profile can require features that are optional in IEEE 1588-2008, 123 and it can specify new features that use IEEE 1588-2008 as a 124 foundation. 126 It is expected that the IEEE 1588-2008 YANG module will be used as 127 follows: 129 o The IEEE 1588-2008 YANG module can be used as-is for products 130 that conform to one of the default profiles specified in IEEE 1588- 131 2008. 133 o When the IEEE 1588 standard is revised (e.g. the IEEE 1588 134 revision in progress scheduled to be published in 2017), it will 135 add some new optional features to its data sets. The YANG module 136 of this document can be revised and extended to add the new 137 features (e.g. of IEEE 1588-2017). The YANG "revision" can be used 138 to indicate changes to the YANG module. 140 o A profile standard based on IEEE 1588-2008 may create a 141 dedicated YANG module for its profile. The profile's YANG module 142 may use YANG "import" to import the IEEE 1588-2008 YANG module as 143 its foundation. Then the profile's YANG module can use YANG 144 "augment" to add any profile-specific enhancements. 146 o A product that conforms to a profile standard can also create 147 its own YANG module. The product's YANG module can "import" the 148 profile's module, and then use YANG "augment" to add any product- 149 specific enhancements. 151 2. Conventions used in this document 153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 155 this document are to be interpreted as described in [RFC2119]. 157 3. Terminology 159 Terminologies used in this document are extracted from [IEEE1588] 160 and [PTP-MIB]. 162 BC Boundary Clock 164 DS Data Set 166 E2E End-to-End 168 EUI Extended Unique Identifier. 170 GPS Global Positioning System 172 IANA Internet Assigned Numbers Authority 174 IP Internet Protocol 176 NIST National Institute of Standards and Technology 178 NTP Network Time Protocol 180 OC Ordinary Clock 182 P2P Peer-to-Peer 184 PTP Precision Time Protocol 186 TAI International Atomic Time 187 TC Transparent Clock 189 UTC Coordinated Universal Time 191 4. IEEE 1588-2008 YANG Model hierarchy 193 This section describes the hierarchy of IEEE 1588-2008 YANG module. 194 Query and retrieval of device wide or port specific configuration 195 information and clock data set is described for this version. 197 Query and retrieval of clock information include: 199 - Clock data set attributes in a clock node, including: current-ds, 200 parent-ds, default-ds, time-properties-ds, and transparentClock- 201 default-ds. 203 - Port specific data set attributes, including: port-ds and 204 transparentClock-port-ds. 206 A simplified graphical representation of the data model is 207 typically used by YANG modules as described in [REST-CONF]. This 208 document uses the same representation and the meaning of the 209 symbols in these diagrams is as follows: 211 o Brackets "[" and "]" enclose list keys. 213 o Abbreviations before data node names: "rw" means configuration 214 data (read-write) and "ro" state data (read-only). 216 o Symbols after data node names: "?" means an optional node, "!" 217 means a presence container, and "*" denotes a list and leaf-list. 219 o Parentheses enclose choice and case nodes, and case nodes are 220 also marked with a colon (":"). 222 o Ellipsis ("...") stands for contents of subtrees that are not 223 shown. 225 module: ietf-ptp-dataset 226 +--rw ptp-datasets* [domain-number] 227 +--rw domain-number uint8 228 +--rw default-ds 229 | +--rw two-step-flag? boolean 230 | +--rw clock-identity? binary 231 | +--rw number-ports? uint16 232 | +--rw clock-quality 233 | | +--rw clock-class? uint8 234 | | +--rw clock-accuracy? uint8 235 | | +--rw offset-scaled-log-variance? uint16 236 | +--rw priority1? uint8 237 | +--rw priority2? uint8 238 | +--rw slave-only? boolean 239 +--rw current-ds 240 | +--rw steps-removed? uint16 241 | +--rw offset-from-master? binary 242 | +--rw mean-path-delay? binary 243 +--rw parent-ds 244 | +--rw parent-port-identity 245 | | +--rw clock-identity? binary 246 | | +--rw port-number? uint16 247 | +--rw parent-stats? boolean 248 | +--rw observed-parent-offset-scaled-log-variance? uint16 249 | +--rw observed-parent-clock-phase-change-rate? int32 250 | +--rw grandmaster-identity? binary 251 | +--rw grandmaster-clock-quality 252 | | +--rw grandmaster-clock-class? uint8 253 | | +--rw grandmaster-clock-accuracy? uint8 254 | | +--rw grandmaster-offset-scaled-log-variance? uint16 255 | +--rw grandmaster-priority1? uint8 256 | +--rw grandmaster-priority2? uint8 257 +--rw time-properties-ds 258 | +--rw current-utc-offset-valid? boolean 259 | +--rw current-utc-offset? uint16 260 | +--rw leap59? boolean 261 | +--rw leap61? boolean 262 | +--rw time-traceable? boolean 263 | +--rw frequency-traceable? boolean 264 | +--rw ptp-timescale? boolean 265 | +--rw time-source? uint8 266 +--rw port-ds-list* [port-number] 267 | +--rw port-number -> ../port-identity/port-number 268 | +--rw port-identity 269 | | +--rw clock-identity? binary 270 | | +--rw port-number? uint16 271 | +--rw port-state? uint8 272 | +--rw log-min-delay-req-interval? int8 273 | +--rw peer-mean-path-delay? int64 274 | +--rw log-announce-interval? int8 275 | +--rw announce-receipt-timeout? uint8 276 | +--rw log-sync-interval? int8 277 | +--rw delay-mechanism? enumeration 278 | +--rw log-min-pdelay-req-interval? int8 279 | +--rw version-number? uint8 280 +--rw transparent-clock-default-ds 281 | +--rw clock-identity? binary 282 | +--rw number-ports? uint16 283 | +--rw delay-mechanism? enumeration 284 | +--rw primary-domain? uint8 285 +--rw transparent-clock-port-ds-list* [port-number] 286 +--rw port-number -> ../port-identity/port-number 287 +--rw port-identity 288 | +--rw clock-identity? binary 289 | +--rw port-number? uint16 290 +--rw log-min-pdelay-req-interval? int8 291 +--rw faulty-flag? boolean 292 +--rw peer-mean-path-delay? int64 294 5. IEEE 1588-2008 YANG Module 296 file "ietf-ptp-dataset@2015-11-10.yang" 298 module ietf-ptp-dataset{ 299 namespace "urn:ietf:params:xml:ns:yang:ietf-ptp-dataset"; 300 prefix "ptp-dataset"; 301 organization "IETF TICTOC WG"; 302 contact 303 "WG Web: http://tools.ietf.org/wg/tictoc/ 304 WG List: 305 WG Chair: Karen O'Donoghue 306 307 WG Chair: Yaakov Stein 308 309 Editor: Yuanlong Jiang 310 311 Editor: Rodney Cummings 312 "; 313 description 314 "This YANG module defines a data model for the configuration 315 of IEEE 1588-2008 clocks, and also retrieval of the state 316 data of IEEE 1588-2008 clocks."; 317 revision "2015-11-10" { 318 description "Latest revision."; 319 reference "draft-jxl-tictoc-1588v2-yang"; 320 } 322 grouping default-ds-entry { 323 description 324 "Collection of members of the default data set."; 326 leaf two-step-flag { 327 type boolean; 328 description 329 "The flag indicates whether the Two Step process is 330 used."; 331 } 332 leaf clock-identity { 333 type binary { 334 length "8"; 335 } 336 description 337 "The clockIdentity of the local clock"; 338 } 340 leaf number-ports { 341 type uint16; 342 description 343 "The number of PTP ports on the device."; 344 } 346 container clock-quality { 347 description 348 "The clockQuality of the local clock. It contains 349 clockClass, clockAccuracy and offsetScaledLogVariance."; 351 leaf clock-class { 352 type uint8; 353 default 248; 354 description 355 "The clockClass denotes the traceability of the time 356 or frequency distributed by the grandmaster clock."; 357 } 358 leaf clock-accuracy { 359 type uint8; 360 description 361 "The clockAccuracy indicates the expected accuracy 362 of a clock when it is the grandmaster."; 363 } 364 leaf offset-scaled-log-variance { 365 type uint16; 366 description 367 "An estimate of the variations of the local clock 368 from a linear timescale when it is not synchronized 369 to another clock using the protocol."; 370 } 371 } 373 leaf priority1 { 374 type uint8; 375 description 376 "The priority1 attribute of the local clock."; 377 } 378 leaf priority2{ 379 type uint8; 380 description 381 "The priority2 attribute of the local clock. "; 382 } 384 leaf slave-only { 385 type boolean; 386 description 387 "Indicates whether the clock is a slave-only clock."; 389 } 390 } 392 grouping current-ds-entry { 393 description 394 "Collection of members of current data set."; 396 leaf steps-removed { 397 type uint16; 398 default 0; 399 description 400 "The number of communication paths traversed 401 between the local clock and the grandmaster clock."; 403 } 404 leaf offset-from-master { 405 type binary { 406 length "1..255"; 407 } 408 description 409 "An implementation-specific representation of the 410 current value of the time difference between a master 411 and a slave clock as computed by the slave."; 412 } 413 leaf mean-path-delay { 414 type binary { 415 length "1..255"; 416 } 417 description 418 "An implementation-specific representation of the 419 current value of the mean propagation time between a 420 master and slave clock as computed by the slave."; 422 } 423 } 425 grouping parent-ds-entry { 426 description 427 "Collection of members of the parent data set."; 429 container parent-port-identity { 430 description 431 "The portIdentity of the port on the master. 432 It contains two members: clockIdentity and portNumer."; 434 leaf clock-identity { 435 type binary { 436 length "8"; 437 } 438 description 439 "The clockIdentity of the master clock."; 440 } 442 leaf port-number { 443 type uint16; 444 description 445 "The portNumber for the port on the specific 446 master."; 447 } 448 } 449 leaf parent-stats { 450 type boolean; 451 default false; 452 description 453 "Indicates whether the values of 454 observedParentOffsetScaledLogVariance and 455 observedParentClockPhaseChangeRate of parentDS 456 have been measured and are valid."; 457 } 458 leaf observed-parent-offset-scaled-log-variance { 459 type uint16; 460 default 0xFFFF; 461 description 462 "An estimate of the parent clock's PTP variance 463 as observed by the slave clock."; 464 } 465 leaf observed-parent-clock-phase-change-rate { 466 type int32; 467 description 468 "An estimate of the parent clock's phase change rate 469 as observed by the slave clock."; 470 } 471 leaf grandmaster-identity { 472 type binary{ 473 length "8"; 474 } 475 description 476 "The clockIdentity attribute of the grandmaster clock."; 478 } 479 container grandmaster-clock-quality { 480 description 481 "The clockQuality of the grandmaster clock. It contains 482 clockClass, clockAccuracy and offsetScaledLogVariance."; 484 leaf grandmaster-clock-class { 485 type uint8; 486 default 248; 487 description 488 "The clockClass attribute of the grandmaster clock."; 490 } 491 leaf grandmaster-clock-accuracy { 492 type uint8; 493 description 494 "The clockAccuracy attribute of the grandmaster 495 clock."; 496 } 497 leaf grandmaster-offset-scaled-log-variance { 498 type uint16; 499 description 500 "The offsetScaledLogVariance of the grandmaster 501 clock."; 502 } 503 } 504 leaf grandmaster-priority1 { 505 type uint8; 506 description 507 "The priority1 attribute of the grandmaster clock."; 509 } 510 leaf grandmaster-priority2 { 511 type uint8; 512 description 513 "The priority2 attribute of the grandmaster clock."; 515 } 517 } 519 grouping time-properties-ds-entry { 520 description 521 "Collection of members of the timeProperties data set."; 523 leaf current-utc-offset-valid { 524 type boolean; 525 description 526 "Indicates whether current UTC offset is valid."; 527 } 528 leaf current-utc-offset { 529 type uint16; 530 description 531 "The offset between TAI and UTC when the epoch of the 532 PTP system is the PTP epoch, otherwise the value has 533 no meaning."; 534 } 535 leaf leap59 { 536 type boolean; 537 description 538 "Indicates whether the last minute of the current UTC 539 day contains 59 seconds."; 540 } 541 leaf leap61 { 542 type boolean; 543 description 544 "Indicates whether the last minute of the current UTC 545 day contains 61 seconds."; 546 } 547 leaf time-traceable { 548 type boolean; 549 description 550 "Indicates whether the timescale and the 551 currentUtcOffset are traceable to a primary 552 reference."; 553 } 554 leaf frequency-traceable { 555 type boolean; 556 description 557 "Indicates whether the frequency determining the 558 timescale is traceable to a primary reference."; 559 } 560 leaf PTP-timescale { 561 type boolean; 562 description 563 "Indicates whether the clock timescale 564 of the grandmaster clock is PTP."; 565 } 566 leaf time-source { 567 type uint8; 568 description 569 "The source of time used by the grandmaster clock."; 571 } 572 } 574 grouping port-ds-entry { 575 description 576 "Collection of members of the port data set."; 578 container port-identity { 579 description 580 "The PortIdentity attribute of the local port. 581 It contains two members: clockIdentity and 582 portNumber."; 584 leaf clock-identity { 585 type binary { 586 length "8"; 587 } 588 description 589 "The clockIdentity of the local clock."; 590 } 592 leaf port-number { 593 type uint16; 594 description 595 "The portNumber for a port on the local clock."; 597 } 598 } 600 leaf port-state { 601 type uint8; 602 default 1; 603 description 604 "Current state associated with the port."; 605 } 607 leaf log-min-delay-req-interval { 608 type int8; 609 description 610 "The logarithm to the base 2 of the minDelayReqInterval 611 (the minimum permitted mean time interval between 612 successive Delay_Req messages)."; 613 } 615 leaf peer-mean-path-delay { 616 type int64; 617 default 0; 618 description 619 "An estimate of the current one-way propagation delay 620 on the link when the delayMechanism is P2P, otherwise 621 it is zero."; 623 } 625 leaf log-announce-interval { 626 type int8; 627 description 628 "The logarithm to the base 2 of the of the mean 629 announceInterval (mean time interval between 630 successive Announce messages)."; 631 } 633 leaf announce-receipt-timeout { 634 type uint8; 635 description 636 "The number of announceInterval that have to pass 637 without receipt of an announce message before the 638 occurrence of the event ANNOUNCE_RECEIPT_TIMEOUT_ 639 EXPIRES."; 640 } 642 leaf log-sync-interval { 643 type int8; 644 description 645 "The logarithm to the base 2 of the mean SyncInterval 646 for multicast messages. The rates for unicast 647 transmissions are negotiated separately on a per port 648 basis."; 649 } 651 leaf delay-mechanism { 652 type enumeration { 653 enum E2E { 654 value 01; 655 description 656 "The port uses the delay request-response 657 mechanism."; 658 } 659 enum P2P { 660 value 02; 661 description 662 "The port uses the peer delay mechanism."; 663 } 664 enum DISABLED { 665 value 254; 666 description 667 "The port does not implement the delay 668 mechanism."; 669 } 671 } 672 description 673 "The propagation delay measuring option used by the 674 port in computing meanPathDelay."; 675 } 677 leaf log-min-Pdelay-req-interval { 678 type int8; 679 description 680 "The logarithm to the base 2 of the 681 minPdelayReqInterval (minimum permitted mean time 682 interval between successive Pdelay_Req messages)."; 684 } 686 leaf version-number { 687 type uint8; 688 description 689 "The PTP version in use on the port."; 690 } 691 } 693 grouping transparent-clock-default-ds-entry { 694 description 695 "Collection of members of the transparentClockDefault data 696 set (default data set for a transparent clock)."; 698 leaf clock-identity { 699 type binary { 700 length "8"; 701 } 702 description 703 "The clockIdentity of the transparent clock."; 704 } 705 leaf number-ports { 706 type uint16; 707 description 708 "The number of PTP ports on the device."; 709 } 710 leaf delay-mechanism { 711 type enumeration { 712 enum E2E { 713 value 1; 714 description 715 "The port uses the delay request-response 716 mechanism."; 717 } 718 enum P2P { 719 value 2; 720 description 721 "The port uses the peer delay mechanism."; 722 } 723 enum DISABLED { 724 value 254; 725 description 726 "The port does not implement the delay 727 mechanism."; 728 } 729 } 730 description 731 "The propagation delay measuring option 732 used by the transparent clock."; 733 } 734 leaf primary-domain { 735 type uint8; 736 default 0; 737 description 738 "The domainNumber of the primary syntonization domain."; 740 } 741 } 743 grouping transparent-clock-port-ds-entry { 744 description 745 "Collection of members of the transparentClockPort data 746 set (port data set for a transparent clock)."; 748 container port-identity { 749 description 750 "This object specifies the portIdentity of the local 751 port."; 753 leaf clock-identity { 754 type binary { 755 length "8"; 756 } 757 description 758 "The clockIdentity of the transparent clock."; 759 } 761 leaf port-number { 762 type uint16; 763 description 764 "The portNumber for a port on the transparent 765 clock."; 766 } 767 } 768 leaf log-min-pdelay-req-interval { 769 type int8; 770 description 771 "The logarithm to the base 2 of the 772 minPdelayReqInterval (minimum permitted mean time 773 interval between successive Pdelay_Req messages)."; 774 } 775 leaf faulty-flag { 776 type boolean; 777 default false; 778 description 779 "Indicates whether the port is faulty."; 780 } 781 leaf peer-mean-path-delay { 782 type int64; 783 default 0; 784 description 785 "An estimate of the current one-way propagation delay 786 on the link when the delayMechanism is P2P, otherwise 787 it is zero."; 788 } 789 } 791 list ptp-datasets { 793 key "domain-number"; 794 min-elements "1"; 796 description 797 "List of one or more PTP datasets in the device, 798 one for each domain-number (see IEEE 1588-2008 subclause 799 6.3)"; 801 leaf domain-number { 802 type uint8; 803 description 804 "The domainNumber of the current syntonization domain."; 805 } 807 container default-ds { 808 description 809 "The default data set of the clock."; 810 uses default-ds-entry; 811 } 812 container current-ds { 813 description 814 "The current data set of the clock."; 815 uses current-ds-entry; 816 } 818 container parent-ds { 819 description 820 "The parent data set of the clock."; 821 uses parent-ds-entry; 822 } 824 container time-properties-ds { 825 description 826 "The timeProperties data set of the clock."; 827 uses time-properties-ds-entry; 828 } 830 list port-ds-list { 831 key "port-number"; 832 description 833 "List of port data sets of the clock."; 834 leaf port-number{ 835 type leafref{ 836 path "../port-identity/port-number"; 837 } 838 description 839 "Refers to the portNumber memer of 840 portDS.portIdentity."; 841 } 842 uses port-ds-entry; 843 } 845 container transparent-clock-default-ds { 846 description 847 "The members of the transparentClockDefault Data Set"; 848 uses transparent-clock-default-ds-entry; 849 } 851 list transparent-clock-port-ds-list { 852 key "port-number"; 853 description 854 "List of transparentClockPort data sets 855 of the transparent clock."; 856 leaf port-number{ 857 type leafref{ 858 path "../port-identity/port-number"; 859 } 860 description 861 "Refers to the portNumber memer 862 of transparentClockPortDS.portIdentity."; 863 } 864 uses transparent-clock-port-ds-entry; 865 } 866 } 867 } 868 870 6. Security Considerations 872 YANG modules are designed to be accessed via the NETCONF protocol 873 [RFC6241], thus security considerations in [RFC6241] apply here. 874 Security measures such as using the NETCONF over SSH [RFC6242] and 875 restricting its use with access control [RFC6536] can further 876 improve its security, avoid injection attacks and misuse of the 877 protocol. 879 Some data nodes defined in this YANG module are writable, and any 880 changes to them may adversely impact a synchronization network. 882 7. IANA Considerations 884 This document registers a URI in the IETF XML registry, and the 885 following registration is requested to be made: 886 URI: urn:ietf:params:xml:ns:yang:ietf-ptp-dataset 888 This document registers a YANG module in the YANG Module Names: 889 name: ietf-ptp-dataset namespace: urn:ietf:params:xml:ns:yang:ietf- 890 ptp-dataset 892 8. References 894 8.1. Normative References 896 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 897 Requirement Levels", BCP 14, RFC 2119, March 1997 899 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 900 Network Configuration Protocol (NETCONF) ", RFC 6020, 901 October 2010 903 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 904 July 2013 906 [IEEE1588] IEEE, "IEEE Standard for a Precision Clock 907 Synchronization Protocol for Networked Measurement and 908 Control Systems", IEEE Std 1588-2008, July 2008 910 8.2. Informative References 912 [IEEE8021AS] IEEE, "Timing and Synchronizations for Time-Sensitive 913 Applications in Bridged Local Area Networks", IEEE 914 802.1AS-2001, 2011 916 [PTP-MIB] Shankarkumar, V., Montini, L., Frost, T., and Dowd, G., 917 "Precision Time Protocol Version 2 (PTPv2) Management 918 Information Base", draft-ietf-tictoc-ptp-mib-08, Work in 919 progress 921 [REST-CONF] Bierman, A., Bjorklund, M., and Watsen, K., "RESTCONF 922 protocol", draft-ietf-netconf-restconf-09, Work in 923 progress 925 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 926 Information Models and Data Models", RFC 3444, January 927 2003, 929 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 930 Bierman, "Network Configuration Protocol (NETCONF)", RFC 931 6241, June 2011 933 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 934 Shell (SSH)", RFC 6242, June 2011 936 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 937 Protocol (NETCONF) Access Control Model", RFC 6536, March 938 2012 940 9. Acknowledgments 942 The authors would like to thank reviews and suggestions from Mahesh 943 Jethanandani and Tal Mizrahi. 945 Authors' Addresses 946 Yuanlong Jiang (Editor) 947 Huawei Technologies Co., Ltd. 948 Bantian, Longgang district 949 Shenzhen 518129, China 950 Email: jiangyuanlong@huawei.com 952 Xian Liu 953 Huawei Technologies Co., Ltd. 954 Bantian, Longgang district 955 Shenzhen 518129, China 956 lene.liuxian@huawei.com 958 Jinchun Xu 959 Huawei Technologies Co., Ltd. 960 Bantian, Longgang district 961 Shenzhen 518129, China 962 xujinchun@huawei.com 964 Rodney Cummings (Editor) 965 National Instruments 966 11500 N. Mopac Expwy 967 Bldg. C 968 Austin, TX 78759-3504 969 Email: Rodney.Cummings@ni.com