< draft-ietf-ntp-yang-data-model-16.txt   draft-ietf-ntp-yang-data-model-17.txt >
NTP Working Group N. Wu NTP Working Group N. Wu
Internet-Draft D. Dhody, Ed. Internet-Draft D. Dhody, Ed.
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: 14 August 2022 A. Sinha, Ed. Expires: 21 September 2022 A. Sinha, Ed.
A. Kumar S N A. Kumar S N
RtBrick Inc. RtBrick Inc.
Y. Zhao Y. Zhao
Ericsson Ericsson
10 February 2022 20 March 2022
A YANG Data Model for NTP A YANG Data Model for NTP
draft-ietf-ntp-yang-data-model-16 draft-ietf-ntp-yang-data-model-17
Abstract Abstract
This document defines a YANG data model for Network Time Protocol This document defines a YANG data model for Network Time Protocol
(NTP) version 4 implementations. It can also be used to configure (NTP) version 4 implementations. It can also be used to configure
version 3. The data model includes configuration data and state version 3. The data model includes configuration data and state
data. data.
Requirements Language Requirements Language
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 https://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 14 August 2022. This Internet-Draft will expire on 21 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 52 skipping to change at page 2, line 52
9.8. Get all association . . . . . . . . . . . . . . . . . . . 53 9.8. Get all association . . . . . . . . . . . . . . . . . . . 53
9.9. Global statistic . . . . . . . . . . . . . . . . . . . . 55 9.9. Global statistic . . . . . . . . . . . . . . . . . . . . 55
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
10.1. IETF XML Registry . . . . . . . . . . . . . . . . . . . 55 10.1. IETF XML Registry . . . . . . . . . . . . . . . . . . . 55
10.2. YANG Module Names . . . . . . . . . . . . . . . . . . . 55 10.2. YANG Module Names . . . . . . . . . . . . . . . . . . . 55
11. Security Considerations . . . . . . . . . . . . . . . . . . . 56 11. Security Considerations . . . . . . . . . . . . . . . . . . . 56
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 58 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 58
13.1. Normative References . . . . . . . . . . . . . . . . . . 58 13.1. Normative References . . . . . . . . . . . . . . . . . . 58
13.2. Informative References . . . . . . . . . . . . . . . . . 59 13.2. Informative References . . . . . . . . . . . . . . . . . 59
Appendix A. Full YANG Tree . . . . . . . . . . . . . . . . . . . 61 Appendix A. Full YANG Tree . . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for Network Time This document defines a YANG [RFC7950] data model for Network Time
Protocol [RFC5905] implementations. Note that the model could also Protocol [RFC5905] implementations. Note that the model could also
be used to configure NTPv3 [RFC1305] (see Section 7). be used to configure NTPv3 [RFC1305] (see Section 7).
The data model covers configuration of system parameters of NTP, such The data model covers configuration of system parameters of NTP, such
as access rules, authentication and VPN Routing and Forwarding (VRF) as access rules, authentication and VPN Routing and Forwarding (VRF)
skipping to change at page 5, line 15 skipping to change at page 5, line 15
| Title | Reference | | Title | Reference |
+=======================================+===========+ +=======================================+===========+
| Network Time Protocol Version 4: | [RFC5905] | | Network Time Protocol Version 4: | [RFC5905] |
| Protocol and Algorithms Specification | | | Protocol and Algorithms Specification | |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| Common YANG Data Types | [RFC6991] | | Common YANG Data Types | [RFC6991] |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| A YANG Data Model for System | [RFC7317] | | A YANG Data Model for System | [RFC7317] |
| Management | | | Management | |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| YANG Data Model for Key Chains | [RFC8177] |
+---------------------------------------+-----------+
| Common YANG Data Types for the | [RFC8294] | | Common YANG Data Types for the | [RFC8294] |
| Routing Area | | | Routing Area | |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| Network Configuration Access Control | [RFC8341] | | Network Configuration Access Control | [RFC8341] |
| Model | | | Model | |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| A YANG Data Model for Interface | [RFC8343] | | A YANG Data Model for Interface | [RFC8343] |
| Management | | | Management | |
+---------------------------------------+-----------+ +---------------------------------------+-----------+
| YANG Data Model for Network Access | [RFC8519] | | YANG Data Model for Network Access | [RFC8519] |
skipping to change at page 11, line 7 skipping to change at page 11, line 7
7. NTP Version 7. NTP Version
This YANG model allow a version to be configured for the NTP This YANG model allow a version to be configured for the NTP
association i.e. an operator can control the use of NTPv3 [RFC1305] association i.e. an operator can control the use of NTPv3 [RFC1305]
or NTPv4 [RFC5905] for each association it forms. This allows or NTPv4 [RFC5905] for each association it forms. This allows
backward compatibility with a legacy system. Note that the version 3 backward compatibility with a legacy system. Note that the version 3
of NTP [RFC1305] is obsoleted by NTPv4 [RFC5905]. of NTP [RFC1305] is obsoleted by NTPv4 [RFC5905].
8. NTP YANG Module 8. NTP YANG Module
<CODE BEGINS> file "ietf-ntp@2022-02-10.yang" <CODE BEGINS> file "ietf-ntp@2022-03-21.yang"
module ietf-ntp { module ietf-ntp {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ntp"; namespace "urn:ietf:params:xml:ns:yang:ietf-ntp";
prefix ntp; prefix ntp;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
skipping to change at page 12, line 36 skipping to change at page 12, line 36
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Revised BSD License to the license terms contained in, the Revised BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2022-02-10 { revision 2022-03-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for NTP."; "RFC XXXX: A YANG Data Model for NTP.";
} }
/* Note: The RFC Editor will replace XXXX with the number assigned /* Note: The RFC Editor will replace XXXX with the number assigned
to this document once it becomes an RFC.*/ to this document once it becomes an RFC.*/
/* Typedef Definitions */ /* Typedef Definitions */
skipping to change at page 21, line 21 skipping to change at page 21, line 21
"HMAC-SHA-1 authentication algorithm."; "HMAC-SHA-1 authentication algorithm.";
reference reference
"FIPS 180-4: Secure Hash Standard (SHS)"; "FIPS 180-4: Secure Hash Standard (SHS)";
} }
identity hmac-sha1-12 { identity hmac-sha1-12 {
if-feature "deprecated"; if-feature "deprecated";
base crypto-algorithm; base crypto-algorithm;
description description
"The HMAC-SHA1-12 algorithm."; "The HMAC-SHA1-12 algorithm.";
reference
"FIPS 180-4: Secure Hash Standard (SHS)";
} }
identity hmac-sha-256 { identity hmac-sha-256 {
description description
"HMAC-SHA-256 authentication algorithm."; "HMAC-SHA-256 authentication algorithm.";
reference reference
"FIPS 180-4: Secure Hash Standard (SHS)"; "FIPS 180-4: Secure Hash Standard (SHS)";
} }
identity hmac-sha-384 { identity hmac-sha-384 {
skipping to change at page 25, line 26 skipping to change at page 25, line 24
default "10"; default "10";
description description
"The maximum poll interval used in this association."; "The maximum poll interval used in this association.";
reference reference
"RFC 5905: Network Time Protocol Version 4: Protocol and "RFC 5905: Network Time Protocol Version 4: Protocol and
Algorithms Specification, Section 7.2"; Algorithms Specification, Section 7.2";
} }
leaf port { leaf port {
if-feature "ntp-port"; if-feature "ntp-port";
type inet:port-number { type inet:port-number {
range "123 | 1025..max"; range "123 | 1024..max";
} }
default "123"; default "123";
description description
"Specify the port used to send NTP packets."; "Specify the port used to send NTP packets.";
reference reference
"RFC 5905: Network Time Protocol Version 4: Protocol and "RFC 5905: Network Time Protocol Version 4: Protocol and
Algorithms Specification, Section 7.2"; Algorithms Specification, Section 7.2";
} }
leaf version { leaf version {
type ntp-version; type ntp-version;
skipping to change at page 26, line 43 skipping to change at page 26, line 40
"Applicable when the system /sys/ntp/ is not used."; "Applicable when the system /sys/ntp/ is not used.";
} }
presence "NTP is enabled and system should attempt to presence "NTP is enabled and system should attempt to
synchronize the system clock with an NTP server synchronize the system clock with an NTP server
from the 'ntp/associations' list."; from the 'ntp/associations' list.";
description description
"Configuration parameters for NTP."; "Configuration parameters for NTP.";
leaf port { leaf port {
if-feature "ntp-port"; if-feature "ntp-port";
type inet:port-number { type inet:port-number {
range "123 | 1025..max"; range "123 | 1024..max";
} }
default "123"; default "123";
description description
"Specify the port used to send and receive NTP packets."; "Specify the port used to send and receive NTP packets.";
reference reference
"RFC 5905: Network Time Protocol Version 4: Protocol and "RFC 5905: Network Time Protocol Version 4: Protocol and
Algorithms Specification, Section 7.2"; Algorithms Specification, Section 7.2";
} }
container refclock-master { container refclock-master {
presence "NTP master clock is enabled."; presence "NTP master clock is enabled.";
skipping to change at page 59, line 13 skipping to change at page 59, line 13
2014, <https://www.rfc-editor.org/info/rfc7317>. 2014, <https://www.rfc-editor.org/info/rfc7317>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
Zhang, "YANG Data Model for Key Chains", RFC 8177,
DOI 10.17487/RFC8177, June 2017,
<https://www.rfc-editor.org/info/rfc8177>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294, "Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017, DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>. <https://www.rfc-editor.org/info/rfc8294>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
 End of changes. 12 change blocks. 
18 lines changed or deleted 9 lines changed or added

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