draft-ietf-ntp-yang-data-model-00.txt   draft-ietf-ntp-yang-data-model-01.txt 
Network Working Group N. Wu Network Working Group N. Wu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track A. Kumar S N Intended status: Standards Track A. Kumar S N
Expires: January 18, 2018 RtBrick Inc. Expires: May 1, 2018 RtBrick Inc.
Y. Zhao Y. Zhao
Ericsson Ericsson
D. Dhody D. Dhody
A. Sinha A. Sinha
Huawei Huawei
July 17, 2017 October 28, 2017
A YANG Data Model for NTP A YANG Data Model for NTP
draft-ietf-ntp-yang-data-model-00 draft-ietf-ntp-yang-data-model-01
Abstract Abstract
This document defines a YANG data model for Network Time Protocol This document defines a YANG data model for Network Time Protocol
implementations. The data model includes configuration data and implementations. The data model includes configuration data and
state data. state data.
Requirements Language Requirements Language
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 this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 18, 2018. This Internet-Draft will expire on May 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (https://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Operational State . . . . . . . . . . . . . . . . . . . . 3 1.1. Operational State . . . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. NTP data model . . . . . . . . . . . . . . . . . . . . . . . 3 2. NTP data model . . . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship with NTPv4-MIB . . . . . . . . . . . . . . . . . 6 3. Relationship with NTPv4-MIB . . . . . . . . . . . . . . . . . 6
4. Relationship with RFC7317 . . . . . . . . . . . . . . . . . . 7 4. Relationship with RFC7317 . . . . . . . . . . . . . . . . . . 7
5. NTP YANG Module . . . . . . . . . . . . . . . . . . . . . . . 8 5. NTP YANG Module . . . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 6. Usage Example . . . . . . . . . . . . . . . . . . . . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 6.1. Unicast association . . . . . . . . . . . . . . . . . . . 27
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26 6.2. Refclock master . . . . . . . . . . . . . . . . . . . . . 29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.3. Authentication configuration . . . . . . . . . . . . . . 30
9.1. Normative References . . . . . . . . . . . . . . . . . . 26 6.4. Access configuration . . . . . . . . . . . . . . . . . . 31
9.2. Informative References . . . . . . . . . . . . . . . . . 27 6.5. Multicast configuration . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 6.6. Manycast configuration . . . . . . . . . . . . . . . . . 35
6.7. Clock state . . . . . . . . . . . . . . . . . . . . . . . 38
6.8. Get all association . . . . . . . . . . . . . . . . . . . 38
6.9. Global statistic . . . . . . . . . . . . . . . . . . . . 40
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
8. Security Considerations . . . . . . . . . . . . . . . . . . . 41
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.1. Normative References . . . . . . . . . . . . . . . . . . 41
10.2. Informative References . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for Network Time This document defines a YANG [RFC6020] data model for Network Time
Protocol [RFC5905] implementations. Protocol [RFC5905] implementations.
The data model convers configuration of system parameters of NTP, The data model convers configuration of system parameters of NTP,
such as access rules, authentication and VRF binding, and also such as access rules, authentication and VRF binding, and also
associations of NTP in different modes and parameters of per- associations of NTP in different modes and parameters of per-
interface. It also provides information about running state of NTP interface. It also provides information about running state of NTP
skipping to change at page 3, line 16 skipping to change at page 3, line 22
NTP Operational State is included in the same tree as NTP NTP Operational State is included in the same tree as NTP
configuration, consistent with Network Management Datastore configuration, consistent with Network Management Datastore
Architecture [I-D.ietf-netmod-revised-datastores]. NTP current state Architecture [I-D.ietf-netmod-revised-datastores]. NTP current state
and statistics are also maintained in the operational state. and statistics are also maintained in the operational state.
Additionally, the operational state also include the associations Additionally, the operational state also include the associations
state. state.
1.2. Terminology 1.2. Terminology
The terminology used in this document is aligned to [RFC5905].
1.3. Tree Diagrams 1.3. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. This document uses the graphical representation of
follows: data models defined in [I-D.ietf-netmod-yang-tree-diagrams].
o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration
data (read-write), and "ro" means state data (read-only).
o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
2. NTP data model 2. NTP data model
This document defines the YANG module "ietf-ntp", which has the This document defines the YANG module "ietf-ntp", which has the
following structure: following structure:
module: ietf-ntp module: ietf-ntp
+--rw ntp! +--rw ntp!
| +--rw port? uint16 +--rw port? uint16
| +--rw refclock-master! +--rw refclock-master!
| | +--rw master-stratum? ntp-stratum | +--rw master-stratum? ntp-stratum
+--rw authentication
| +--rw auth-enabled? boolean
| +--rw trusted-keys* [key-id]
| | +--rw key-id -> /ntp/authentication/authentication-keys/key-id
| +--rw authentication-keys* [key-id]
| +--rw key-id uint32
| +--rw algorithm? identityref
| +--rw password? ianach:crypt-hash
+--rw access-rules
| +--rw access-rule* [access-mode]
| +--rw access-mode access-modes
| +--rw acl? -> /acl:access-lists/acl/acl-name
+--ro clock-state
| +--ro system-status
| +--ro clock-state ntp-clock-status
| +--ro clock-stratum ntp-stratum
| +--ro clock-refid union
| +--ro associations-address? -> /ntp/associations/address
| +--ro associations-local-mode? -> /ntp/associations/local-mode
| +--ro associations-isConfigured? -> /ntp/associations/isConfigured
| +--ro nominal-freq decimal64
| +--ro actual-freq decimal64
| +--ro clock-precision uint8
| +--ro clock-offset? decimal64
| +--ro root-delay? decimal64
| +--ro root-dispersion? decimal64
| +--ro reference-time? yang:date-and-time
| +--ro sync-state ntp-sync-state
+--rw unicast* [address type]
| +--rw address inet:host
| +--rw type unicast-configuration-type
| +--rw authentication | +--rw authentication
| | +--rw auth-enabled? boolean | | +--rw (authentication-type)?
| | +--rw trusted-keys* [key-id] | | +--:(symmetric-key)
| | | +--rw key-id leafref | | +--rw key-id? -> /ntp/authentication/authentication-keys/key-id
| | +--rw authentication-keys* [key-id] | +--rw prefer? boolean
| | +--rw key-id uint32 | +--rw burst? boolean
| | +--rw algorithm? identityref | +--rw iburst? boolean
| | +--rw password? ianach:crypt-hash | +--rw source? if:interface-ref
| +--rw access-rules | +--rw minpoll? ntp-minpoll
| | +--rw access-rule* [access-mode] | +--rw maxpoll? ntp-maxpoll
| | +--rw access-mode access-modes | +--rw port? uint16
| | +--rw acl? -> /acl:access-lists/acl/acl-name | +--rw version? ntp-version
| +--ro clock-state +--ro associations* [address local-mode isConfigured]
| | +--ro system-status | +--ro address inet:host
| | +--ro clock-state? ntp-clock-status | +--ro local-mode association-modes
| | +--ro clock-stratum? ntp-stratum | +--ro isConfigured boolean
| | +--ro clock-refid? union | +--ro stratum? ntp-stratum
| | +--ro nominal-freq? decimal64 | +--ro refid? union
| | +--ro actual-freq? decimal64 | +--ro authentication? -> /ntp/authentication/authentication-keys/key-id
| | +--ro clock-precision? uint8 | +--ro prefer? boolean
| | +--ro clock-offset? decimal64 | +--ro peer-interface? if:interface-ref
| | +--ro root-delay? decimal64 | +--ro minpoll? ntp-minpoll
| | +--ro root-dispersion? decimal64 | +--ro maxpoll? ntp-maxpoll
| | +--ro peer-dispersion? decimal64 | +--ro port? uint16
| | +--ro reference-time? yang:date-and-time | +--ro version? ntp-version
| | +--ro sync-state? ntp-sync-state | +--ro reach? uint8
| +--rw associations* [address association-type] | +--ro unreach? uint8
| | +--rw address inet:host | +--ro poll? uint8
| | +--rw association-type association-modes | +--ro now? uint32
| | +--rw authentication | +--ro offset? decimal64
| | | +--rw (authentication-type)? | +--ro delay? decimal64
| | | +--:(symmetric-key) | +--ro dispersion? decimal64
| | | +--rw key-id? leafref | +--ro originate-time? yang:date-and-time
| | +--rw prefer? boolean | +--ro receive-time? yang:date-and-time
| | +--rw burst? boolean | +--ro transmit-time? yang:date-and-time
| | +--rw iburst? boolean | +--ro input-time? yang:date-and-time
| | +--rw source? if:interface-ref | +--ro ntp-statistics
| | +--rw minpoll? ntp-minpoll | +--ro packet-sent? yang:counter32
| | +--rw maxpoll? ntp-maxpoll | +--ro packet-sent-fail? yang:counter32
| | +--rw port? uint16 | +--ro packet-received? yang:counter32
| | +--rw version? ntp-version | +--ro packet-dropped? yang:counter32
| | +--ro stratum? ntp-stratum +--rw interfaces
| | +--ro refid? union | +--rw interface* [name]
| | +--ro reach? uint8 | +--rw name if:interface-ref
| | +--ro unreach? uint8 | +--rw broadcast-server!
| | +--ro poll? uint8 | | +--rw ttl? uint8
| | +--ro now? uint32 | | +--rw authentication
| | +--ro offset? decimal64 | | | +--rw (authentication-type)?
| | +--ro delay? decimal64 | | | +--:(symmetric-key)
| | +--ro dispersion? decimal64 | | | +--rw key-id? -> /ntp/authentication/authentication-keys/key-id
| | +--ro originate-time? yang:date-and-time | | +--rw minpoll? ntp-minpoll
| | +--ro receive-time? yang:date-and-time | | +--rw maxpoll? ntp-maxpoll
| | +--ro transmit-time? yang:date-and-time | | +--rw port? uint16
| | +--ro input-time? yang:date-and-time | | +--rw version? ntp-version
| | +--ro ntp-statistics | +--rw broadcast-client!
| | +--ro packet-sent? yang:counter32 | +--rw multicast-server* [address]
| | +--ro packet-sent-fail? yang:counter32 | | +--rw address rt-types:ip-multicast-group-address
| | +--ro packet-received? yang:counter32 | | +--rw ttl? uint8
| | +--ro packet-dropped? yang:counter32 | | +--rw authentication
| +--rw interface | | | +--rw (authentication-type)?
| +--rw interface* [interface] | | | +--:(symmetric-key)
| +--rw interface if:interface-ref | | | +--rw key-id? -> /ntp/authentication/authentication-keys/key-id
| +--rw broadcast-server! | | +--rw minpoll? ntp-minpoll
| | +--rw ttl? uint8 | | +--rw maxpoll? ntp-maxpoll
| | +--rw authentication | | +--rw port? uint16
| | | +--rw (authentication-type)? | | +--rw version? ntp-version
| | | +--:(symmetric-key) | +--rw multicast-client* [address]
| | | +--rw key-id? leafref | | +--rw address rt-types:ip-multicast-group-address
| | +--rw minpoll? ntp-minpoll | +--rw manycast-server* [address]
| | +--rw maxpoll? ntp-maxpoll | | +--rw address rt-types:ip-multicast-group-address
| | +--rw port? uint16 | +--rw manycast-client* [address]
| | +--rw version? ntp-version | +--rw address rt-types:ip-multicast-group-address
| +--rw broadcast-client! | +--rw authentication
| +--rw multicast-server* [address] | | +--rw (authentication-type)?
| | +--rw address | | +--:(symmetric-key)
| | | rt-types:ip-multicast-group-address | | +--rw key-id? -> /ntp/authentication/authentication-keys/key-id
| | +--rw ttl? uint8 | +--rw ttl? uint8
| | +--rw authentication | +--rw minclock? uint8
| | | +--rw (authentication-type)? | +--rw maxclock? uint8
| | | +--:(symmetric-key) | +--rw beacon? uint8
| | | +--rw key-id? leafref | +--rw minpoll? ntp-minpoll
| | +--rw minpoll? ntp-minpoll | +--rw maxpoll? ntp-maxpoll
| | +--rw maxpoll? ntp-maxpoll | +--rw port? uint16
| | +--rw port? uint16 | +--rw version? ntp-version
| | +--rw version? ntp-version
| +--rw multicast-client* [address]
| | +--rw address rt-types:ip-multicast-group-address
| +--rw manycast-server* [address]
| | +--rw address rt-types:ip-multicast-group-address
| +--rw manycast-client* [address]
| +--rw address
| | rt-types:ip-multicast-group-address
| +--rw authentication
| | +--rw (authentication-type)?
| | +--:(symmetric-key)
| | +--rw key-id? leafref
| +--rw ttl? uint8
| +--rw minclock? uint8
| +--rw maxclock? uint8
| +--rw beacon? uint8
| +--rw minpoll? ntp-minpoll
| +--rw maxpoll? ntp-maxpoll
| +--rw port? uint16
| +--rw version? ntp-version
+--ro ntp-statistics +--ro ntp-statistics
+--ro packet-sent? yang:counter32 +--ro packet-sent? yang:counter32
+--ro packet-sent-fail? yang:counter32 +--ro packet-sent-fail? yang:counter32
+--ro packet-received? yang:counter32 +--ro packet-received? yang:counter32
+--ro packet-dropped? yang:counter32 +--ro packet-dropped? yang:counter32
This data model defines two primary containers, one for NTP This data model defines one top-level container which includes both
configuration and the other is for NTP running state. The NTP the NTP configuration and the NTP running state including access
configuration container includes data nodes for access rules, rules, authentication, associations, unicast, interfaces, system
authentication, associations and interfaces. In the NTP running status and associations.
state container, there are data nodes for system status and
associations.
3. Relationship with NTPv4-MIB 3. Relationship with NTPv4-MIB
If the device implements the NTPv4-MIB [RFC5907], data nodes in If the device implements the NTPv4-MIB [RFC5907], data nodes in
container ntp and ntp-state from YANG module can be mapped to table container ntp and ntp-state from YANG module can be mapped to table
entries in NTPv4-MIB. entries in NTPv4-MIB.
The following tables list the YANG data nodes with corresponding The following tables list the YANG data nodes with corresponding
objects in the NTPv4-MIB. objects in the NTPv4-MIB.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
+--------------------------------------+---------------------+ +--------------------------------------+---------------------+
| YANG data nodes in /ntp/associations | NTPv4-MIB objects | | YANG data nodes in /ntp/associations | NTPv4-MIB objects |
+--------------------------------------+---------------------+ +--------------------------------------+---------------------+
| address | ntpAssocAddressType | | address | ntpAssocAddressType |
| | ntpAssocAddress | | | ntpAssocAddress |
+--------------------------------------+---------------------+ +--------------------------------------+---------------------+
YANG NTP Configuration Data Nodes and Related NTPv4-MIB Objects YANG NTP Configuration Data Nodes and Related NTPv4-MIB Objects
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| YANG data nodes in /ntp-state | NTPv4-MIB objects | | YANG data nodes in /ntp/clock- | NTPv4-MIB objects |
| /system-status | | | state/system-status | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| clock-state | ntpEntStatusCurrentMode | | clock-state | ntpEntStatusCurrentMode |
| clock-stratum | ntpEntStatusStratum | | clock-stratum | ntpEntStatusStratum |
| clock-refid | ntpEntStatusActiveRefSourceId | | clock-refid | ntpEntStatusActiveRefSourceId |
| | ntpEntStatusActiveRefSourceName | | | ntpEntStatusActiveRefSourceName |
| clock-precision | ntpEntTimePrecision | | clock-precision | ntpEntTimePrecision |
| clock-offset | ntpEntStatusActiveOffset | | clock-offset | ntpEntStatusActiveOffset |
| root-dispersion | ntpEntStatusDispersion | | root-dispersion | ntpEntStatusDispersion |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
+-------------------------------------------+-----------------------+ +---------------------------------------+---------------------------+
| YANG data nodes in /ntp-state | NTPv4-MIB objects | | YANG data nodes in /ntp/associations/ | NTPv4-MIB objects |
| /associations-status/association-status/ | | +---------------------------------------+---------------------------+
+-------------------------------------------+-----------------------+ | address | ntpAssocAddressType |
| association-source | ntpAssocAddressType | | | ntpAssocAddress |
| | ntpAssocAddress | | stratum | ntpAssocStratum |
| association-stratum | ntpAssocStratum | | refid | ntpAssocRefId |
| association-refid | ntpAssocRefId | | offset | ntpAssocOffset |
| association-offset | ntpAssocOffset | | delay | ntpAssocStatusDelay |
| association-delay | ntpAssocStatusDelay | | dispersion | ntpAssocStatusDispersion |
| association-dispersion | ntpAssocStatusDispers | | ntp-statistics/packet-sent | ntpAssocStatOutPkts |
| | ion | | ntp-statistics/packet-received | ntpAssocStatInPkts |
| association-sent | ntpAssocStatOutPkts | | ntp-statistics/packet-dropped | ntpAssocStatProtocolError |
| association-received | ntpAssocStatInPkts | +---------------------------------------+---------------------------+
| association-dropped | ntpAssocStatProtocolE |
| | rror |
+-------------------------------------------+-----------------------+
YANG NTP State Data Nodes and Related NTPv4-MIB Objects YANG NTP State Data Nodes and Related NTPv4-MIB Objects
4. Relationship with RFC7317 4. Relationship with RFC7317
This section describes the relationship with NTP definition in This section describes the relationship with NTP definition in
Section 3.2 System Time Management of [RFC7317] . YANG data nodes in Section 3.2 System Time Management of [RFC7317] . YANG data nodes in
/ntp/ also supports interface related configurations which is not /ntp/ also supports interface related configurations which is not
supported in /system/ntp supported in /system/ntp
+----------------------------------+--------------------------------+ +---------------------------+--------------------------------+
| YANG data nodes in /ntp/ | YANG data nodes in /system/ntp | | YANG data nodes in /ntp/ | YANG data nodes in /system/ntp |
+----------------------------------+--------------------------------+ +---------------------------+--------------------------------+
| ntp-enabled | enabled | | ntp-enabled | enabled |
| associations/association | server | | unicast | server |
| | server/name | | | server/name |
| associations/association/address | server/transport/udp/address | | unicast/address | server/transport/udp/address |
| ntp-enabled/port | server/transport/udp/port | | unicast/port | server/transport/udp/port |
| associations/association-type | server/association-type | | unicast/type | server/association-type |
| associations/association/iburst | server/iburst | | unicast/iburst | server/iburst |
| associations/association/prefer | server/prefer | | unicast/prefer | server/prefer |
+----------------------------------+--------------------------------+ +---------------------------+--------------------------------+
YANG NTP Configuration Data Nodes and counterparts in RFC7317 Objects YANG NTP Configuration Data Nodes and counterparts in RFC7317 Objects
5. NTP YANG Module 5. NTP YANG Module
<CODE BEGINS> file "ietf-ntp@2017-05-12.yang" <CODE BEGINS> file "ietf-ntp@2017-10-28.yang"
module ietf-ntp { module ietf-ntp {
namespace "urn:ietf:params:xml:ns:yang:ietf-ntp";
prefix "ntp";
import ietf-yang-types {
prefix "yang";
}
import ietf-inet-types {
prefix "inet";
}
import ietf-interfaces {
prefix "if";
}
import iana-crypt-hash {
prefix ianach;
}
import ietf-key-chain {
prefix "key-chain";
}
import ietf-access-control-list {
prefix "acl";
}
import ietf-routing-types {
prefix "rt-types";
}
organization
"IETF NTP (Network Time Protocol) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/ntp/>
WG List: <mailto: ntpwg@lists.ntp.org
WG Chair: Karen O'Donoghue
<mailto: odonoghue@isoc.org>
Editor: Eric Wu
<mailto:eric.wu@huawei.com>
Editor: Anil Kumar S N
<mailto:anil.ietf@gmail.com>
Editor: Yi Zhao
<mailto:yi.z.zhao@ericsson.com>
Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com>
Editor: Ankit Kumar Sinha
<mailto:ankit.ietf@gmail.com>";
description
"This YANG module defines essential components for the
management of a routing subsystem.
Copyright (c) 2017 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant to,
and subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices.";
revision 2017-05-12 { namespace "urn:ietf:params:xml:ns:yang:ietf-ntp";
description
"Updated revision.";
reference
"RFC XXXX: A YANG Data Model for NTP Management";
}
/* Typedef Definitions */ prefix "ntp";
typedef ntp-stratum {
type uint8 {
range "1..16";
}
description
"The level of each server in the hierarchy is defined by
a stratum number. Primary servers are assigned stratum
one; secondary servers at each lower level are assigned
stratum numbers one greater than the preceding level";
}
typedef ntp-version { import ietf-yang-types {
type uint8 { prefix "yang";
range "1..4"; }
}
default "3";
description
"The current NTP version supported by corresponding
association.";
}
typedef ntp-minpoll { import ietf-inet-types {
type uint8 { prefix "inet";
range "4..17"; }
}
default "6";
description
"The minimum poll exponent for this NTP association.";
}
typedef ntp-maxpoll { import ietf-interfaces {
type uint8 { prefix "if";
range "4..17"; }
}
default "10";
description
"The maximul poll exponent for this NTP association.";
}
typedef access-modes { import iana-crypt-hash {
type enumeration { prefix ianach;
enum peer { }
value "0";
description
"Sets the fully access authority. Both time
request and control query can be performed
on the local NTP service, and the local clock
can be synchronized to the remote server.";
}
enum server {
value "1";
description
"Enables the server access and query.
Both time requests and control query can be
performed on the local NTP service, but the
local clock cannot be synchronized to the
remote server.";
}
enum synchronization {
value "2";
description
"Enables the server to access.
Only time request can be performed on the
local NTP service.";
}
enum query {
value "3";
description
"Sets the maximum access limitation.
Control query can be performed only on the
local NTP service.";
}
}
description
"This defines NTP acess modes.";
}
typedef association-modes { import ietf-key-chain {
type enumeration { prefix "key-chain";
enum server { }
value "0";
description
"Use client association mode. This device
will not provide synchronization to the
configured NTP server.";
}
enum peer {
value "1";
description
"Use symmetric active association mode.
This device may provide synchronization
to the configured NTP server.";
}
enum pool {
value "2";
description
"Use client association mode with one or
more of the NTP servers found by DNS
resolution of the domain name given by
the 'address' leaf. This device will not
provide synchronization to the servers.";
}
}
description
"This defines NTP association modes.";
}
typedef ntp-clock-status { import ietf-access-control-list {
type enumeration { prefix "acl";
enum synchronized { }
value "0"; import ietf-routing-types {
description prefix "rt-types";
"Indicates that the local clock has been }
synchronized with an NTP server or
the reference clock.";
}
enum unsynchronized {
value "1";
description
"Indicates that the local clock has not been
synchronized with any NTP server.";
}
}
description
"This defines NTP clock status.";
}
typedef ntp-sync-state { organization
type enumeration { "IETF NTP (Network Time Protocol) Working Group";
enum clock-not-set {
value "0";
description
"Indicates the clock is not updated.";
}
enum freq-set-by-cfg {
value "1";
description
"Indicates the clock frequency is set by
NTP configuration.";
}
enum clock-set {
value "2";
description
"Indicates the clock is set.";
}
enum freq-not-determined {
value "3";
description
"Indicates the clock is set but the frequency
is not determined.";
}
enum clock-synchronized {
value "4";
description
"Indicates that the clock is synchronized";
}
enum spike {
value "5";
description
"Indicates a time difference of more than 128
milliseconds is detected between NTP server
and client clock. The clock change will take
effect in XXX seconds.";
}
}
description
"This defines NTP clock sync states.";
}
/* Groupings */ contact
grouping authentication-key { "WG Web: <http://tools.ietf.org/wg/ntp/>
description WG List: <mailto: ntpwg@lists.ntp.org
"To define an authentication key for a Network Time WG Chair: Karen O'Donoghue
Protocol (NTP) time source."; <mailto: odonoghue@isoc.org>
leaf key-id { Editor: Eric Wu
type uint32 { <mailto:eric.wu@huawei.com>
range "1..max"; Editor: Anil Kumar S N
} <mailto:anil.ietf@gmail.com>
description Editor: Yi Zhao
"Authentication key identifier."; <mailto:yi.z.zhao@ericsson.com>
} Editor: Dhruv Dhody
leaf algorithm { <mailto:dhruv.ietf@gmail.com>
type identityref { Editor: Ankit Kumar Sinha
base key-chain:crypto-algorithm; <mailto:ankit.ietf@gmail.com>";
} description
description "This YANG module defines essential components for the
"Authentication algorithm."; management of a routing subsystem.
}
leaf password {
type ianach:crypt-hash;
description "Clear or encrypted mode for password text.";
} Copyright (c) 2017 IETF Trust and the persons identified
} as authors of the code. All rights reserved.
grouping authentication-type-param { Redistribution and use in source and binary forms,
description with or without modification, is permitted pursuant to,
"Authentication type."; and subject to the license terms contained in, the
choice authentication-type { Simplified BSD License set forth in Section 4.c of the
description IETF Trust's Legal Provisions Relating to IETF Documents
"Type of authentication."; (http://trustee.ietf.org/license-info).
case symmetric-key {
leaf key-id {
type leafref {
path "/ntp:ntp/ntp:authentication/"
+ "ntp:authentication-keys/ntp:key-id";
}
description
"Authentication key id referenced in this
association.";
}
}
}
}
grouping statistics { This version of this YANG module is part of RFC XXXX;
description see the RFC itself for full legal notices.";
"NTP packet statistic.";
leaf packet-sent {
type yang:counter32;
description
"Indicates the total number of packets sent.";
}
leaf packet-sent-fail {
type yang:counter32;
description
"Indicates the number of times packet
sending failed.";
}
leaf packet-received {
type yang:counter32;
description
"Indicates the total number of packets received.";
}
leaf packet-dropped {
type yang:counter32;
description
"Indicates the number of packets dropped.";
}
}
grouping comman-attributes {
description
"NTP common attributes for configuration.";
leaf minpoll {
type ntp-minpoll;
description
"The minimum poll interval used in this association.";
}
leaf maxpoll {
type ntp-maxpoll;
description
"The maximul poll interval used in this association.";
}
leaf port {
type uint16 {
range "123 | 1025..max";
}
default "123";
description
"Specify the port used to send NTP packets.";
}
leaf version {
type ntp-version;
description
"NTP version.";
}
}
/* Configuration data nodes */ revision 2017-10-28 {
container ntp { description
presence "Updated revision.";
"NTP is enable"; reference
description "RFC XXXX: A YANG Data Model for NTP Management";
"Configuration parameters for NTP."; }
leaf port {
type uint16 {
range "123 | 1025..max";
}
default "123";
description
"Specify the port used to send NTP packets.";
}
container refclock-master { /* Typedef Definitions */
presence typedef ntp-stratum {
"NTP master clock is enable"; type uint8 {
description range "1..16";
"Configures the device as NTP server.";
leaf master-stratum {
type ntp-stratum;
default "16";
description
"Stratum level from which NTP
clients get their time synchronized.";
}
}
container authentication {
description
"Configuration of authentication.";
leaf auth-enabled {
type boolean;
default false;
description
"Controls whether NTP authentication is enabled
or disabled on this device.";
}
list trusted-keys {
key "key-id";
description
"List of keys trusted by NTP.";
leaf key-id {
type leafref {
path "/ntp:ntp/ntp:authentication/"
+ "ntp:authentication-keys/ntp:key-id";
}
description
"The key trusted by NTP.";
}
}
list authentication-keys {
key "key-id";
uses authentication-key;
description
"List of authentication key.";
}
} }
description
"The level of each server in the hierarchy is defined by
a stratum number. Primary servers are assigned stratum
one; secondary servers at each lower level are assigned
stratum numbers one greater than the preceding level";
}
container access-rules { typedef ntp-version {
description type uint8 {
"Configuration of access rules."; range "1..4";
list access-rule {
key "access-mode";
description
"List of access rules.";
leaf access-mode {
type access-modes;
description
"NTP access mode.";
}
leaf acl {
type leafref {
path "/acl:access-lists/acl:acl/acl:acl-name";
}
description
"NTP ACL.";
}
}
} }
default "3";
description
"The current NTP version supported by corresponding
association.";
}
container clock-state { typedef ntp-minpoll {
config "false"; type uint8 {
description range "4..17";
"Operational state of the NTP."; }
default "6";
container system-status { description
description "The minimum poll exponent for this NTP association.";
"System status of NTP."; }
leaf clock-state {
type ntp-clock-status;
description "Indicates the state of system clock.";
}
leaf clock-stratum {
type ntp-stratum;
description
"Indicates the stratum of the reference clock.";
}
leaf clock-refid {
type union {
type inet:ipv4-address;
type binary {
length "4";
}
type string {
length "4";
}
}
description
"IPv4 address or first 32 bits of the MD5 hash of
the IPv6 address or reference clock of the peer to
which clock is synchronized.";
}
leaf nominal-freq {
type decimal64 {
fraction-digits 4;
} typedef ntp-maxpoll {
description type uint8 {
"Indicates the nominal frequency of the range "4..17";
local clock, in Hz.";
}
leaf actual-freq {
type decimal64 {
fraction-digits 4;
}
description
"Indicates the actual frequency of the
local clock, in Hz.";
}
leaf clock-precision {
type uint8;
description
"Precision of the clock of this system
in Hz.(prec=2^(-n))";
}
leaf clock-offset {
type decimal64 {
fraction-digits 4;
}
description
"Offset of clock to synchronized peer,
in milliseconds.";
}
leaf root-delay {
type decimal64 {
fraction-digits 2;
}
description
"Total delay along path to root clock,
in milliseconds.";
}
leaf root-dispersion {
type decimal64 {
fraction-digits 2;
}
description
"Indicates the dispersion between the local clock
and the master reference clock, in milliseconds.";
}
leaf peer-dispersion {
type decimal64 {
fraction-digits 2;
}
description
"Indicates the dispersion between the local clock
and the peer clock, in milliseconds.";
}
leaf reference-time {
type yang:date-and-time;
description
"Indicates reference timestamp.";
}
leaf sync-state {
type ntp-sync-state;
description
"Indicates the synchronization status of
the local clock.";
}
}
} }
default "10";
description
"The maximul poll exponent for this NTP association.";
}
list associations { typedef access-modes {
key "address association-type"; type enumeration {
description enum peer {
"list of association."; value "0";
leaf address {
type inet:host;
description description
"The address of this association."; "Sets the fully access authority. Both time
request and control query can be performed
on the local NTP service, and the local clock
can be synchronized to the remote server.";
} }
leaf association-type { enum server {
type association-modes; value "1";
description description
"The desired association type for this NTP server."; "Enables the server access and query.
Both time requests and control query can be
performed on the local NTP service, but the
local clock cannot be synchronized to the
remote server.";
} }
container authentication{ enum synchronization {
value "2";
description description
"Authentication type."; "Enables the server to access.
uses authentication-type-param; Only time request can be performed on the
local NTP service.";
} }
leaf prefer { enum query {
type boolean; value "3";
default "false";
description description
"Whether this association is preferred."; "Sets the maximum access limitation.
Control query can be performed only on the
local NTP service.";
} }
leaf burst { }
type boolean; description
default "false"; "This defines NTP acess modes.";
}
typedef unicast-configuration-type {
type enumeration {
enum server {
value "0";
description description
"Sends a series of packets instead of a single packet "Use client association mode. This device
within each synchronization interval to achieve faster will not provide synchronization to the
synchronization."; configured NTP server.";
} }
leaf iburst { enum peer {
type boolean; value "1";
default "false";
description description
"Sends a series of packets instead of a single packet "Use symmetric active association mode.
within the initial synchronization interval to achieve This device may provide synchronization
faster initial synchronization."; to the configured NTP server.";
} }
leaf source { }
type if:interface-ref; description
"This defines NTP unicast mode of operation.";
}
typedef association-modes {
type enumeration {
enum client {
value "0";
description description
"The interface whose ip address this association used "Use client association mode(mode 3).
as source address."; This device will not provide synchronization
to the configured NTP server.";
} }
uses comman-attributes { enum active {
value "1";
description description
"Common attribute like port, version, min and max poll."; "Use symmetric active association mode(mode 1).
This device may synchronize with its NTP peer,
or provide synchronization to configured NTP peer.";
} }
leaf stratum { enum passive {
type ntp-stratum; value "2";
config "false";
description description
"Indicates the stratum of the reference clock."; "Use symmetric passive association mode(mode 2).
This device has learnt this asso dynamically.
This device may synchronize with its NTP peer.";
} }
leaf refid { enum broadcast {
type union { value "3";
type inet:ipv4-address;
type binary {
length "4";
}
type string {
length "4";
}
}
config "false";
description description
"Reference clock type or address for the peer."; "Use broadcast mode(mode 5).
This mode defines that its eigther working
as broadcast-server or multicast-server.";
} }
leaf reach { enum broadcast-client {
type uint8; value "4";
config "false";
description description
"Indicates the reachability of the configured "This mode defines that its eigther working
server or peer."; as broadcast-client or multicast-client.";
} }
leaf unreach { }
type uint8; description
config "false"; "This defines NTP association modes.";
}
typedef ntp-clock-status {
type enumeration {
enum synchronized {
value "0";
description description
"Indicates the unreachability of the configured "Indicates that the local clock has been
server or peer."; synchronized with an NTP server or
the reference clock.";
} }
leaf poll { enum unsynchronized {
type uint8; value "1";
config "false";
description description
"Indicates the polling interval for current, "Indicates that the local clock has not been
in seconds."; synchronized with any NTP server.";
} }
leaf now { }
type uint32; description
config "false"; "This defines NTP clock status.";
}
typedef ntp-sync-state {
type enumeration {
enum clock-not-set {
value "0";
description description
"Indicates the time since the NTP packet was "Indicates the clock is not updated.";
not received or last synchronized, in seconds.";
} }
leaf offset { enum freq-set-by-cfg {
type decimal64 { value "1";
fraction-digits 4;
}
config "false";
description description
"Indicates the offset between the local clock "Indicates the clock frequency is set by
and the superior reference clock."; NTP configuration.";
} }
leaf delay { enum clock-set {
type decimal64 { value "2";
fraction-digits 2;
}
config "false";
description description
"Indicates the delay between the local clock "Indicates the clock is set.";
and the superior reference clock.";
} }
leaf dispersion { enum freq-not-determined {
type decimal64 { value "3";
fraction-digits 2;
}
config "false";
description description
"Indicates the dispersion between the local "Indicates the clock is set but the frequency
clock and the superior reference clock."; is not determined.";
} }
leaf originate-time { enum clock-synchronized {
type yang:date-and-time; value "4";
config "false";
description description
"Indicates packet originate timestamp(T1)."; "Indicates that the clock is synchronized";
} }
leaf receive-time { enum spike {
type yang:date-and-time; value "5";
config "false";
description description
"Indicates packet receive timestamp(T2)."; "Indicates a time difference of more than 128
milliseconds is detected between NTP server
and client clock. The clock change will take
effect in XXX seconds.";
} }
leaf transmit-time { }
type yang:date-and-time; description
config "false"; "This defines NTP clock sync states.";
description }
"Indicates packet transmit timestamp(T3).";
/* Groupings */
grouping authentication-key {
description
"To define an authentication key for a Network Time
Protocol (NTP) time source.";
leaf key-id {
type uint32 {
range "1..max";
} }
leaf input-time { description
type yang:date-and-time; "Authentication key identifier.";
config "false"; }
description leaf algorithm {
"Indicates packet input timestamp(T4)."; type identityref {
base key-chain:crypto-algorithm;
} }
container ntp-statistics { description
config "false"; "Authentication algorithm.";
description }
"Per Peer packet send and receive statistic."; leaf password {
uses statistics { type ianach:crypt-hash;
description description "Clear or encrypted mode for password text.";
"NTP send and receive packet statistic."; }
}
grouping authentication-type-param {
description
"Authentication type.";
choice authentication-type {
description
"Type of authentication.";
case symmetric-key {
leaf key-id {
type leafref {
path "/ntp:ntp/ntp:authentication/"
+ "ntp:authentication-keys/ntp:key-id";
}
description
"Authentication key id referenced in this
association.";
} }
} }
} }
}
container interface { grouping statistics {
description
"NTP packet statistic.";
leaf packet-sent {
type yang:counter32;
description description
"Configuration parameters for NTP interfaces."; "Indicates the total number of packets sent.";
list interface { }
key "interface"; leaf packet-sent-fail {
type yang:counter32;
description
"Indicates the number of times packet
sending failed.";
}
leaf packet-received {
type yang:counter32;
description
"Indicates the total number of packets received.";
}
leaf packet-dropped {
type yang:counter32;
description
"Indicates the number of packets dropped.";
}
}
grouping comman-attributes {
description
"NTP common attributes for configuration.";
leaf minpoll {
type ntp-minpoll;
description
"The minimum poll interval used in this association.";
}
leaf maxpoll {
type ntp-maxpoll;
description
"The maximul poll interval used in this association.";
}
leaf port {
type uint16 {
range "123 | 1025..max";
}
default "123";
description
"Specify the port used to send NTP packets.";
}
leaf version {
type ntp-version;
description
"NTP version.";
}
}
grouping association-ref {
description
"Reference to NTP association node";
leaf associations-address {
type leafref {
path "/ntp:ntp/ntp:associations/ntp:address";
}
description description
"List of interfaces."; "Indicates the association address
leaf interface { which result in clock synchronization.";
type if:interface-ref; }
description leaf associations-local-mode {
"The interface name."; type leafref {
path "/ntp:ntp/ntp:associations/ntp:local-mode";
} }
description
container broadcast-server { "Indicates the association local-mode
presence which result in clock synchronization.";
"NTP broadcast-server is configured"; }
description leaf associations-isConfigured {
"Configuration of broadcast server."; type leafref {
leaf ttl { path "/ntp:ntp/ntp:associations/ntp:isConfigured";
type uint8;
description
"Specifies the time to live (TTL) of a
broadcast packet.";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
} }
description
"Indicates the association was configured or dynamic
which result in clock synchronization.";
}
}
container broadcast-client { /* Configuration data nodes */
presence container ntp {
"NTP broadcast-client is configured"; presence
description "NTP is enable";
"Configuration of broadcast-client."; description
} "Configuration parameters for NTP.";
list multicast-server { leaf port {
key "address"; type uint16 {
description range "123 | 1025..max";
"Configuration of multicast server."; }
leaf address { default "123";
type rt-types:ip-multicast-group-address; description
description "Specify the port used to send NTP packets.";
"The IP address to send NTP multicast packets."; }
}
leaf ttl { container refclock-master {
type uint8; presence
description "NTP master clock is enable";
"Specifies the time to live (TTL) of a description
multicast packet."; "Configures the device as NTP server.";
} leaf master-stratum {
container authentication{ type ntp-stratum;
description default "16";
"Authentication type."; description
uses authentication-type-param; "Stratum level from which NTP
} clients get their time synchronized.";
uses comman-attributes { }
description }
"Common attribute like port, version, min and max poll."; container authentication {
description
"Configuration of authentication.";
leaf auth-enabled {
type boolean;
default false;
description
"Controls whether NTP authentication is enabled
or disabled on this device.";
}
list trusted-keys {
key "key-id";
description
"List of keys trusted by NTP.";
leaf key-id {
type leafref {
path "/ntp:ntp/ntp:authentication/"
+ "ntp:authentication-keys/ntp:key-id";
} }
}
list multicast-client {
key "address";
description description
"Configuration of multicast-client."; "The key trusted by NTP.";
leaf address {
type rt-types:ip-multicast-group-address;
description
"The IP address of the multicast group to join.";
}
} }
list manycast-server { }
key "address"; list authentication-keys {
key "key-id";
uses authentication-key;
description
"List of authentication key.";
}
}
container access-rules {
description
"Configuration of access rules.";
list access-rule {
key "access-mode";
description
"List of access rules.";
leaf access-mode {
type access-modes;
description description
"Configuration of manycast server."; "NTP access mode.";
leaf address { }
type rt-types:ip-multicast-group-address; leaf acl {
description type leafref {
"The multicast group IP address to receive path "/acl:access-lists/acl:acl/acl:acl-name";
manycast client messages .";
} }
}
list manycast-client {
key "address";
description description
"Configuration of manycast-client."; "NTP ACL.";
leaf address { }
type rt-types:ip-multicast-group-address;
description
"The group IP address that the manycast client
broadcasts the request message to.";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
leaf ttl {
type uint8;
description
"Specifies the maximum time to live (TTL) for
the expanding ring search.";
}
leaf minclock {
type uint8;
description
"The minimum manycast survivors in this
association.";
}
leaf maxclock {
type uint8;
description
"The maximum manycast candidates in this
association.";
}
leaf beacon {
type uint8;
description
"The maximum interval between beacons in this
association.";
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
}
} }
} }
}
/* Operational state data */ container clock-state {
config "false";
description
"Operational state of the NTP.";
container ntp-statistics { container system-status {
config "false"; description
description "System status of NTP.";
"Total NTP packet statistic."; leaf clock-state {
uses statistics { type ntp-clock-status;
mandatory true;
description "Indicates the state of system clock.";
}
leaf clock-stratum {
type ntp-stratum;
mandatory true;
description
"Indicates the stratum of the reference clock.";
}
leaf clock-refid {
type union {
type inet:ipv4-address;
type binary {
length "4";
}
type string {
length "4";
}
}
mandatory true;
description
"IPv4 address or first 32 bits of the MD5 hash of
the IPv6 address or reference clock of the peer to
which clock is synchronized.";
}
uses association-ref {
description
"Reference to Association node";
}
leaf nominal-freq {
type decimal64 {
fraction-digits 4;
}
mandatory true;
description
"Indicates the nominal frequency of the
local clock, in Hz.";
}
leaf actual-freq {
type decimal64 {
fraction-digits 4;
}
mandatory true;
description
"Indicates the actual frequency of the
local clock, in Hz.";
}
leaf clock-precision {
type uint8;
mandatory true;
description
"Precision of the clock of this system
in Hz.(prec=2^(-n))";
}
leaf clock-offset {
type decimal64 {
fraction-digits 4;
}
description
"Offset of clock to synchronized peer,
in milliseconds.";
}
leaf root-delay {
type decimal64 {
fraction-digits 2;
}
description
"Total delay along path to root clock,
in milliseconds.";
}
leaf root-dispersion {
type decimal64 {
fraction-digits 2;
}
description
"Indicates the dispersion between the local clock
and the master reference clock, in milliseconds.";
}
leaf reference-time {
type yang:date-and-time;
description
"Indicates reference timestamp.";
}
leaf sync-state {
type ntp-sync-state;
mandatory true;
description
"Indicates the synchronization status of
the local clock.";
}
}
}
list unicast {
key "address type";
description
"list of unicast configuration.";
leaf address {
type inet:host;
description
"The address of this association.";
}
leaf type {
type unicast-configuration-type;
description
"Type for this NTP configuration";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
leaf prefer {
type boolean;
default "false";
description
"Whether this association is preferred.";
}
leaf burst {
type boolean;
default "false";
description
"Sends a series of packets instead of a single packet
within each synchronization interval to achieve faster
synchronization.";
}
leaf iburst {
type boolean;
default "false";
description
"Sends a series of packets instead of a single packet
within the initial synchronization interval to achieve
faster initial synchronization.";
}
leaf source {
type if:interface-ref;
description
"The interface whose ip address this association used
as source address.";
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
}
list associations {
key "address local-mode isConfigured";
config "false";
description
"list of NTP association.";
leaf address {
type inet:host;
description
"The address of this association.";
}
leaf local-mode {
type association-modes;
description
"Local mode for this NTP association.";
}
leaf isConfigured {
type boolean;
description
"Whether this association is configured or dynamically learnt.";
}
leaf stratum {
type ntp-stratum;
description
"Indicates the stratum of the reference clock.";
}
leaf refid {
type union {
type inet:ipv4-address;
type binary {
length "4";
}
type string {
length "4";
}
}
description
"Reference clock type or address for the peer.";
}
leaf authentication{
type leafref {
path "/ntp:ntp/ntp:authentication/"
+ "ntp:authentication-keys/ntp:key-id";
}
description
"Authentication Key used for this association.";
}
leaf prefer {
type boolean;
default "false";
description
"Whether this association is preferred.";
}
leaf peer-interface {
type if:interface-ref;
description
"The interface which is used for communication.";
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
leaf reach {
type uint8;
description
"Indicates the reachability of the configured
server or peer.";
}
leaf unreach {
type uint8;
description
"Indicates the unreachability of the configured
server or peer.";
}
leaf poll {
type uint8;
description
"Indicates the polling interval for current,
in seconds.";
}
leaf now {
type uint32;
description
"Indicates the time since the NTP packet was
not received or last synchronized, in seconds.";
}
leaf offset {
type decimal64 {
fraction-digits 4;
}
description
"Indicates the offset between the local clock
and the superior reference clock.";
}
leaf delay {
type decimal64 {
fraction-digits 2;
}
description
"Indicates the delay between the local clock
and the superior reference clock.";
}
leaf dispersion {
type decimal64 {
fraction-digits 2;
}
description
"Indicates the dispersion between the local
clock and the superior reference clock.";
}
leaf originate-time {
type yang:date-and-time;
description
"Indicates packet originate timestamp(T1).";
}
leaf receive-time {
type yang:date-and-time;
description
"Indicates packet receive timestamp(T2).";
}
leaf transmit-time {
type yang:date-and-time;
description
"Indicates packet transmit timestamp(T3).";
}
leaf input-time {
type yang:date-and-time;
description
"Indicates packet input timestamp(T4).";
}
container ntp-statistics {
description
"Per Peer packet send and receive statistic.";
uses statistics {
description
"NTP send and receive packet statistic.";
}
}
}
container interfaces {
description
"Configuration parameters for NTP interfaces.";
list interface {
key "name";
description
"List of interfaces.";
leaf name {
type if:interface-ref;
description
"The interface name.";
}
container broadcast-server {
presence
"NTP broadcast-server is configured";
description
"Configuration of broadcast server.";
leaf ttl {
type uint8;
description
"Specifies the time to live (TTL) of a
broadcast packet.";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
}
container broadcast-client {
presence
"NTP broadcast-client is configured";
description
"Configuration of broadcast-client.";
}
list multicast-server {
key "address";
description
"Configuration of multicast server.";
leaf address {
type rt-types:ip-multicast-group-address;
description description
"NTP send and receive packet statistic."; "The IP address to send NTP multicast packets.";
} }
leaf ttl {
type uint8;
description
"Specifies the time to live (TTL) of a
multicast packet.";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
}
list multicast-client {
key "address";
description
"Configuration of multicast-client.";
leaf address {
type rt-types:ip-multicast-group-address;
description
"The IP address of the multicast group to join.";
}
}
list manycast-server {
key "address";
description
"Configuration of manycast server.";
leaf address {
type rt-types:ip-multicast-group-address;
description
"The multicast group IP address to receive
manycast client messages .";
}
}
list manycast-client {
key "address";
description
"Configuration of manycast-client.";
leaf address {
type rt-types:ip-multicast-group-address;
description
"The group IP address that the manycast client
broadcasts the request message to.";
}
container authentication{
description
"Authentication type.";
uses authentication-type-param;
}
leaf ttl {
type uint8;
description
"Specifies the maximum time to live (TTL) for
the expanding ring search.";
}
leaf minclock {
type uint8;
description
"The minimum manycast survivors in this
association.";
}
leaf maxclock {
type uint8;
description
"The maximum manycast candidates in this
association.";
}
leaf beacon {
type uint8;
description
"The maximum interval between beacons in this
association.";
}
uses comman-attributes {
description
"Common attribute like port, version, min and max poll.";
}
}
} }
} }
<CODE ENDS> /* Operational state data */
6. IANA Considerations container ntp-statistics {
config "false";
description
"Total NTP packet statistic.";
uses statistics {
description
"NTP send and receive packet statistic.";
}
}
}
}
<CODE ENDS>
6. Usage Example
6.1. Unicast association
Below is the example on how to configure a preferred unicast server
present at 1.1.1.1 running at port 1025 with authentication-key 10
and version 4
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<unicast>
<address>1.1.1.1</address>
<type>server</type>
<prefer>true</prefer>
<version>4</version>
<port>1025</port>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
</unicast>
</ntp>
</config>
</edit-config>
Below is the example on how to get unicast configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:unicast>
</sys:unicast>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<unicast>
<address>1.1.1.1</address>
<type>server</type>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
<prefer>true</prefer>
<burst>false</burst>
<iburst>true</iburst>
<source/>
<minpoll>6</minpoll>
<maxpoll>10</maxpoll>
<port>1025</port>
<version>4</version>
<stratum>9</stratum>
<refid>20.1.1.1</refid>
<reach>255</reach>
<unreach>0</unreach>
<poll>128</poll>
<now>10</now>
<offset>0.025</offset>
<delay>0.5</delay>
<dispersion>0.6</dispersion>
<originate-time>10-10-2017 07:33:55.253 Z+05:30</originate-time>
<receive-time>10-10-2017 07:33:55.258 Z+05:30</receive-time>
<transmit-time>10-10-2017 07:33:55.300 Z+05:30</transmit-time>
<input-time>10-10-2017 07:33:55.305 Z+05:30</input-time>
<ntp-statistics>
<packet-sent>20</packet-sent>
<packet-sent-fail>0</packet-sent-fail>
<packet-received>20</packet-received>
<packet-dropped>0</packet-dropped>
</ntp-statistics>
</unicast>
</ntp>
</data>
6.2. Refclock master
Below is the example on how to configure reference clock with stratum
8
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<refclock-master>
<master-stratum>8</master-stratum>
</refclock-master>
</ntp>
</config>
</edit-config>
Below is the example on how to get reference clock configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:refclock-master>
</sys:refclock-master>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<refclock-master>
<master-stratum>8</master-stratum>
</refclock-master>
</ntp>
</data>
6.3. Authentication configuration
Below is the example on how to enable authentication and configure
authentication key 10 with mode as md5 and password as abcd
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<authentication>
<auth-enabled>true</auth-enabled>
<authentication-keys>
<key-id>10</key-id>
<algorithm>md5</algorithm>
<password>abcd</password>
</authentication-keys>
</authentication>
</ntp>
</config>
</edit-config>
Below is the example on how to get authentication related
configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:authentication>
</sys:authentication>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<authentication>
<auth-enabled>false</auth-enabled>
<trusted-keys/>
<authentication-keys>
<key-id>10</key-id>
<algorithm>md5</algorithm>
<password>abcd</password>
</authentication-keys>
</authentication>
</ntp>
</data>
6.4. Access configuration
Below is the example on how to configure acess type peer associated
with acl 2000
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<access-rules>
<access-rule>
<access-mode>peer</access-mode>
<acl>2000</acl>
</access-rule>
</access-rules>
</ntp>
</config>
</edit-config>
Below is the example on how to get access related configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:access-rules>
</sys:access-rules>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<access-rules>
<access-rule>
<access-mode>peer</access-mode>
<acl>2000</acl>
</access-rule>
</access-rules>
</ntp>
</data>
6.5. Multicast configuration
Below is the example on how to configure multicast-server with
address as 224.1.1.1, port as 1025 and authentication keyid as 10
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<multicast-server>
<address>224.1.1.1</address>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
<port>1025</port>
</multicast-server>
</interface>
</interfaces>
</ntp>
</config>
</edit-config>
Below is the example on how to get multicast-server related
configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:interfaces>
<sys:interface>
<sys:multicast-server>
</sys:multicast-server>
</sys:interface>
</sys:interfaces>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<multicast-server>
<address>224.1.1.1</address>
<ttl>224.1.1.1</ttl>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
<minpoll>6</minpoll>
<maxpoll>10</maxpoll>
<port>1025</port>
<version>3</version>
</multicast-server>
</interface>
</interfaces>
</ntp>
</data>
Below is the example on how to configure multicast-client with
address as 224.1.1.1
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<multicast-client>
<address>224.1.1.1</address>
</multicast-client>
</interface>
</interfaces>
</ntp>
</config>
</edit-config>
Below is the example on how to get multicast-client related
configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:interfaces>
<sys:interface>
<sys:multicast-client>
</sys:multicast-client>
</sys:interface>
</sys:interfaces>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<multicast-client>
<address>224.1.1.1</address>
</multicast-client>
</interface>
</interfaces>
</ntp>
</data>
6.6. Manycast configuration
Below is the example on how to configure manycast-client with address
as 224.1.1.1, port as 1025 and authentication keyid as 10
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<manycast-client>
<address>224.1.1.1</address>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
<port>1025</port>
</manycast-client>
</interface>
</interfaces>
</ntp>
</config>
</edit-config>
Below is the example on how to get manycast-client related
configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:interfaces>
<sys:interface>
<sys:manycast-client>
</sys:manycast-client>
</sys:interface>
</sys:interfaces>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<manycast-client>
<address>224.1.1.1</address>
<authentication>
<symmetric-key>
<key-id>10</key-id>
</symmetric-key>
</authentication>
<ttl>255</ttl>
<minclock>3</minclock>
<maxclock>10</maxclock>
<beacon>6</beacon>
<minpoll>6</minpoll>
<maxpoll>10</maxpoll>
<port>1025</port>
</manycast-client>
</interface>
</interfaces>
</ntp>
</data>
Below is the example on how to configure manycast-server with address
as 224.1.1.1
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<manycast-server>
<address>224.1.1.1</address>
</manycast-server>
</interface>
</interfaces>
</ntp>
</config>
</edit-config>
Below is the example on how to get manycast-server related
configuration
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:interfaces>
<sys:interface>
<sys:manycast-server>
</sys:manycast-server>
</sys:interface>
</sys:interfaces>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<interfaces>
<interface>
<name>Ethernet3/0/0</name>
<manycast-server>
<address>224.1.1.1</address>
</manycast-server>
</interface>
</interfaces>
</ntp>
</data>
6.7. Clock state
Below is the example on how to get clock current state
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:clock-state>
</sys:clock-state>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<clock-state>
<system-status>
<clock-state>synchronized</clock-state>
<clock-stratum>7</clock-stratum>
<clock-refid>1.1.1.1</clock-refid>
<associations-address>1.1.1.1</associations-address>
<associations-local-mode>client</associations-local-mode>
<associations-isConfigured>yes</associations-isConfigured>
<nominal-freq>100.0</nominal-freq>
<actual-freq>100.0</actual-freq>
<clock-precision>18</clock-precision>
<clock-offset>0.025</clock-offset>
<root-delay>0.5</root-delay>
<root-dispersion>0.8</root-dispersion>
<reference-time>10-10-2017 07:33:55.258 Z+05:30</reference-time>
<sync-state>clock-synchronized</sync-state>
</system-status>
</clock-state>
</ntp>
</data>
6.8. Get all association
Below is the example on how to get all association present
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:associations>
</sys:associations>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<associations>
<address>1.1.1.1</address>
<stratum>9</stratum>
<refid>20.1.1.1</refid>
<local-mode>client</local-mode>
<isConfigured>true</isConfigured>
<authentication-key>10</authentication-key>
<prefer>true</prefer>
<peer-interface>Ethernet3/0/0</peer-interface>
<minpoll>6</minpoll>
<maxpoll>10</maxpoll>
<port>1025</port>
<version>4</version>
<reach>255</reach>
<unreach>0</unreach>
<poll>128</poll>
<now>10</now>
<offset>0.025</offset>
<delay>0.5</delay>
<dispersion>0.6</dispersion>
<originate-time>10-10-2017 07:33:55.253 Z+05:30</originate-time>
<receive-time>10-10-2017 07:33:55.258 Z+05:30</receive-time>
<transmit-time>10-10-2017 07:33:55.300 Z+05:30</transmit-time>
<input-time>10-10-2017 07:33:55.305 Z+05:30</input-time>
<ntp-statistics>
<packet-sent>20</packet-sent>
<packet-sent-fail>0</packet-sent-fail>
<packet-received>20</packet-received>
<packet-dropped>0</packet-dropped>
</ntp-statistics>
</associations>
</ntp>
</data>
6.9. Global statistic
Below is the example on how to get clock current state
<get>
<filter type="subtree">
<sys:ntp xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-ntp">
<sys:ntp-statistics>
</sys:ntp-statistics>
</sys:ntp>
</filter>
</get>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ntp xmlns="urn:ietf:params:xml:ns:yang:ietf-ntp">
<ntp-statistics>
<packet-sent>30</packet-sent>
<packet-sent-fail>5</packet-sent-fail>
<packet-received>20</packet-received>
<packet-dropped>2</packet-dropped>
</ntp-statistics>
</ntp>
</data>
7. IANA Considerations
This document registers a URI in the "IETF XML Registry" [RFC3688]. This document registers a URI in the "IETF XML Registry" [RFC3688].
Following the format in RFC 3688, the following registration has been Following the format in RFC 3688, the following registration has been
made. made.
URI: urn:ietf:params:xml:ns:yang:ietf-ntp URI: urn:ietf:params:xml:ns:yang:ietf-ntp
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers a YANG module in the "YANG Module Names" This document registers a YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
Name: ietf-ntp Name: ietf-ntp
Namespace: urn:ietf:params:xml:ns:yang:ietf-ntp Namespace: urn:ietf:params:xml:ns:yang:ietf-ntp
skipping to change at page 26, line 19 skipping to change at page 41, line 5
registry [RFC6020]. registry [RFC6020].
Name: ietf-ntp Name: ietf-ntp
Namespace: urn:ietf:params:xml:ns:yang:ietf-ntp Namespace: urn:ietf:params:xml:ns:yang:ietf-ntp
Prefix: ntp Prefix: ntp
Reference: RFC XXXX Reference: RFC XXXX
7. Security Considerations 8. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides the means to restrict access for particular [RFC6536] provides the means to restrict access for particular
NETCONF users to a pre-configured subset of all available NETCONF NETCONF users to a pre-configured subset of all available NETCONF
protocol operations and content. protocol operations and content.
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., <edit-config>) in some network environments. Write operations (e.g., <edit-config>)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. effect on network operations.
8. Acknowledgments 9. Acknowledgments
The authors would like to express their thanks to Sladjana Zoric, The authors would like to express their thanks to Sladjana Zoric,
Danny Mayer, Harlan Stenn, Ulrich Windl and Miroslav Lichvar for Danny Mayer, Harlan Stenn, Ulrich Windl and Miroslav Lichvar for
their review and suggestions. their review and suggestions.
9. References 10. References
9.1. Normative References 10.1. Normative References
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-02 (work in progress),
October 2017.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<http://www.rfc-editor.org/info/rfc5905>. <https://www.rfc-editor.org/info/rfc5905>.
[RFC5907] Gerstung, H., Elliott, C., and B. Haberman, Ed., [RFC5907] Gerstung, H., Elliott, C., and B. Haberman, Ed.,
"Definitions of Managed Objects for Network Time Protocol "Definitions of Managed Objects for Network Time Protocol
Version 4 (NTPv4)", RFC 5907, DOI 10.17487/RFC5907, June Version 4 (NTPv4)", RFC 5907, DOI 10.17487/RFC5907, June
2010, <http://www.rfc-editor.org/info/rfc5907>. 2010, <https://www.rfc-editor.org/info/rfc5907>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
9.2. Informative References [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
10.2. Informative References
[I-D.ietf-netmod-revised-datastores] [I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-03 Architecture", draft-ietf-netmod-revised-datastores-05
(work in progress), July 2017. (work in progress), October 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for
System Management", RFC 7317, DOI 10.17487/RFC7317, August System Management", RFC 7317, DOI 10.17487/RFC7317, August
2014, <http://www.rfc-editor.org/info/rfc7317>. 2014, <https://www.rfc-editor.org/info/rfc7317>.
Authors' Addresses Authors' Addresses
Nan Wu Nan Wu
Huawei Huawei
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: eric.wu@huawei.com Email: eric.wu@huawei.com
Anil Kumar S N Anil Kumar S N
RtBrick Inc. RtBrick Inc.
 End of changes. 116 change blocks. 
947 lines changed or deleted 1607 lines changed or added

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