Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-11.txt
Harlan Stenn <stenn@nwtime.org> Wed, 16 February 2022 03:07 UTC
Return-Path: <stenn@nwtime.org>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C95343A0491 for <ntp@ietfa.amsl.com>; Tue, 15 Feb 2022 19:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.614
X-Spam-Level:
X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUMQZzao1lhF for <ntp@ietfa.amsl.com>; Tue, 15 Feb 2022 19:07:05 -0800 (PST)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4CAA3A131C for <ntp@ietf.org>; Tue, 15 Feb 2022 19:07:03 -0800 (PST)
Received: from [10.208.75.149] (071-084-168-128.res.spectrum.com [71.84.168.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4Jz2tZ74ZKzMNLD; Wed, 16 Feb 2022 03:07:02 +0000 (UTC)
Message-ID: <4f29532c-281c-3002-c968-d121ba7fa03b@nwtime.org>
Date: Tue, 15 Feb 2022 19:07:02 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0
Content-Language: en-US
To: ntp@ietf.org
References: <164494786706.31921.2790066397538591891@ietfa.amsl.com>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <164494786706.31921.2790066397538591891@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/SZBcGA4PGAzEBBbV_hA7gLYIkD8>
Subject: Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-11.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 03:07:13 -0000
Brian, On 2/15/2022 9:57 AM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Network Time Protocols WG of the IETF. > > Title : Control Messages Protocol for Use with Network Time Protocol Version 4 > Author : Brian Haberman > Filename : draft-ietf-ntp-mode-6-cmds-11.txt > Pages : 22 > Date : 2022-02-15 > > Abstract: > This document describes the structure of the control messages that > were historically used with the Network Time Protocol before the > advent of more modern control and management approaches. These > control messages have been used to monitor and control the Network > Time Protocol application running on any IP network attached > computer. The information in this document was originally described > in Appendix B of RFC 1305. The goal of this document is to provide > an updated description of the control messages described in RFC 1305 > in order to conform with the updated Network Time Protocol > specification documented in RFC 5905. Yup... > The publication of this document is not meant to encourage the > development and deployment of these control messages. This document > is only providing a current reference for these control messages > given the current status of RFC 1305. I'm curious why you write the preceding paragraph. Mode 6 is still the preferred way to handle monitoring and control of an NTP daemon. Mode 6 was designed to be a vendor-neutral way to accomplish this. The only implementation I know of for NTP+SNMP is ntpsnmpd, in the Reference Implementation, and that daemon translates SNMP in to mode 6 directives. The NTP Yang Data Model is still a draft document, and from what I have seen there is no reference implementation of it. If and when the NTP Project provides this capability, it will very likely be done the same way - using mode 6 messages to the NTP daemon. > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-ntp-mode-6-cmds/ > > There is also an htmlized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-ntp-mode-6-cmds-11 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-mode-6-cmds-11 > > > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts > > > _______________________________________________ > ntp mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp > -- Harlan Stenn <stenn@nwtime.org> http://networktimefoundation.org - be a member!
- [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-11.t… internet-drafts
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Harlan Stenn
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Miroslav Lichvar
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Harlan Stenn
- [Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑ntp‑… Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑… Miroslav Lichvar
- [Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑ntp‑… Ulrich Windl
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Miroslav Lichvar
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Hal Murray
- Re: [Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑… Karen O'Donoghue
- Re: [Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑… Harlan Stenn
- Re: [Ntp] I-D Action: draft-ietf-ntp-mode-6-cmds-… Danny Mayer