draft-ietf-tictoc-1588v2-yang-02.txt   draft-ietf-tictoc-1588v2-yang-03.txt 
Internet Working Group Y. Jiang, Ed. Internet Working Group Y. Jiang, Ed.
X. Liu X. Liu
Internet-Draft J. Xu Internet-Draft J. Xu
Huawei Huawei
Intended status: Standards Track R. Cummings, Ed. Intended status: Standards Track R. Cummings, Ed.
National Instruments National Instruments
Expires: May 2017 November 25, 2016 Expires: June 2017 December 5, 2016
YANG Data Model for IEEE 1588v2 YANG Data Model for IEEE 1588v2
draft-ietf-tictoc-1588v2-yang-02 draft-ietf-tictoc-1588v2-yang-03
Abstract Abstract
This document defines a YANG data model for the configuration of This document defines a YANG data model for the configuration of
IEEE 1588-2008 devices and clocks, and also retrieval of the IEEE 1588-2008 devices and clocks, and also retrieval of the
configuration information, data set and running states of IEEE configuration information, data set and running states of IEEE
1588-2008 clocks. 1588-2008 clocks.
Status of this Memo Status of this Memo
skipping to change at page 1, line 42 skipping to change at page 1, line 42
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 25, 2017. This Internet-Draft will expire on June 5, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 30
2. IEEE 1588-2008 YANG Model hierarchy ....................... 5 2. IEEE 1588-2008 YANG Model hierarchy ....................... 5
2.1. Interpretations from IEEE 1588 Working Group ........... 8 2.1. Interpretations from IEEE 1588 Working Group ........... 8
3. IEEE 1588-2008 YANG Module ................................ 9 3. IEEE 1588-2008 YANG Module ................................ 9
4. Security Considerations .................................. 21 4. Security Considerations .................................. 21
5. IANA Considerations ...................................... 22 5. IANA Considerations ...................................... 22
6. References ............................................... 22 6. References ............................................... 22
6.1. Normative References .................................. 22 6.1. Normative References .................................. 22
6.2. Informative References ................................ 22 6.2. Informative References ................................ 22
7. Acknowledgments .......................................... 23 7. Acknowledgments .......................................... 23
Appendix A Transferring YANG Work to IEEE 1588 WG (Informational) Appendix A Transferring YANG Work to IEEE 1588 WG (Informational)
................................................................. 23 ............................................................... 23
A.1. Assumptions for the Transfer .......................... 24 A.1. Assumptions for the Transfer .......................... 24
A.2. Intellectual Property Considerations .................. 25 A.2. Intellectual Property Considerations .................. 25
A.3. Namespace and Module Name ............................. 25 A.3. Namespace and Module Name ............................. 25
A.4. IEEE 1588 YANG Modules in ASCII Format ................ 26 A.4. IEEE 1588 YANG Modules in ASCII Format ................ 26
1. Introduction 1. Introduction
As a synchronization protocol, IEEE 1588-2008 (also known as IEEE As a synchronization protocol, IEEE 1588-2008 (also known as IEEE
1588v2) [IEEE1588] is widely supported in the carrier networks, 1588v2) [IEEE1588] is widely supported in the carrier networks,
industrial networks, automotive networks, and many other industrial networks, automotive networks, and many other
skipping to change at page 3, line 9 skipping to change at page 3, line 9
quality messages. The configuration parameters and state data sets quality messages. The configuration parameters and state data sets
of IEEE 1588-2008 are numerous. of IEEE 1588-2008 are numerous.
According to the concepts described in [RFC3444], IEEE 1588-2008 According to the concepts described in [RFC3444], IEEE 1588-2008
itself provides an information model in its normative itself provides an information model in its normative
specifications for the data sets (in IEEE 1588-2008 clause 8). Some specifications for the data sets (in IEEE 1588-2008 clause 8). Some
standardization organizations including the IETF have specified standardization organizations including the IETF have specified
data models in MIBs (Management Information Bases) for IEEE 1588- data models in MIBs (Management Information Bases) for IEEE 1588-
2008 data sets (e.g. [PTP-MIB], [IEEE8021AS]). These MIBs are 2008 data sets (e.g. [PTP-MIB], [IEEE8021AS]). These MIBs are
typically focused on retrieval of state data using the Simple typically focused on retrieval of state data using the Simple
Network Management Protocol (SNMP), while configuration of PTP data Network Management Protocol (SNMP), furthermore, configuration of
sets is not considered. PTP data sets is not considered in [PTP-MIB].
Some service providers and applications require that the management Some service providers and applications require that the management
of the IEEE 1588-2008 synchronization network be flexible and more of the IEEE 1588-2008 synchronization network be flexible and more
Internet-based (typically overlaid on their transport networks). Internet-based (typically overlaid on their transport networks).
Software Defined Network (SDN) is another driving factor, which Software Defined Network (SDN) is another driving factor, which
demands an improved configuration capability of synchronization demands an improved configuration capability of synchronization
networks. networks.
YANG [RFC6020] is a data modeling language used to model YANG [RFC6020] is a data modeling language used to model
configuration and state data manipulated by network management configuration and state data manipulated by network management
skipping to change at page 4, line 34 skipping to change at page 4, line 34
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
1.2. Terminology 1.2. Terminology
Most terminologies used in this document are extracted from Most terminologies used in this document are extracted from
[IEEE1588]. [IEEE1588].
BC Boundary Clock BC Boundary Clock
DS Data Set DS Data Set
E2E End-to-End E2E End-to-End
EUI Extended Unique Identifier. EUI Extended Unique Identifier.
GPS Global Positioning System GPS Global Positioning System
IANA Internet Assigned Numbers Authority IANA Internet Assigned Numbers Authority
IP Internet Protocol IP Internet Protocol
skipping to change at page 9, line 7 skipping to change at page 9, line 7
The instance number has no usage within PTP messages. The instance number has no usage within PTP messages.
Based on statements in IEEE 1588-2008 subclauses 8.3.1. and 10.1, Based on statements in IEEE 1588-2008 subclauses 8.3.1. and 10.1,
most transparent clock products have interpreted the transparent most transparent clock products have interpreted the transparent
clock data sets to reside as a singleton at the root level of the clock data sets to reside as a singleton at the root level of the
managed product. Since 1588-2008 transparent clocks are domain managed product. Since 1588-2008 transparent clocks are domain
independent, the instance concept is not applicable for domains. independent, the instance concept is not applicable for domains.
3. IEEE 1588-2008 YANG Module 3. IEEE 1588-2008 YANG Module
<CODE BEGINS> file "ietf-ptp-dataset@2016-11-25.yang" <CODE BEGINS> file "ietf-ptp-dataset@2016-12-05.yang"
module ietf-ptp-dataset{ module ietf-ptp-dataset{
namespace "urn:ietf:params:xml:ns:yang:ietf-ptp-dataset"; namespace "urn:ietf:params:xml:ns:yang:ietf-ptp-dataset";
prefix "ptp-dataset"; prefix "ptp-dataset";
organization "IETF TICTOC Working Group"; organization "IETF TICTOC Working Group";
contact contact
"WG Web: http://tools.ietf.org/wg/tictoc/ "WG Web: http://tools.ietf.org/wg/tictoc/
WG List: <mailto:tictoc@ietf.org> WG List: <mailto:tictoc@ietf.org>
WG Chair: Karen O'Donoghue WG Chair: Karen O'Donoghue
<mailto:odonoghue@isoc.org> <mailto:odonoghue@isoc.org>
skipping to change at page 9, line 29 skipping to change at page 9, line 29
<mailto: Yaakov_s@rad.com> <mailto: Yaakov_s@rad.com>
Editor: Yuanlong Jiang Editor: Yuanlong Jiang
<mailto:jiangyuanlong@huawei.com> <mailto:jiangyuanlong@huawei.com>
Editor: Rodney Cummings Editor: Rodney Cummings
<mailto:rodney.cummings@ni.com>"; <mailto:rodney.cummings@ni.com>";
description description
"This YANG module defines a data model for the configuration "This YANG module defines a data model for the configuration
of IEEE 1588-2008 clocks, and also for retrieval of the state of IEEE 1588-2008 clocks, and also for retrieval of the state
data of IEEE 1588-2008 clocks."; data of IEEE 1588-2008 clocks.";
revision "2016-11-25" { revision "2016-12-05" {
description "Version 2.0"; description "Version 3.0";
reference "draft-ietf-tictoc-1588v2-yang"; reference "draft-ietf-tictoc-1588v2-yang";
} }
grouping default-ds-entry { grouping default-ds-entry {
description description
"Collection of members of the default data set."; "Collection of members of the default data set.";
leaf two-step-flag { leaf two-step-flag {
type boolean; type boolean;
description description
skipping to change at page 16, line 41 skipping to change at page 16, line 41
description description
"The base-two logarithm of the mean SyncInterval "The base-two logarithm of the mean SyncInterval
for multicast messages. The rates for unicast for multicast messages. The rates for unicast
transmissions are negotiated separately on a per port transmissions are negotiated separately on a per port
basis and are not constrained by this attribute."; basis and are not constrained by this attribute.";
} }
leaf delay-mechanism { leaf delay-mechanism {
type enumeration { type enumeration {
enum E2E { enum E2E {
value 01; value 1;
description description
"The port uses the delay request-response "The port uses the delay request-response
mechanism."; mechanism.";
} }
enum P2P { enum P2P {
value 02; value 2;
description description
"The port uses the peer delay mechanism."; "The port uses the peer delay mechanism.";
} }
enum DISABLED { enum DISABLED {
value 254; value 254;
description description
"The port does not implement any delay "The port does not implement any delay
mechanism."; mechanism.";
} }
} }
skipping to change at page 23, line 22 skipping to change at page 23, line 22
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011 Shell (SSH)", RFC 6242, June 2011
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, March Protocol (NETCONF) Access Control Model", RFC 6536, March
2012 2012
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Joe Gwinn, Mahesh Jethanandani and The authors would like to thank Joe Gwinn, Mahesh Jethanandani and
Tal Mizrahi for their valuable reviews and suggestions. Tal Mizrahi for their valuable reviews and suggestions, and thank
Benoit Claise and Radek Krejci for their validation of the YANG
module.
Appendix A Transferring YANG Work to IEEE 1588 WG (Informational) Appendix A Transferring YANG Work to IEEE 1588 WG (Informational)
This appendix describes a future plan to transition responsibility This appendix describes a future plan to transition responsibility
for IEEE 1588 YANG modules from the IETF TICTOC Working Group (WG) for IEEE 1588 YANG modules from the IETF TICTOC Working Group (WG)
to the IEEE 1588 WG, which develops the time synchronization to the IEEE 1588 WG, which develops the time synchronization
technology that the YANG modules are designed to manage. technology that the YANG modules are designed to manage.
This appendix is forward-looking with regard to future This appendix is forward-looking with regard to future
standardization roadmaps in IETF and IEEE. Since those roadmaps standardization roadmaps in IETF and IEEE. Since those roadmaps
 End of changes. 12 change blocks. 
14 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/