draft-ietf-ntp-yang-data-model-08.txt   draft-ietf-ntp-yang-data-model-09.txt 
NTP Working Group N. Wu NTP Working Group N. Wu
Internet-Draft D. Dhody Internet-Draft D. Dhody, Ed.
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: July 25, 2020 A. Sinha Expires: January 14, 2021 A. Sinha, Ed.
A. Kumar S N A. Kumar S N
RtBrick Inc. RtBrick Inc.
Y. Zhao Y. Zhao
Ericsson Ericsson
January 22, 2020 July 13, 2020
A YANG Data Model for NTP A YANG Data Model for NTP
draft-ietf-ntp-yang-data-model-08 draft-ietf-ntp-yang-data-model-09
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) implementations. The data model includes configuration data (NTP) implementations. The data model includes configuration data
and state data. and 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",
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 July 25, 2020. This Internet-Draft will expire on January 14, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://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
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
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
1.4. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.4. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
1.5. Refrences in the Model . . . . . . . . . . . . . . . . . 4 1.5. Refrences in the Model . . . . . . . . . . . . . . . . . 4
2. NTP data model . . . . . . . . . . . . . . . . . . . . . . . 4 2. NTP data model . . . . . . . . . . . . . . . . . . . . . . . 4
3. Relationship with NTPv4-MIB . . . . . . . . . . . . . . . . . 8 3. Relationship with NTPv4-MIB . . . . . . . . . . . . . . . . . 9
4. Relationship with RFC 7317 . . . . . . . . . . . . . . . . . 9 4. Relationship with RFC 7317 . . . . . . . . . . . . . . . . . 9
5. Access Rules . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Access Rules . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Key Management . . . . . . . . . . . . . . . . . . . . . . . 10 6. Key Management . . . . . . . . . . . . . . . . . . . . . . . 10
7. NTP YANG Module . . . . . . . . . . . . . . . . . . . . . . . 10 7. NTP YANG Module . . . . . . . . . . . . . . . . . . . . . . . 10
8. Usage Example . . . . . . . . . . . . . . . . . . . . . . . . 35 8. Usage Example . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Unicast association . . . . . . . . . . . . . . . . . . . 35 8.1. Unicast association . . . . . . . . . . . . . . . . . . . 35
8.2. Refclock master . . . . . . . . . . . . . . . . . . . . . 37 8.2. Refclock master . . . . . . . . . . . . . . . . . . . . . 37
8.3. Authentication configuration . . . . . . . . . . . . . . 38 8.3. Authentication configuration . . . . . . . . . . . . . . 38
8.4. Access configuration . . . . . . . . . . . . . . . . . . 40 8.4. Access configuration . . . . . . . . . . . . . . . . . . 40
8.5. Multicast configuration . . . . . . . . . . . . . . . . . 40 8.5. Multicast configuration . . . . . . . . . . . . . . . . . 40
skipping to change at page 10, line 46 skipping to change at page 10, line 46
cryptographic keys indexed by a key identifier included in the NTP cryptographic keys indexed by a key identifier included in the NTP
message. This key-id is 32-bits unsigned integer that MUST be message. This key-id is 32-bits unsigned integer that MUST be
configured on the NTP peers before the authentication could be used. configured on the NTP peers before the authentication could be used.
For this reason, this YANG modules allow such configuration via For this reason, this YANG modules allow such configuration via
/ntp/authentication/authentication-keys/. Further at the time of /ntp/authentication/authentication-keys/. Further at the time of
configuration of NTP association (for example unicast-server), the configuration of NTP association (for example unicast-server), the
key-id is specefied. key-id is specefied.
7. NTP YANG Module 7. NTP YANG Module
<CODE BEGINS> file "ietf-ntp@2020-01-22.yang" <CODE BEGINS> file "ietf-ntp@2020-07-13.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 11, line 51 skipping to change at page 11, line 51
reference reference
"RFC 8341: Network Configuration Protocol (NETCONF) Access "RFC 8341: Network Configuration Protocol (NETCONF) Access
Control Model"; Control Model";
} }
organization organization
"IETF NTP (Network Time Protocol) Working Group"; "IETF NTP (Network Time Protocol) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ntp/> "WG Web: <http://tools.ietf.org/wg/ntp/>
WG List: <mailto: ntpwg@lists.ntp.org WG List: <mailto: ntpwg@lists.ntp.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 Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Ankit Kumar Sinha Editor: Ankit Kumar Sinha
<mailto:ankit.ietf@gmail.com>"; <mailto:ankit.ietf@gmail.com>";
description description
"This document defines a YANG data model for Network Time Protocol "This document defines a YANG data model for Network Time Protocol
(NTP) implementations. The data model includes configuration data (NTP) implementations. The data model includes configuration data
and state data. and state data.
Copyright (c) 2020 IETF Trust and the persons identified Copyright (c) 2020 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant to, with or without modification, is permitted pursuant to,
and subject to the license terms contained in, the and subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents IETF Trust's Legal Provisions 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; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.
revision 2020-01-22 { The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";
revision 2020-07-13 {
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 53, line 39 skipping to change at page 53, line 39
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
Dhruv Dhody Dhruv Dhody (editor)
Huawei Huawei
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Kanataka 560066 Bangalore, Kanataka 560066
India India
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Ankit kumar Sinha Ankit kumar Sinha (editor)
RtBrick Inc. RtBrick Inc.
Bangalore, Kanataka Bangalore, Kanataka
India India
Email: ankit.ietf@gmail.com Email: ankit.ietf@gmail.com
Anil Kumar S N Anil Kumar S N
RtBrick Inc. RtBrick Inc.
Bangalore, Kanataka Bangalore, Kanataka
India India
 End of changes. 12 change blocks. 
17 lines changed or deleted 17 lines changed or added

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