idnits 2.17.1 draft-jlx-tictoc-1588v2-yang-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 6, 2015) is 3214 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' -- Obsolete informational reference (is this intentional?): RFC 6536 (Obsoleted by RFC 8341) == Outdated reference: A later version (-12) exists of draft-ietf-tictoc-ptp-mib-07 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Working Group Y. Jiang 2 X. Liu 3 Internet Draft J. Xu 4 Huawei 5 Intended status: Standards Track 7 Expires: January 2015 July 6, 2015 9 Yang Data Model for IEEE 1588v2 10 draft-jlx-tictoc-1588v2-yang-00.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 January 6, 2013. 36 Copyright Notice 38 Copyright (c) 2015 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 1588v2 devices and clocks, and also retrieval of the 55 configuration information, data set and running states of IEEE 56 1588v2 clocks. 58 Table of Contents 60 1. Introduction .............................................. 2 61 2. Conventions used in this document ......................... 3 62 3. Terminology ............................................... 3 63 4. IEEE 1588V2 YANG Model .................................... 4 64 4.1. IEEE 1588V2 YANG model hierarchy ....................... 4 65 4.2. IEEE 1588v2 rpc definitions ............................ 7 66 5. IEEE 1588v2 YANG Module .................................. 12 67 6. Security Considerations .................................. 36 68 7. IANA Considerations ...................................... 36 69 8. References ............................................... 36 70 8.1. Normative References .................................. 36 71 8.2. Informative References ................................ 36 72 9. Acknowledgments .......................................... 37 74 1. Introduction 76 IEEE 1588v2 as a synchronization protocol is widely supported in 77 the carrier networks. It can provide high precision time 78 synchronization as high as nano-seconds. The protocol depends on a 79 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 1588v2 are numerous. 84 Some work on IEEE 1588v2 MIB [PTP-MIB] is in progress in the IETF 85 TICTOC WG. But the work is only scoped with retrieval of the state 86 data of IEEE 1588v2 by SNMP and configuration is not considered, 87 thus its use is limited. 89 Some service providers require the management of the IEEE 1588v2 90 synchronization network can be more flexible and more Internet- 91 based (typically overlaid on their transport networks). SDN is 92 another driving factor which demands a greater control over 93 synchronization networks. Advantages of YANG include Internet based 94 configuration capability, validation, roll-back and etc., all these 95 characteristics make it attractive to become a modeling language 96 for IEEE 1588v2. 98 YANG [RFC6020] is a data modeling language used to model 99 configuration and state data manipulated by the Network 100 Configuration Protocol (NETCONF) [RFC6241]. A small set of built- 101 in data types are defined in [RFC6020], and a collection of common 102 data types are further defined in [RFC6991]. 104 This document defines a YANG [RFC6020] data model for the 105 configuration of IEEE 1588v2 devices and clocks, and also retrieval 106 of the state data of IEEE 1588v2 clocks. 108 In order to fulfill the need of a lightweight implementation, the 109 core module is designed to be generic and minimal, but be 110 extensible with capability negotiation. That is, if a node is 111 verified with a capability of more functions, then more modules can 112 be loaded on demand, otherwise, only a basic module is loaded on 113 the node. 115 This document defines system information, data sets and running 116 states following the structure and definitions in IEEE 1588v2, and 117 in [PTP-MIB]. 119 2. Conventions used in this document 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 123 this document are to be interpreted as described in [RFC2119]. 125 3. Terminology 127 Terminologies used in this document are extracted from [IEEE1588] 128 and [PTP-MIB]. 130 ARB Arbitrary Timescale 132 BC Boundary Clock 134 DS Data Set 136 E2E End-to-End 138 EUI Extended Unique Identifier. 140 GPS Global Positioning System 142 IANA Internet Assigned Numbers Authority 144 IP Internet Protocol 146 NIST National Institute of Standards and Technology 148 NTP Network Time Protocol 150 OC Ordinary Clock 152 P2P Peer-to-Peer 154 PTP Precision Time Protocol 156 TAI International Atomic Time 158 TC Transparent Clock 160 UDP User Datagram Protocol 162 UTC Coordinated Universal Time 164 4. IEEE 1588V2 YANG Model 166 4.1. IEEE 1588V2 YANG model hierarchy 168 This section describes the hierarchy of IEEE 1588v2 YANG module. 169 Query and retrieval of device wide or port specific configuration 170 information and clock data set is described for this version, while 171 configuration module will be described in a next version. 173 Query and retrieval of clock information include: 175 - Device level configuration information, including: clock identity, 176 domain number, clock-running states and statistics. 178 - Clock data set attributes in a clock node, including: clock- 179 current-DS, clock-parent-DS, clock-default-DS, clock-time- 180 properties-DS, and clock-trans-default-DS and etc. 182 - Port specific data set attributes, including: clock-port-DS, 183 clock-port-running, clock-port-trans-DS and clock-port-associate 184 and etc. 186 module: ietf-yang-ptp-query 187 +--rw device-ptp-query-table 188 | +--rw ptpDevicequery* [clock-identity domain-number] 189 | +--rw clock-identity binary 190 | +--rw domain-number uint32 191 | +--rw clock-current-DS 192 | | +--rw steps-removed? uint16 193 | | +--rw offset-from-master? binary 194 | | +--rw mean-path-delay? binary 195 | +--rw clock-parent-DS 196 | | +--rw parent-port-identity? binary 197 | | +--rw parent-stats? boolean 198 | | +--rw offset-scaled-log-variance? int32 199 | | +--rw clock-phase-change-rate? int32 200 | | +--rw GM-clock-identity? binary 201 | | +--rw GM-clock-priority1? uint8 202 | | +--rw GM-clock-priority2? uint8 203 | | +--rw GM-clock-quality-class? uint32 204 | | +--rw GM-clock-quality-accuracy? uint32 205 | | +--rw GM-clock-quality-offset? uint16 206 | +--rw clock-default-DS 207 | | +--rw two-step-flag? boolean 208 | | +--rw clock-identity? binary 209 | | +--rw priority1? uint8 210 | | +--rw priority2? uint8 211 | | +--rw slave-only? boolean 212 | | +--rw quality-class? uint32 213 | | +--rw quality-accuracy? uint32 214 | | +--rw quality-offset? uint16 215 | +--rw clock-running 216 | | +--rw device-clock-type? enumeration 217 | | +--rw clock-running-state? enumeration 218 | | +--rw clock-running-packets-sent? uint64 219 | | +--rw clock-running-packets-received? uint64 220 | +--rw clock-time-properties-DS 221 | | +--rw current-UTC-offset-valid? boolean 222 | | +--rw current-UTC-offset? uint16 223 | | +--rw leap59? boolean 224 | | +--rw leap61? boolean 225 | | +--rw time-traceable? boolean 226 | | +--rw freq-traceable? boolean 227 | | +--rw PTP-timescale? boolean 228 | | +--rw source? enumeration 229 | +--rw clock-trans-default-DS 230 | +--rw clock-identity? binary 231 | +--rw num-of-ports? uint32 232 | +--rw delay? enumeration 233 | +--rw primary-domain? uint32 234 +--rw port-ptp-query-table 235 +--rw ptp-port-query* [clock-identity port-number domain- 236 number] 237 +--rw clock-identity binary 238 +--rw port-number uint32 239 +--rw domain-number uint32 240 +--rw clock-port 241 | +--rw clock-port-name? string 242 | +--rw port-twostep-flag? boolean 243 | +--rw clock-port-current-peer-address? string 244 | +--rw clock-port-num-of-associated-ports? uint32 245 +--rw clock-port-DS 246 | +--rw port-identity 247 | | +--rw clock-identity? binary 248 | | +--rw port-number? uint32 249 | +--rw log-announcement-interval? int64 250 | +--rw announce-rct-timeout? uint8 251 | +--rw log-sync-interval? int8 252 | +--rw min-delay-req-interval? uint8 253 | +--rw peer-delay-req-interval? uint32 254 | +--rw delay-mech? enumeration 255 | +--rw peer-mean-path-delay? binary 256 | +--rw grant-duration? uint32 257 | +--rw PTP-version? uint32 258 +--rw clock-port-running 259 | +--rw port-type? enumeration 260 | +--rw running-state? enumeration 261 | +--rw running-role? enumeration 262 | +--rw running-interface-index? uint32 263 | +--rw running-Tx-mode? enumeration 264 | +--rw running-Rx-mode? enumeration 265 | +--rw running-packets-received? binary 266 | +--rw running-packets-sent? uint64 267 +--rw clock-port-trans-DS 268 | +--rw log-min-pdelay-req-int? int32 269 | +--rw faulty-flag? boolean 270 | +--rw peer-mean-path-delay? binary 271 +--rw clock-port-associate 272 +--rw port-index? uint32 273 +--rw associate-address? binary 274 +--rw associate-packets-sent? binary 275 +--rw associate-packets-received? binary 276 +--rw associate-in-errors? binary 277 +--rw associate-out-errors? binary 279 4.2. IEEE 1588v2 rpc definitions 281 The rpc model facilitates issuing commands to a NETCONF server and 282 obtaining a response. Rpc model defined in this document provides 283 commands to retrieve their configuration information, data sets and 284 running states. Configuration of 1588v2 clocks and PTP ports will 285 be provided in a next version. 287 rpcs: 288 +---x read-device-ptp-query-table 289 | +---w input 290 | | +---w clock-identity? binary 291 | | +---w domain-number? uint32 292 | +--ro output 293 | +--ro clock-current-DS 294 | | +--ro steps-removed? uint16 295 | | +--ro offset-from-master? binary 296 | | +--ro mean-path-delay? binary 297 | +--ro clock-parent-DS 298 | | +--ro parent-port-identity? binary 299 | | +--ro parent-stats? boolean 300 | | +--ro offset-scaled-log-variance? int32 301 | | +--ro clock-phase-change-rate? int32 302 | | +--ro GM-clock-identity? binary 303 | | +--ro GM-clock-priority1? uint8 304 | | +--ro GM-clock-priority2? uint8 305 | | +--ro GM-clock-quality-class? uint32 306 | | +--ro GM-clock-quality-accuracy? uint32 307 | | +--ro GM-clock-quality-offset? uint16 308 | +--ro clock-default-DS 309 | | +--ro two-step-flag? boolean 310 | | +--ro clock-identity? binary 311 | | +--ro priority1? uint8 312 | | +--ro priority2? uint8 313 | | +--ro slave-only? boolean 314 | | +--ro quality-class? uint32 315 | | +--ro quality-accuracy? uint32 316 | | +--ro quality-offset? uint16 317 | +--ro clock-running 318 | | +--ro device-clock-type? enumeration 319 | | +--ro clock-running-state? enumeration 320 | | +--ro clock-running-packets-sent? uint64 321 | | +--ro clock-running-packets-received? uint64 322 | +--ro clock-time-properties-DS 323 | | +--ro current-UTC-offset-valid? boolean 324 | | +--ro current-UTC-offset? uint16 325 | | +--ro leap59? boolean 326 | | +--ro leap61? boolean 327 | | +--ro time-traceable? boolean 328 | | +--ro freq-traceable? boolean 329 | | +--ro PTP-timescale? boolean 330 | | +--ro source? enumeration 331 | +--ro clock-trans-default-DS 332 | +--ro clock-identity? binary 333 | +--ro num-of-ports? uint32 334 | +--ro delay? enumeration 335 | +--ro primary-domain? uint32 336 +---x read-clock-current-DS 337 | +---w input 338 | | +---w clock-identity? binary 339 | | +---w domain-number? uint32 340 | +--ro output 341 | +--ro steps-removed? uint16 342 | +--ro offset-from-master? binary 343 | +--ro mean-path-delay? binary 344 +---x read-clock-parent-DS 345 | +---w input 346 | | +---w clock-identity? binary 347 | | +---w domain-number? uint32 348 | +--ro output 349 | +--ro parent-port-identity? binary 350 | +--ro parent-stats? boolean 351 | +--ro offset-scaled-log-variance? int32 352 | +--ro clock-phase-change-rate? int32 353 | +--ro GM-clock-identity? binary 354 | +--ro GM-clock-priority1? uint8 355 | +--ro GM-clock-priority2? uint8 356 | +--ro GM-clock-quality-class? uint32 357 | +--ro GM-clock-quality-accuracy? uint32 358 | +--ro GM-clock-quality-offset? uint16 359 +---x read-clock-default-DS 360 | +---w input 361 | | +---w clock-identity? binary 362 | | +---w domain-number? uint32 363 | +--ro output 364 | +--ro two-step-flag? boolean 365 | +--ro clock-identity? binary 366 | +--ro priority1? uint8 367 | +--ro priority2? uint8 368 | +--ro slave-only? boolean 369 | +--ro quality-class? uint32 370 | +--ro quality-accuracy? uint32 371 | +--ro quality-offset? uint16 372 +---x read-clock-running 373 | +---w input 374 | | +---w clock-identity? binary 375 | | +---w domain-number? uint32 376 | +--ro output 377 | +--ro device-clock-type? enumeration 378 | +--ro clock-running-state? enumeration 379 | +--ro clock-running-packets-sent? uint64 380 | +--ro clock-running-packets-received? uint64 381 +---x read-clock-time-properties-DS 382 | +---w input 383 | | +---w clock-identity? binary 384 | | +---w domain-number? uint32 385 | +--ro output 386 | +--ro current-UTC-offset-valid? boolean 387 | +--ro current-UTC-offset? uint16 388 | +--ro leap59? boolean 389 | +--ro leap61? boolean 390 | +--ro time-traceable? boolean 391 | +--ro freq-traceable? boolean 392 | +--ro PTP-timescale? boolean 393 | +--ro source? enumeration 394 +---x read-clock-trans-default-DS 395 | +---w input 396 | | +---w clock-identity? binary 397 | | +---w domain-number? uint32 398 | +--ro output 399 | +--ro clock-identity? binary 400 | +--ro num-of-ports? uint32 401 | +--ro delay? enumeration 402 | +--ro primary-domain? uint32 403 +---x read-port-ptp-query-table 404 | +---w input 405 | | +---w clock-identity? binary 406 | | +---w port-number? uint32 407 | | +---w domain-number? uint32 408 | +--ro output 409 | +--ro clock-port 410 | | +--ro clock-port-name? string 411 | | +--ro port-twostep-flag? boolean 412 | | +--ro clock-port-current-peer-address? string 413 | | +--ro clock-port-num-of-associated-ports? uint32 414 | +--ro clock-port-DS 415 | | +--ro port-identity 416 | | | +--ro clock-identity? binary 417 | | | +--ro port-number? uint32 418 | | +--ro log-announcement-interval? int64 419 | | +--ro announce-rct-timeout? uint8 420 | | +--ro log-sync-interval? int8 421 | | +--ro min-delay-req-interval? uint8 422 | | +--ro peer-delay-req-interval? uint32 423 | | +--ro delay-mech? enumeration 424 | | +--ro peer-mean-path-delay? binary 425 | | +--ro grant-duration? uint32 426 | | +--ro PTP-version? uint32 427 | +--ro clock-port-running 428 | | +--ro port-type? enumeration 429 | | +--ro running-state? enumeration 430 | | +--ro running-role? enumeration 431 | | +--ro running-interface-index? uint32 432 | | +--ro running-Tx-mode? enumeration 433 | | +--ro running-Rx-mode? enumeration 434 | | +--ro running-packets-received? binary 435 | | +--ro running-packets-sent? uint64 436 | +--ro clock-port-trans-DS 437 | | +--ro log-min-pdelay-req-int? int32 438 | | +--ro faulty-flag? boolean 439 | | +--ro peer-mean-path-delay? binary 440 | +--ro clock-port-associate 441 | +--ro port-index? uint32 442 | +--ro associate-address? binary 443 | +--ro associate-packets-sent? binary 444 | +--ro associate-packets-received? binary 445 | +--ro associate-in-errors? binary 446 | +--ro associate-out-errors? binary 447 +---x read-clock-port 448 | +---w input 449 | | +---w clock-identity? binary 450 | | +---w port-number? uint32 451 | | +---w domain-number? uint32 452 | +--ro output 453 | +--ro clock-port-name? string 454 | +--ro port-twostep-flag? boolean 455 | +--ro clock-port-current-peer-address? string 456 | +--ro clock-port-num-of-associated-ports? uint32 457 +---x read-clock-port-DS 458 | +---w input 459 | | +---w clock-identity? binary 460 | | +---w port-number? uint32 461 | | +---w domain-number? uint32 462 | +--ro output 463 | +--ro port-identity 464 | | +--ro clock-identity? binary 465 | | +--ro port-number? uint32 466 | +--ro log-announcement-interval? int64 467 | +--ro announce-rct-timeout? uint8 468 | +--ro log-sync-interval? int8 469 | +--ro min-delay-req-interval? uint8 470 | +--ro peer-delay-req-interval? uint32 471 | +--ro delay-mech? enumeration 472 | +--ro peer-mean-path-delay? binary 473 | +--ro grant-duration? uint32 474 | +--ro PTP-version? uint32 475 +---x read-clock-port-running 476 | +---w input 477 | | +---w clock-identity? binary 478 | | +---w port-number? uint32 479 | | +---w domain-number? uint32 480 | +--ro output 481 | +--ro port-type? enumeration 482 | +--ro running-state? enumeration 483 | +--ro running-role? enumeration 484 | +--ro running-interface-index? uint32 485 | +--ro running-Tx-mode? enumeration 486 | +--ro running-Rx-mode? enumeration 487 | +--ro running-packets-received? binary 488 | +--ro running-packets-sent? uint64 489 +---x read-clock-port-trans-DS 490 | +---w input 491 | | +---w clock-identity? binary 492 | | +---w port-number? uint32 493 | | +---w domain-number? uint32 494 | +--ro output 495 | +--ro log-min-pdelay-req-int? int32 496 | +--ro faulty-flag? boolean 497 | +--ro peer-mean-path-delay? binary 498 +---x read-clock-port-associate 499 +---w input 500 | +---w clock-identity? binary 501 | +---w port-number? uint32 502 | +---w domain-number? uint32 503 +--ro output 504 +--ro port-index? uint32 505 +--ro associate-address? binary 506 +--ro associate-packets-sent? binary 507 +--ro associate-packets-received? binary 508 +--ro associate-in-errors? binary 509 +--ro associate-out-errors? binary 511 5. IEEE 1588v2 YANG Module 513 module ietf-yang-ptp-query{ 514 namespace "urn:ietf:params:xml:ns:yang:1588v2"; 515 prefix "ptp-query"; 516 organization "IETF TICTOC WG"; 517 contact "jiangyuanlong@huawei.com"; 518 description 519 "This YANG module defines a data model for the configuration 520 of IEEE 1588v2 devices and clocks, and also retrieval of the 521 state data of IEEE 1588v2 clocks."; 522 revision "2015-07-06"{ 523 description "Initial revision."; 524 reference "draft-jxl-tictoc-1588v2-yang"; 525 } 527 grouping device-identify-infor{ 528 description 529 "This group bundles together all information used to 530 identify a device."; 531 leaf clock-identity{ 532 description "identify a specific PTP node."; 533 config true; 534 type binary { 535 length "1..255"; 536 } 537 } 539 leaf domain-number{ 540 description 541 "This object specifies the domain number used to create 542 logical group of PTP devices."; 543 type uint32{ 544 range "0..255"; 545 } 546 } 547 } 549 grouping clock-current-DS-entry{ 550 description 551 "This group bundles together all information about the 552 PTP clock Current Datasets for a single device."; 554 leaf steps-removed{ 555 description 556 "specifies the distance measured by the number of 557 Boundary clocks between the local clock and the 558 Foreign master as indicated in the stepsRemoved 559 field of Announce messages."; 560 type uint16; 561 } 562 leaf offset-from-master{ 563 description 564 "specifies the current clock dataset ClockOffset value. 565 The value of the computation of the offset in time 566 between a slave and a master clock."; 567 type binary { 568 length "1..255"; 569 } 570 } 571 leaf mean-path-delay{ 572 description 573 "The mean path delay between a pair of ports as measure 574 by the delay request-response mechanism."; 575 type binary { 576 length "1..255"; 577 } 578 } 579 } 581 grouping clock-parent-DS-entry{ 582 description 583 "This group bundles together all information about the PTP 584 clock Parent Datasets for a single device."; 586 leaf parent-port-identity{ 587 description 588 "specifies the value of portIdentity of the port on the 589 master that issues the Sync messages used in 590 synchronizing this clock."; 591 type binary{ 592 length "1..256"; 593 } 594 } 595 leaf parent-stats{ 596 description 597 "specifies the Parent Dataset ParentStats value. This 598 value indicates whether the values of ParentDSOffset and 599 ParentDSClockPhChRate have been measured and are valid. 600 A TRUE value shall indicate valid data"; 601 type boolean; 602 } 603 leaf offset-scaled-log-variance{ 604 description 605 "specifies the Parent Dataset 606 ParentOffsetScaledLogVariance value. This value is the 607 variance of the parent clocks phase as measured by the 608 local clock."; 609 type int32{ 610 range "-128..127"; 611 } 612 } 613 leaf clock-phase-change-rate{ 614 description 615 "specifies the clock's parent dataset 616 ParentClockPhaseChangeRate value. This value is an 617 estimate of the parent clocks phase change rate as 618 measured by the slave clock."; 619 type int32; 620 } 621 leaf GM-clock-identity{ 622 description 623 "This object specifies the parent dataset Grandmaster 624 clock identity"; 625 type binary{ 626 length "1..255"; 627 } 628 } 629 leaf GM-clock-priority1{ 630 description 631 "This object specifies the parent dataset Grandmaster 632 clock priority1."; 633 type uint8; 634 } 635 leaf GM-clock-priority2{ 636 description 637 "This object specifies the parent dataset grandmaster 638 clock priority2."; 639 type uint8; 640 } 641 leaf GM-clock-quality-class{ 642 description 643 "This object specifies the parent dataset grandmaster 644 clock quality class."; 645 type uint32{ 646 range "0..255"; 647 } 648 } 649 leaf GM-clock-quality-accuracy{ 650 description 651 "This object specifies the parent dataset grandmaster 652 clock quality accuracy"; 653 type uint32; 654 } 655 leaf GM-clock-quality-offset{ 656 description 657 "This object specifies the parent dataset grandmaster 658 clock quality offset."; 659 type uint16; 660 } 661 } 663 grouping clock-default-DS-entry{ 664 description 665 "This group bundles together all information about the 666 PTP clock Default Datasets for a single device."; 668 leaf two-step-flag{ 669 description 670 "This object specifies whether the Two Step process is 671 used."; 672 type boolean; 673 } 674 leaf clock-identity{ 675 description 676 "This object specifies the default Datasets clock 677 identity"; 678 type binary{ 679 length "1..255"; 680 } 681 } 682 leaf priority1{ 683 description 684 "This object specifies the default Datasets clock 685 Priority1"; 686 type uint8; 687 } 688 leaf priority2{ 689 description 690 "This object specifies the default Datasets clock 691 Priority2"; 692 type uint8; 693 } 694 leaf slave-only{ 695 description "Whether the SlaveOnly flag is set"; 696 type boolean; 698 } 699 leaf quality-class{ 700 description 701 "This object specifies the default dataset Quality 702 Class."; 703 type uint32{ 704 range "0..255"; 705 } 706 } 707 leaf quality-accuracy{ 708 description 709 "This object specifies the default dataset Quality 710 Accuracy."; 711 type uint32; 712 } 713 leaf quality-offset{ 714 description 715 "This object specifies the default dataset Quality 716 offset."; 717 type uint16; 718 } 719 } 721 grouping clock-running-entry{ 722 description 723 "This group bundles together all information about the 724 PTP clock Running Datasets for a single device."; 726 leaf device-clock-type{ 727 description "This object specifies the clock type."; 728 type enumeration{ 729 enum oc{ 730 value 0; 731 description "ordinary clock "; 732 } 733 enum bc{ 734 value 1; 735 description "boundary clock"; 736 } 737 enum e2etc{ 738 value 2; 739 description "End-to-end transparent clock"; 740 } 741 enum p2ptc{ 742 value 3; 743 description "Peer-to-peer transparent clock "; 744 } 745 enum e2etcoc{ 746 value 4; 747 description 748 "End-to-End transparent clock ordinary clock"; 749 } 750 enum p2ptcoc{ 751 value 5; 752 description 753 "peer-to-peer transparent clock ordinary clock "; 754 } 755 enum tcandbc{ 756 value 6; 757 description "transparent clock and boundary clock"; 758 } 759 } 760 } 762 leaf clock-running-state{ 763 description 764 "specifies the Clock state returned by PTP engine which 765 was described earlier."; 766 type enumeration{ 767 enum freerun{ 768 value 1; 769 description 770 "Applies to a slave device that is not locked to a 771 master. This is the initial state a slave starts 772 out with when it 773 is not getting any PTP packets from the master or 774 because of some other input error (erroneous 775 packets, etc)."; 776 } 777 enum holdover{ 778 value 2; 779 description 780 "In this state the slave device is locked to a 781 master but communication with the master has been 782 lost or the timestamps in the ptp packets are 783 incorrect. Since the slave was locked to the 784 master, it can run in this state, with similar 785 accuracy for some time. If communication with the 786 master is not restored for an extended period 787 (dependent on the clock implementation), the 788 device should move to the FREERUN state."; 789 } 790 enum acquiring{ 791 value 3; 792 description 793 "The slave device is receiving packets from a 794 master and is trying to acquire a lock."; 795 } 796 enum frequencyLocked{ 797 value 4; 798 description 799 "Slave device is locked to the Master with respect 800 to frequency, but not phase aligned"; 801 } 802 enum phaseAligned{ 803 value 5; 804 description 805 "Locked to the master with respect to frequency 806 and phase."; 807 } 808 } 809 } 810 leaf clock-running-packets-sent{ 811 description 812 "This object specifies the total number of all packet 813 Unicast and multicast that have been sent out for this 814 clock in this domain for this type."; 815 type uint64; 816 } 817 leaf clock-running-packets-received{ 818 description 819 "This object specifies the total number of all packet 820 Unicast and multicast that have been received for this 821 clock in this domain for this type."; 822 type uint64; 823 } 824 } 826 grouping clock-time-properties-DS-entry{ 827 description 828 "This group bundles together all information about the 829 PTP clock time properties datasets for a single device."; 831 leaf current-UTC-offset-valid{ 832 description 833 "This object specifies the timeproperties dataset value 834 of whether current UTC offset is valid."; 835 type boolean; 836 } 837 leaf current-UTC-offset{ 838 description 839 "This object specifies the timeproperties dataset value 840 of current UTC offset. In PTP systems whose epoch is the 841 PTP epoch, the value of 842 timePropertiesDS.currentUtcOffset is the offset between 843 TAI and UTC; otherwise the value has no meaning. The 844 value shall be in units of seconds. The initialization 845 value shall be selected as follows: a) If the 846 timePropertiesDS.ptpTimescale is TRUE, the value is the 847 value obtained from a primary reference if the value is 848 known at the time of initialization, else, b) The value 849 shall be the current number of leap seconds (7.2.3) 850 when the node is designed."; 851 type uint16; 852 } 853 leaf leap59{ 854 description 855 "This object specifies the Leap59 value in the clock 856 Current Dataset."; 857 type boolean; 858 } 859 leaf leap61{ 860 description 861 "This object specifies the Leap61 value in the clock 862 Current Dataset."; 863 type boolean; 864 } 865 leaf time-traceable{ 866 description 867 "This object specifies the Timetraceable value in the 868 clock Current Dataset."; 869 type boolean; 870 } 871 leaf freq-traceable{ 872 description 873 "This object specifies the Frequency Traceable value in 874 the clock Current Dataset."; 875 type boolean; 876 } 877 leaf PTP-timescale{ 878 description 879 "This object specifies the PTP Timescale value in the 880 clock Current Dataset."; 881 type boolean; 882 } 883 leaf source{ 884 description 885 "This object specifies the Timesource value in the clock 886 Current Dataset."; 887 type enumeration{ 888 enum atomicClock{ 889 value 16; 890 } 891 enum gps{ 892 value 32; 893 } 894 enum terrestrialRadio{ 895 value 48; 896 } 897 enum ptp{ 898 value 64; 899 } 900 enum ntp{ 901 value 80; 902 } 903 enum handSet{ 904 value 96; 905 } 906 enum other{ 907 value 144; 908 } 909 enum internalOscillator{ 910 value 160; 911 } 912 } 913 } 914 } 916 grouping clock-trans-default-DS-entry{ 917 description 918 "This group bundles together all information about the 919 PTP Transparent clock Default Datasets for a single 920 device."; 922 leaf clock-identity{ 923 description 924 "This object specifies the value of the clockIdentity 925 attribute of the local clock."; 926 type binary{ 927 length "0..255"; 928 } 929 } 930 leaf num-of-ports{ 931 description 932 "This object specifies the number of PTP ports of the 933 device."; 934 type uint32; 935 } 936 leaf delay{ 937 description 938 "This object, if the transparent clock is an end-to-end 939 transparent clock, has the value shall be E2E; If the 940 transparent clock is a peer-to-peer transparent clock, 941 the value shall be P2P."; 942 type enumeration{ 943 enum E2E{ 944 value 1; 945 description 946 "The port is configured to use the delay request- 947 response mechanism."; 948 } 949 enum P2P{ 950 value 2; 951 description 952 "The port is configured to use the peer delay 953 mechanism."; 954 } 955 enum DISABLED{ 956 value 254; 957 description 958 "The port does not implement the delay mechanism."; 959 } 960 } 961 } 962 leaf primary-domain{ 963 description 964 "This object specifies the value of the primary 965 syntonization domain. The initialization value shall be 966 0."; 967 type uint32{ 968 range "0..255"; 969 } 970 } 971 } 973 container device-ptp-query-table{ 974 list ptpDevicequery{ 975 description ""; 977 key "clock-identity domain-number"; 978 uses device-identify-infor; 979 container clock-current-DS{ 980 uses clock-current-DS-entry; 981 } 982 container clock-parent-DS{ 983 uses clock-parent-DS-entry; 984 } 985 container clock-default-DS{ 986 uses clock-default-DS-entry; 987 } 988 container clock-running{ 989 uses clock-running-entry; 990 } 991 container clock-time-properties-DS{ 992 uses clock-time-properties-DS-entry; 993 } 994 container clock-trans-default-DS{ 995 uses clock-trans-default-DS-entry; 996 } 997 } 998 } 1000 rpc read-device-ptp-query-table{ 1001 description 1002 "Read all device-level PTP informations of a specific 1003 device."; 1004 input{ 1005 uses device-identify-infor; 1006 } 1007 output{ 1008 container clock-current-DS{ 1009 uses clock-current-DS-entry; 1010 } 1011 container clock-parent-DS{ 1012 uses clock-parent-DS-entry; 1013 } 1014 container clock-default-DS{ 1015 uses clock-default-DS-entry; 1016 } 1017 container clock-running{ 1018 uses clock-running-entry; 1019 } 1020 container clock-time-properties-DS{ 1021 uses clock-time-properties-DS-entry; 1022 } 1023 container clock-trans-default-DS{ 1024 uses clock-trans-default-DS-entry; 1025 } 1027 } 1028 } 1029 rpc read-clock-current-DS { 1030 description 1031 "Reads the information about the PTP clock Current 1032 Datasets for all domains."; 1033 input { 1034 uses device-identify-infor; 1035 } 1036 output { 1037 uses clock-current-DS-entry; 1038 } 1039 } 1041 rpc read-clock-parent-DS { 1042 description 1043 "Reads the information about the PTP clock Parent 1044 Datasets for all domains."; 1045 input { 1046 uses device-identify-infor; 1047 } 1048 output { 1049 uses clock-parent-DS-entry; 1050 } 1051 } 1053 rpc read-clock-default-DS { 1054 description 1055 "Reads the information about the PTP clock Parent 1056 Datasets for all domains."; 1057 input { 1058 uses device-identify-infor; 1059 } 1060 output { 1061 uses clock-default-DS-entry; 1062 } 1063 } 1065 rpc read-clock-running{ 1066 description 1067 "Reads the clock Running PTP information for a device."; 1068 input { 1069 uses device-identify-infor; 1070 } 1071 output { 1072 uses clock-running-entry; 1073 } 1075 } 1077 rpc read-clock-time-properties-DS{ 1078 description 1079 "Reads the information about the PTP clock 1080 TimeProperties Datasets for all domains."; 1081 input { 1082 uses device-identify-infor; 1083 } 1084 output { 1085 uses clock-time-properties-DS-entry; 1086 } 1087 } 1089 rpc read-clock-trans-default-DS { 1090 description 1091 "Reads the information about the PTP clock Parent 1092 Datasets for all domains."; 1093 input { 1094 uses device-identify-infor; 1095 } 1096 output { 1097 uses clock-trans-default-DS-entry; 1098 } 1099 } 1101 grouping port-identify-info{ 1102 description ""; 1104 leaf clock-identity { 1105 description "identify a specific PTP node."; 1106 config true; 1107 type binary { 1108 length "1..255"; 1109 } 1110 } 1112 leaf port-number{ 1113 description 1114 "This object specifies the PTP Portnumber for this 1115 port."; 1116 type uint32{ 1117 range "0..65535"; 1118 } 1119 } 1121 leaf domain-number{ 1122 description 1123 "This object specifies the domain number used to create 1124 logical group of PTP devices."; 1125 type uint32{ 1126 range "0..255"; 1127 } 1128 } 1130 } 1132 grouping clock-port-entry{ 1133 description 1134 "This group bundles together basic information about a 1135 single clock port."; 1137 leaf clock-port-name{ 1138 description 1139 "This object specifies the PTP clock port name 1140 configured on the router."; 1141 type string; 1142 } 1144 leaf port-twostep-flag{ 1145 description 1146 "This object specifies that two-step clock operation 1147 between the PTP master and slave device is enabled."; 1148 type boolean; 1149 } 1151 leaf clock-port-current-peer-address{ 1152 description 1153 "This object specifies the current peer's network 1154 address used for PTP communication."; 1155 type string; 1156 } 1157 leaf clock-port-num-of-associated-ports{ 1158 description 1159 "This object specifies - For a master port - the number 1160 of PTP slave sessions (peers) associated with this PTP 1161 port. For a slave port - the number of masters available 1162 to this slave port (might or might not be peered)."; 1163 type uint32; 1164 } 1165 } 1167 grouping clock-port-DS-entry{ 1168 description 1169 "This group bundles together all information about the 1170 clock ports dataset for a single clock port."; 1172 container port-identity{ 1173 description 1174 "This object specifies the PTP clock port Identity, 1175 composed of clock-identity and portNumber."; 1176 leaf clock-identity { 1177 description "identify a specific PTP node."; 1178 config true; 1179 type binary { 1180 length "1..255"; 1181 } 1182 } 1184 leaf port-number{ 1185 description 1186 "This object specifies the PTP Portnumber for this 1187 port."; 1188 type uint32{ 1189 range "0..65535"; 1190 } 1191 } 1192 } 1194 leaf log-announcement-interval{ 1195 description 1196 "This object specifies the Announce message transmission 1197 interval associated with this clock port."; 1198 type int64; 1199 } 1201 leaf announce-rct-timeout{ 1202 description 1203 "This object specifies the Announce receipt timeout 1204 associated with this clock port."; 1205 type uint8; 1206 } 1208 leaf log-sync-interval{ 1209 description 1210 "This object specifies the Sync message transmission 1211 interval."; 1212 type int8; 1213 } 1215 leaf min-delay-req-interval{ 1216 description 1217 "This object specifies the Delay_Req message 1218 transmission interval."; 1219 type uint8; 1220 } 1222 leaf peer-delay-req-interval{ 1223 description 1224 "This object specifies the Pdelay_Req message 1225 transmission interval."; 1226 type uint32; 1227 } 1229 leaf delay-mech{ 1230 description 1231 "specifies the delay mechanism used. If the clock is an 1232 end-to-end clock, the value of the is e2e, else if the 1233 clock is a peer to-peer clock, the value shall be p2p."; 1234 type enumeration{ 1235 enum E2E{ 1236 value 01; 1237 description 1238 "The port is configured to use the delay request- 1239 response mechanism."; 1240 } 1241 enum P2P{ 1242 value 02; 1243 description 1244 "The port is configured to use the peer delay 1245 mechanism."; 1246 } 1247 enum DISABLED{ 1248 value 254; 1249 description 1250 "The port does not implement the delay mechanism."; 1251 } 1252 } 1253 } 1255 leaf peer-mean-path-delay{ 1256 description 1257 "This object specifies the peer meanPathDelay."; 1258 type binary{ 1259 length "1..256"; 1260 } 1261 } 1262 leaf grant-duration{ 1263 description 1264 "This object specifies the grant duration allocated by 1265 the master."; 1266 type uint32; 1267 } 1269 leaf PTP-version{ 1270 description 1271 "This object specifies the PTP version being used."; 1272 type uint32; 1273 } 1274 } 1276 grouping clock-port-running-entry{ 1277 description 1278 "This group bundles together all running dataset 1279 information about a single clock port."; 1281 leaf port-type{ 1282 description 1283 "when the clock is configured in TCandBC mode, its port 1284 can be configured to TC or BC."; 1285 config true; 1286 when "device-clock-type='tcandbc' "; 1287 type enumeration{ 1288 enum boundaryClock { 1289 value 2; 1290 description "configured as BC"; 1291 } 1292 enum transparentClock { 1293 value 3; 1294 description "configured as TC"; 1295 } 1296 } 1297 } 1299 leaf running-state{ 1300 description 1301 "This object specifies the port state returned by PTP 1302 engine. "; 1303 type enumeration{ 1304 enum initializing{ 1305 value 1; 1306 description 1307 "In this state a port initializes its data sets, 1308 hardware, and communication facilities."; 1310 } 1311 enum faulty{ 1312 value 2; 1313 description "The fault state of the protocol."; 1314 } 1315 enum disabled{ 1316 value 3; 1317 description 1318 "The port shall not place any messages on its 1319 communication path."; 1320 } 1321 enum listening{ 1322 value 4; 1323 description 1324 "The port is waiting for the 1325 announceReceiptTimeout to expire or to receive an 1326 Announce message from a master."; 1327 } 1328 enum preMaster{ 1329 value 5; 1330 description 1331 "The port shall behave in all respects as though 1332 it were in the MASTER state except that it shall 1333 not place any messages on its communication path 1334 except for Pdelay_Req, Pdelay_Resp, 1335 Pdelay_Resp_Follow_Up, signaling, or management 1336 messages."; 1337 } 1338 enum master{ 1339 value 6; 1340 description "The port is behaving as a master port."; 1341 } 1342 enum passive{ 1343 value 7; 1344 description 1345 "The port shall not place any messages on its 1346 communication path except for Pdelay_Req, 1347 Pdelay_Resp, Pdelay_Resp_Follow_Up, or signaling 1348 messages, or management messages that are a 1349 required response to another management message"; 1350 } 1351 enum uncalibrated{ 1352 value 8; 1353 description 1354 "The local port is preparing to synchronize to the 1355 master port."; 1356 } 1357 enum slave{ 1358 value 9; 1359 description 1360 "The port is synchronizing to the selected master 1361 port."; 1362 } 1363 } 1364 } 1365 leaf running-role{ 1366 description "This object specifies the Clock Role."; 1367 type enumeration{ 1368 enum master{ 1369 value 1; 1370 description 1371 "A clock that is the source of time to which all 1372 other clocks on that path synchronize."; 1373 } 1374 enum slave{ 1375 value 2; 1376 description 1377 "A clock which synchronizes to another clock 1378 (master)."; 1379 } 1380 } 1381 } 1382 leaf running-interface-index{ 1383 description 1384 "This object specifies the interface on the router being 1385 used by the PTP Clock for PTP communication."; 1386 type uint32; 1387 } 1389 leaf running-Tx-mode{ 1390 description "specifies the clock transmission mode "; 1391 type enumeration{ 1392 enum unicast{ 1393 value 1; 1394 description "Using unicast communication channel."; 1395 } 1396 enum multicast{ 1397 value 2; 1398 description "Using Multicast communication channel."; 1399 } 1400 enum multicastmix{ 1401 value 3; 1402 description 1403 "Using multicast-unicast communication channel."; 1405 } 1406 } 1407 } 1409 leaf running-Rx-mode{ 1410 description "This object specifie the clock receive mode "; 1411 type enumeration{ 1412 enum unicast{ 1413 value 1; 1414 description "Using unicast communication channel."; 1415 } 1416 enum multicast{ 1417 value 2; 1418 description "Using Multicast communication channel."; 1419 } 1420 enum multicastmix{ 1421 value 3; 1422 description 1423 "Using multicast-unicast communication channel."; 1424 } 1425 } 1426 } 1427 leaf running-packets-received{ 1428 description 1429 "This object specifies the packets received on the clock 1430 port (cummulative)."; 1431 type binary{ 1432 length "1..255"; 1433 } 1434 } 1435 leaf running-packets-sent{ 1436 description 1437 "This object specifies the packets sent on the clock 1438 port (cummulative)."; 1439 type uint64; 1440 } 1441 } 1443 grouping clock-port-trans-DS-entry{ 1444 description 1445 "This group bundles together all clock port Transparent 1446 dataset information about a single clock port."; 1448 leaf log-min-pdelay-req-int{ 1449 description 1450 "This object specifies the value of the logarithm to the 1451 base 2 of the minPdelayReqInterval."; 1453 type int32{ 1454 range "-128..127"; 1455 } 1456 } 1457 leaf faulty-flag{ 1458 description 1459 "This object specifies the value TRUE if the port is 1460 faulty and FALSE if the port is operating normally."; 1461 type boolean; 1462 } 1463 leaf peer-mean-path-delay{ 1464 description 1465 "This object specifies, (if the delayMechanism used is 1466 P2P) the value is the estimate of the current one-way 1467 propagation delay, i.e., on the link 1468 attached to this port, computed using the peer delay 1469 mechanism. If the value of the delayMechanism used is 1470 E2E, then the value will be zero."; 1471 type binary{ 1472 length "1..255"; 1473 } 1474 } 1475 } 1477 grouping clock-port-associate-entry{ 1478 description 1479 "This group bundles together all information about a 1480 single associated port for the given clockport."; 1482 leaf port-index{ 1483 description 1484 "This object specifies the associated port's serial 1485 number in the current port's context."; 1486 type uint32{ 1487 range "1..65535"; 1488 } 1489 } 1491 leaf associate-address{ 1492 description 1493 "This object specifies the peer port's network address 1494 used for PTP communication."; 1495 type binary{ 1496 length "1..255"; 1497 } 1498 } 1499 leaf associate-packets-sent{ 1500 description 1501 "The number of packets sent to this peer port from the 1502 current port."; 1503 type binary{ 1504 length "1..255"; 1505 } 1506 } 1507 leaf associate-packets-received{ 1508 description 1509 "The number of packets received from this peer port by 1510 the current port."; 1511 type binary{ 1512 length "1..255"; 1513 } 1514 } 1515 leaf associate-in-errors{ 1516 description 1517 "This object specifies the input errors associated with 1518 the peer port."; 1519 type binary{ 1520 length "1..255"; 1521 } 1522 } 1523 leaf associate-out-errors{ 1524 description 1525 "This object specifies the output errors associated with 1526 the peer port."; 1527 type binary{ 1528 length "1..255"; 1529 } 1530 } 1531 } 1533 container port-ptp-query-table{ 1534 list ptp-port-query{ 1535 description ""; 1537 key "clock-identity port-number domain-number"; 1538 uses port-identify-info; 1539 container clock-port{ 1540 uses clock-port-entry; 1541 } 1542 container clock-port-DS{ 1543 uses clock-port-DS-entry; 1544 } 1545 container clock-port-running{ 1546 uses clock-port-running-entry; 1548 } 1549 container clock-port-trans-DS{ 1550 uses clock-port-trans-DS-entry; 1551 } 1552 container clock-port-associate{ 1553 uses clock-port-associate-entry; 1554 } 1555 } 1556 } 1558 rpc read-port-ptp-query-table{ 1559 description 1560 "Read all port-level ptp information of a specific port 1561 on a specific device in a specific domain."; 1562 input{ 1563 uses port-identify-info; 1564 } 1565 output{ 1566 container clock-port{ 1567 uses clock-port-entry; 1568 } 1569 container clock-port-DS{ 1570 uses clock-port-DS-entry; 1571 } 1572 container clock-port-running{ 1573 uses clock-port-running-entry; 1574 } 1575 container clock-port-trans-DS{ 1576 uses clock-port-trans-DS-entry; 1577 } 1578 container clock-port-associate{ 1579 uses clock-port-associate-entry; 1580 } 1581 } 1582 } 1584 rpc read-clock-port { 1585 description 1586 "Reads the information about the PTP clock Parent 1587 Datasets for all domains."; 1588 input { 1589 uses port-identify-info; 1590 } 1591 output { 1592 uses clock-port-entry; 1593 } 1594 } 1595 rpc read-clock-port-DS{ 1596 description 1597 "Reads the information about the PTP clock Parent 1598 Datasets for all domains."; 1599 input { 1600 uses port-identify-info; 1601 } 1602 output { 1603 uses clock-port-DS-entry; 1604 } 1605 } 1607 rpc read-clock-port-running{ 1608 description 1609 "Reads the information about the PTP clock Parent 1610 Datasets for all domains."; 1611 input { 1612 uses port-identify-info; 1613 } 1614 output { 1615 uses clock-port-running-entry; 1616 } 1617 } 1618 rpc read-clock-port-trans-DS{ 1619 description 1620 "Reads the information about the PTP clock Parent 1621 Datasets for all domains."; 1622 input { 1623 uses port-identify-info; 1624 } 1625 output { 1626 uses clock-port-trans-DS-entry; 1627 } 1628 } 1629 rpc read-clock-port-associate{ 1630 description 1631 "Reads the information about the PTP clock Parent 1632 Datasets for all domains."; 1633 input { 1634 uses port-identify-info; 1635 } 1636 output { 1637 uses clock-port-associate-entry; 1638 } 1639 } 1640 } 1642 6. Security Considerations 1644 YANG modules are designed to be accessed via the NETCONF protocol 1645 [RFC6241], thus security considerations in [RFC6241] apply here. 1646 Security measures such as using the NETCONF over SSH [RFC6242] and 1647 restricting its use with access control [RFC6536] can further 1648 improve its security, avoid injection attacks and misuse of the 1649 protocol. 1651 Some data nodes defined in this YANG module are writable, and any 1652 changes to them may adversely impact a synchronization network. 1654 7. IANA Considerations 1656 This document registers a URI in the IETF XML registry, and the 1657 following registration is requested to be made: 1659 URI: urn:ietf:params:xml:ns:yang:1588v2 1661 This document registers a YANG module in the YANG Module Names: 1663 name: 1588v2 namespace: urn:ietf:params:xml:ns:yang:1588v2 1665 8. References 1667 8.1. Normative References 1669 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1670 Requirement Levels", BCP 14, RFC 2119, March 1997 1672 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 1673 Network Configuration Protocol (NETCONF) ", RFC 6020, 1674 October 2010 1676 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 1677 July 2013 1679 [IEEE1588] IEEE, "IEEE Standard for a Precision Clock 1680 Synchronization Protocol for Networked Measurement and 1681 Control Systems", IEEE Std 1588-2008, July 2008 1683 8.2. Informative References 1685 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 1686 Bierman, "Network Configuration Protocol (NETCONF)", RFC 1687 6241, June 2011 1689 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1690 Shell (SSH)", RFC 6242, June 2011 1692 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1693 Protocol (NETCONF) Access Control Model", RFC 6536, March 1694 2012 1696 [PTP-MIB] Shankarkumar, V., Montini, L., Frost, T., and Dowd, G., 1697 "Precision Time Protocol Version 2 (PTPv2) Management 1698 Information Base", draft-ietf-tictoc-ptp-mib-07, Work in 1699 progress 1701 9. Acknowledgments 1703 TBD 1705 Authors' Addresses 1707 Yuanlong Jiang 1708 Huawei Technologies Co., Ltd. 1709 Bantian, Longgang district 1710 Shenzhen 518129, China 1711 Email: jiangyuanlong@huawei.com 1713 Xian Liu 1714 Huawei Technologies Co., Ltd. 1715 Bantian, Longgang district 1716 Shenzhen 518129, China 1718 Jinchun Xu 1719 Huawei Technologies Co., Ltd. 1720 Bantian, Longgang district 1721 Shenzhen 518129, China