idnits 2.17.1 draft-jlx-tictoc-1588v2-yang-01.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 == Line 178 has weird spacing: '... +--rw ptp-d...' == Line 179 has weird spacing: '...-number uint...' == Line 462 has weird spacing: '... leaf grand...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 16, 2015) is 3114 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 (~~), 6 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 R. Cummings 6 National Instruments 7 Expires: April 2015 October 16, 2015 9 YANG Data Model for IEEE 1588v2 10 draft-jlx-tictoc-1588v2-yang-01.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 April 16, 2016. 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 hierarchy .......................... 4 64 5. IEEE 1588v2 YANG Module ................................... 7 65 6. Security Considerations .................................. 18 66 7. IANA Considerations ...................................... 19 67 8. References ............................................... 19 68 8.1. Normative References .................................. 19 69 8.2. Informative References ................................ 19 70 9. Acknowledgments .......................................... 20 72 1. Introduction 74 As a synchronization protocol, IEEE 1588v2 [IEEE1588] is widely 75 supported in the carrier networks. It can provide high precision 76 time synchronization as high as nano-seconds. The protocol depends 77 on a Precision Time Protocol (PTP) engine to automatically decide 78 its state, and a PTP transportation layer to carry the PTP timing 79 and various quality messages. The configuration parameters and 80 state data sets of IEEE 1588v2 are numerous. 82 Some work on IEEE 1588v2 MIB [PTP-MIB] is in progress in the IETF 83 TICTOC WG. But the work is only scoped with retrieval of the state 84 data of IEEE 1588v2 by Simple Network Management Protocol (SNMP) 85 and configuration is not considered, thus its use is limited. 87 Some service providers require the management of the IEEE 1588v2 88 synchronization network can be more flexible and more Internet- 89 based (typically overlaid on their transport networks). Software 90 Defined Network (SDN) is another driving factor which demands a 91 greater control over synchronization networks. 93 YANG [RFC6020] is a data modeling language used to model 94 configuration and state data manipulated by the Network 95 Configuration Protocol (NETCONF) [RFC6241]. A small set of built-in 96 data types are defined in [RFC6020], and a collection of common 97 data types are further defined in [RFC6991]. Advantages of YANG 98 include Internet based configuration capability, validation, roll- 99 back and etc., all these characteristics make it attractive to 100 become a modeling language for IEEE 1588v2. 102 This document defines a YANG [RFC6020] data model for the 103 configuration of IEEE 1588v2 devices and clocks, and also retrieval 104 of the state data of IEEE 1588v2 clocks. 106 In order to fulfill the need of a lightweight implementation, the 107 core module is designed to be generic and minimal, but be 108 extensible with capability negotiation. That is, if a node is 109 verified with a capability of more functions, then more modules can 110 be loaded on demand, otherwise, only a basic module is loaded on 111 the node. 113 This document defines PTP system information, PTP data sets and 114 running states following the structure and definitions in IEEE 115 1588v2, and compatible with [PTP-MIB]. The router specific 1588v2 116 information is out of scope of this document. 118 2. Conventions used in this document 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 122 this document are to be interpreted as described in [RFC2119]. 124 3. Terminology 126 Terminologies used in this document are extracted from [IEEE1588] 127 and [PTP-MIB]. 129 ARB Arbitrary Timescale 131 BC Boundary Clock 133 DS Data Set 135 E2E End-to-End 137 EUI Extended Unique Identifier. 139 GPS Global Positioning System 140 IANA Internet Assigned Numbers Authority 142 IP Internet Protocol 144 NIST National Institute of Standards and Technology 146 NTP Network Time Protocol 148 OC Ordinary Clock 150 P2P Peer-to-Peer 152 PTP Precision Time Protocol 154 TAI International Atomic Time 156 TC Transparent Clock 158 UDP User Datagram Protocol 160 UTC Coordinated Universal Time 162 4. IEEE 1588V2 YANG Model hierarchy 164 This section describes the hierarchy of IEEE 1588v2 YANG module. 165 Query and retrieval of device wide or port specific configuration 166 information and clock data set is described for this version. 168 Query and retrieval of clock information include: 170 - Clock data set attributes in a clock node, including: current-DS, 171 clock-parent-DS, default-DS, time-properties-DS, and 172 transparentClock-default-DS. 174 - Port specific data set attributes, including: port-DS and 175 transparentClock-port-DS. 177 module: ietf-yang-ptp-dataset 178 +--rw ptp-datasets 179 +--rw domain-number uint8 180 +--rw default-DS 181 | +--rw two-step-flag? boolean 182 | +--rw clock-identity? binary 183 | +--rw number-ports? uint16 184 | +--rw clock-quality 185 | | +--rw clock-class? uint8 186 | | +--rw clock-accuracy? uint8 187 | | +--rw offset-scaled-log-variance? uint16 188 | +--rw priority1? uint8 189 | +--rw priority2? uint8 190 | +--rw slave-only? boolean 191 +--rw current-DS 192 | +--rw steps-removed? uint16 193 | +--rw offset-from-master? binary 194 | +--rw mean-path-delay? binary 195 +--rw parent-DS 196 | +--rw parent-port-identity 197 | | +--rw clock-identity? binary 198 | | +--rw port-number? uint32 199 | +--rw parent-stats? boolean 200 | +--rw observed-parent-offset-scaled-log-variance? uint16 201 | +--rw observed-parent-clock-phase-change-rate? int32 202 | +--rw grandmaster-identity? binary 203 | +--rw grandmaster-clock-quality 204 | | +--rw grandmaster-clock-class? uint8 205 | | +--rw grandmaster-clock-accuracy? uint8 206 | | +--rw grandmaster-offset-scaled-log-variance? uint16 207 | +--rw grandmaster-priority1? uint8 208 | +--rw grandmaster-priority2? uint8 209 +--rw time-properties-DS 210 | +--rw current-UTC-offset-valid? boolean 211 | +--rw current-UTC-offset? uint16 212 | +--rw leap59? boolean 213 | +--rw leap61? boolean 214 | +--rw time-traceable? boolean 215 | +--rw frequency-traceable? boolean 216 | +--rw PTP-timescale? boolean 217 | +--rw time-source? uint8 218 +--rw port-DS 219 | +--rw port-number uint32 220 | +--rw port-identity 221 | | +--rw clock-identity? binary 222 | | +--rw port-number? uint32 223 | +--rw port-state? uint8 224 | +--rw log-min-delay-req-interval? int8 225 | +--rw peer-mean-path-delay? int64 226 | +--rw log-announce-interval? int8 227 | +--rw announce-receipt-timeout? uint8 228 | +--rw log-sync-interval? int8 229 | +--rw delay-mechanism? enumeration 230 | +--rw log-min-Pdelay-req-interval? int8 231 | +--rw version-number? uint8 232 +--rw transparent-clock-default-DS 233 | +--rw clock-identity? binary 234 | +--rw number-ports? uint16 235 | +--rw delay-mechanism? enumeration 236 | +--rw primary-domain? uint32 237 +--rw transparent-clock-port-DS 238 +--rw port-identity 239 | +--rw clock-identity? binary 240 | +--rw port-number? uint32 241 +--rw log-min-Pdelay-req-interval? int8 242 +--rw faulty-flag? boolean 243 +--rw peer-mean-path-delay? int64 245 5. IEEE 1588v2 YANG Module 247 module ietf-yang-ptp-dataset { 248 namespace "urn:ietf:params:xml:ns:yang:1588v2"; 249 prefix "ptp-dataset"; 250 organization "IETF TICTOC WG"; 251 contact "jiangyuanlong@huawei.com"; 252 description 253 "This YANG module defines a data model for the configuration 254 of IEEE 1588v2 devices and clocks, and also retrieval of the 255 state data of IEEE 1588v2 clocks."; 256 revision "2015-10-15"{ 257 description "Initial revision."; 258 reference "draft-jxl-tictoc-1588v2-yang"; 259 } 261 grouping default-DS-entry { 262 description 263 "This group bundles together all information about the 264 PTP clock Default Datasets for a single device."; 266 leaf two-step-flag { 267 description 268 "This object specifies whether the Two Step process is 269 used."; 270 type boolean; 271 } 272 leaf clock-identity { 273 description 274 "This object specifies the clockIdentity of the local 275 clock"; 276 config true; 277 type binary { 278 length "8"; 279 } 280 } 282 leaf number-ports { 283 description 284 "This object specifies the number of PTP ports on the 285 device."; 286 type uint16; 287 } 289 container clock-quality { 290 description 291 "This object specifies the default clockQuality of the 292 device, which contains clockClass, clockAccuracy and 293 offsetScaledLogVariance."; 295 leaf clock-class { 296 description 297 "This object specifies the Quality Class in the 298 defaultDS."; 299 type uint8; 300 } 301 leaf clock-accuracy { 302 description 303 "This object specifies the Quality Accuracy in the 304 defaultDS."; 305 type uint8; 306 } 307 leaf offset-scaled-log-variance { 308 description 309 "This object specifies the Quality offset in the 310 defaultDS."; 311 type uint16; 312 } 313 } 315 leaf priority1 { 316 description 317 "This object specifies the clock Priority1 in the 318 defaultDS "; 319 type uint8; 320 } 321 leaf priority2{ 322 description 323 "This object specifies the clock Priority2 in the 324 defaultDS "; 325 type uint8; 326 } 328 leaf slave-only { 329 description 330 "This object indicates whether the SlaveOnly flag is 331 set"; 332 type boolean; 333 } 334 } 336 grouping current-DS-entry { 337 description 338 "This group bundles together all information about the 339 PTP clock Current Datasets for a single device."; 341 leaf steps-removed { 342 description 343 "This object specifies the distance measured by the 344 number of Boundary clocks between the local clock and 345 the Foreign master as indicated in the stepsRemoved 346 field of Announce messages."; 347 type uint16; 348 default 0; 349 } 350 leaf offset-from-master { 351 description 352 "This object specifies the current clock dataset 353 ClockOffset value. The value of the computation of the 354 offset in time between a slave and a master clock."; 355 type binary { 356 length "1..255"; 357 } 358 } 359 leaf mean-path-delay { 360 description 361 "The mean path delay between a pair of ports as measured 362 by the delay request-response mechanism."; 363 type binary { 364 length "1..255"; 365 } 366 } 367 } 369 grouping parent-DS-entry { 370 description 371 "This group bundles together all information about the 372 PTP clock Parent Datasets for a single device."; 374 leaf parent-port-identity { 375 description 376 "This object specifies the value of portIdentity of the 377 port on the master that issues the Sync messages used in 378 synchronizing this clock."; 380 leaf clock-identity { 381 description 382 "This object identifies the clockIdentity of the 383 master clock."; 385 type binary { 386 length "8"; 387 } 388 } 390 leaf port-number { 391 description 392 "This object identifies the PortNumber for the port 393 on the specific master."; 394 type uint32{ 395 range "0..65535"; 396 } 397 } 398 } 399 leaf parent-stats { 400 description 401 "This object indicates whether the values of 402 parentDS.observedParentOffsetScaledLogVariance and 403 parentDS.observedParentClockPhaseChangeRate have been 404 measured and are valid."; 405 type boolean; 406 default false; 407 } 408 leaf observed-parent-offset-scaled-log-variance { 409 description 410 "This object specifies an estimate of the parent clock's 411 phase change rate as measured by the slave clock."; 413 type uint16; 414 default 0xFFFF; 415 } 416 leaf observed-parent-clock-phase-change-rate { 417 description 418 "This object specifies the clock's parent dataset 419 ParentClockPhaseChangeRate value. This value is an 420 estimate of the parent clock's phase change rate as 421 measured by the slave clock."; 422 type int32; 423 } 424 leaf grandmaster-identity { 425 description 426 "This object specifies the clockIdentity of the 427 Grandmaster clock."; 428 type binary{ 429 length "8"; 430 } 431 } 432 container grandmaster-clock-quality { 433 description 434 "This object specifies the clockQuality of the 435 grandmaster clock."; 437 leaf grandmaster-clock-class { 438 description 439 "This object specifies the Quality Class of 440 grandmaster clock."; 441 type uint8; 442 } 443 leaf grandmaster-clock-accuracy { 444 description 445 "This object specifies the Quality Accuracy of the 446 grandmaster clock."; 447 type uint8; 448 } 449 leaf grandmaster-offset-scaled-log-variance { 450 description 451 "This object specifies the Quality offset of the 452 grandmaster clock."; 453 type uint16; 454 } 455 } 456 leaf grandmaster-priority1 { 457 description 458 "This object specifies the priority1 attribute of the 459 grandmaster clock."; 460 type uint8; 461 } 462 leaf grandmaster-priority2 { 463 description 464 "This object specifies the priority2 attribute of the 465 grandmaster clock."; 466 type uint8; 467 } 469 } 471 grouping time-properties-DS-entry { 472 description 473 "This group bundles together all information about the 474 PTP clock time properties datasets for a single device."; 476 leaf current-UTC-offset-valid { 477 description 478 "This object indicates whether current UTC offset is 479 valid."; 480 type boolean; 481 } 482 leaf current-UTC-offset { 483 description 484 "This object specifies the offset between TAI and UTC 485 when the epoch of the PTP system is the PTP epoch, 486 otherwise the value has no meaning. The value shall be 487 in units of seconds."; 488 type uint16; 489 } 490 leaf leap59 { 491 description 492 "This object indicates whether the last minute of the 493 current UTC day contains 59 seconds."; 494 type boolean; 495 } 496 leaf leap61 { 497 description 498 "This object indicates whether the last minute of the 499 current UTC day contains 61 seconds."; 500 type boolean; 501 } 502 leaf time-traceable { 503 description 504 "This object indicates whether the timescale and the 505 currentUtcOffset are traceable to a primary reference."; 506 type boolean; 507 } 508 leaf frequency-traceable { 509 description 510 "This object indicates whether the frequency determining 511 the timescale is traceable to a primary reference."; 512 type boolean; 513 } 514 leaf PTP-timescale { 515 description 516 "This object indicates whether the clock timescale of 517 the grandmaster clock is PTP."; 518 type boolean; 519 } 520 leaf time-source { 521 description 522 "This object specifies the source of time used by the 523 grandmaster clock."; 525 type uint8; 526 } 527 } 529 grouping port-DS-entry { 530 description 531 "This group bundles together all information about the 532 clock ports dataset for a single clock port."; 534 container port-identity { 535 description 536 "This object specifies the PTP clock port Identity, 537 composed of clock-identity and portNumber."; 538 leaf clock-identity { 539 description 540 "This object identify a specific PTP node."; 541 config true; 542 type binary { 543 length "8"; 544 } 545 } 547 leaf port-number { 548 description 549 "This object specifies the PTP Portnumber for this 550 port."; 551 type uint32 { 552 range "0..65535"; 553 } 554 } 555 } 557 leaf port-state { 558 description 559 "This object specifies the current state of the protocol 560 engine associated with the port."; 561 type uint8; 562 default 1; 563 } 565 leaf log-min-delay-req-interval { 566 description 567 "This object specifies the Delay_Req message 568 transmission interval."; 569 type int8; 570 } 571 leaf peer-mean-path-delay { 572 description 573 "This object specifies an estimate of the current one- 574 way propagation delay on the link when the 575 delayMechanism is P2P, otherwise it shall be zero."; 576 type int64; 577 default 0; 578 } 580 leaf log-announce-interval { 581 description 582 "This object specifies the Announce message transmission 583 interval associated with this clock port."; 584 type int8; 585 } 587 leaf announce-receipt-timeout { 588 description 589 "This object specifies the number of announceInterval 590 that have to pass without receipt of an Announce message 591 before the occurrence of the event 592 ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES."; 593 type uint8; 594 } 596 leaf log-sync-interval { 597 description 598 "This object specifies the mean time interval between 599 successive Sync messages."; 600 type int8; 601 } 603 leaf delay-mechanism { 604 description 605 "This object specifies the delay measuring mechanism 606 used by the port. If the clock is an end-to-end clock, 607 the value is e2e, else if the clock is a peer-to-peer 608 clock, the value shall be p2p."; 609 type enumeration { 610 enum E2E { 611 value 01; 612 description 613 "The port is configured to use the delay request- 614 response mechanism."; 615 } 616 enum P2P { 617 value 02; 618 description 619 "The port is configured to use the peer delay 620 mechanism."; 621 } 622 enum DISABLED { 623 value 254; 624 description 625 "The port does not implement the delay mechanism."; 626 } 627 } 628 } 630 leaf log-min-Pdelay-req-interval { 631 description 632 "This object specifies the minimum permitted mean time 633 interval between successive Pdelay_Req messages."; 634 type int8; 635 } 637 leaf version-number { 638 description 639 "This object specifies the version of this standard 640 implemented on the port."; 641 type uint8; 642 } 643 } 645 grouping transparent-clock-default-DS-entry { 646 description 647 "This group bundles together the default data sets of a 648 transparent clock."; 649 leaf clock-identity { 650 description 651 "This object specifies the value of the clockIdentity 652 attribute of the local clock."; 653 type binary { 654 length "8"; 655 } 656 } 657 leaf number-ports { 658 description 659 "This object specifies the number of PTP ports of the 660 device."; 661 type uint16; 662 } 663 leaf delay-mechanism { 664 description 665 "This object specifies the delayMechanism of the 666 transparent clock."; 667 type enumeration { 668 enum E2E { 669 value 1; 670 description 671 "The port is configured to use the delay request- 672 response mechanism."; 673 } 674 enum P2P { 675 value 2; 676 description 677 "The port is configured to use the peer delay 678 mechanism."; 679 } 680 enum DISABLED { 681 value 254; 682 description 683 "The port does not implement the delay mechanism."; 684 } 685 } 686 } 687 leaf primary-domain { 688 description 689 "This object specifies the value of the primary 690 syntonization domain."; 691 type uint32 { 692 range "0..255"; 693 } 694 default 0; 695 } 696 } 698 grouping transparent-clock-port-DS-entry { 699 description 700 "This group bundles together the port data sets of a 701 transparent clock."; 703 container port-identity { 704 description 705 "This object specifies the portIdentity of the local 706 port."; 707 leaf clock-identity { 708 config true; 709 type binary { 710 length "8"; 712 } 713 } 715 leaf port-number { 716 type uint32 { 717 range "0..65535"; 718 } 719 } 720 } 721 leaf log-min-Pdelay-req-interval { 722 description 723 "This object specifies the minimum permitted mean time 724 interval between successive Pdelay_Req messages."; 725 type int8; 726 } 727 leaf faulty-flag { 728 description 729 "This object indicates whether the port is faulty."; 730 type boolean; 731 default false; 732 } 733 leaf peer-mean-path-delay { 734 description 735 "This object specifies an estimate of the current one- 736 way propagation delay on the link when the 737 delayMechanism is P2P, otherwise it shall be zero."; 739 type int64; 740 default 0; 741 } 742 } 744 list ptp-datasets { 746 key "domain-number"; 747 min-elements "1"; 749 description 750 "List of one or more PTP datasets in the device, one for 751 each domain-number (see IEEE 1588-2008 subclause 6.3)"; 753 leaf domain-number { 754 type uint8; 755 } 757 container default-DS { 758 uses default-DS-entry; 760 } 762 container current-DS { 763 uses current-DS-entry; 764 } 766 container parent-DS { 767 uses parent-DS-entry; 768 } 770 container time-properties-DS { 771 uses time-properties-DS-entry; 772 } 774 container port-DS { 775 uses port-DS-entry; 776 } 778 list port-DS { 779 key "port-number"; 780 min-elements "1"; 781 leaf port-number { 782 type uint32 { 783 range "0..65535"; 784 } 785 } 786 uses port-DS-entry; 787 } 789 container transparent-clock-default-DS { 790 uses transparent-clock-default-DS-entry; 791 } 793 container transparent-clock-port-DS { 794 uses transparent-clock-port-DS-entry; 795 } 796 } 797 } 798 6. Security Considerations 800 YANG modules are designed to be accessed via the NETCONF protocol 801 [RFC6241], thus security considerations in [RFC6241] apply here. 802 Security measures such as using the NETCONF over SSH [RFC6242] and 803 restricting its use with access control [RFC6536] can further 804 improve its security, avoid injection attacks and misuse of the 805 protocol. 807 Some data nodes defined in this YANG module are writable, and any 808 changes to them may adversely impact a synchronization network. 810 7. IANA Considerations 812 This document registers a URI in the IETF XML registry, and the 813 following registration is requested to be made: 815 URI: urn:ietf:params:xml:ns:yang:1588v2 817 This document registers a YANG module in the YANG Module Names: 819 name: 1588v2 namespace: urn:ietf:params:xml:ns:yang:1588v2 821 8. References 823 8.1. Normative References 825 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 826 Requirement Levels", BCP 14, RFC 2119, March 1997 828 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 829 Network Configuration Protocol (NETCONF) ", RFC 6020, 830 October 2010 832 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 833 July 2013 835 [IEEE1588] IEEE, "IEEE Standard for a Precision Clock 836 Synchronization Protocol for Networked Measurement and 837 Control Systems", IEEE Std 1588-2008, July 2008 839 8.2. Informative References 841 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 842 Bierman, "Network Configuration Protocol (NETCONF)", RFC 843 6241, June 2011 845 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 846 Shell (SSH)", RFC 6242, June 2011 848 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 849 Protocol (NETCONF) Access Control Model", RFC 6536, March 850 2012 852 [PTP-MIB] Shankarkumar, V., Montini, L., Frost, T., and Dowd, G., 853 "Precision Time Protocol Version 2 (PTPv2) Management 854 Information Base", draft-ietf-tictoc-ptp-mib-07, Work in 855 progress 857 9. Acknowledgments 859 TBD 861 Authors' Addresses 863 Yuanlong Jiang 864 Huawei Technologies Co., Ltd. 865 Bantian, Longgang district 866 Shenzhen 518129, China 867 Email: jiangyuanlong@huawei.com 869 Xian Liu 870 Huawei Technologies Co., Ltd. 871 Bantian, Longgang district 872 Shenzhen 518129, China 874 Jinchun Xu 875 Huawei Technologies Co., Ltd. 876 Bantian, Longgang district 877 Shenzhen 518129, China 879 Rodney Cummings 880 National Instruments 881 Email: Rodney.Cummings@ni.com