[Ntp] Antw: [EXT] Re: I‑D Action: draft‑ietf‑ntp‑mode‑6‑cmds‑11.txt

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Wed, 16 February 2022 11:01 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 1EC6B3A101B for <ntp@ietfa.amsl.com>; Wed, 16 Feb 2022 03:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qXNTABUO-L6b for <ntp@ietfa.amsl.com>; Wed, 16 Feb 2022 03:01:42 -0800 (PST)
Received: from mx1.uni-regensburg.de (mx1.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf7]) (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 E6A0F3A1016 for <ntp@ietf.org>; Wed, 16 Feb 2022 03:01:41 -0800 (PST)
Received: from mx1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0607A600005A for <ntp@ietf.org>; Wed, 16 Feb 2022 12:01:36 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx1.uni-regensburg.de (Postfix) with ESMTP id D24476000057 for <ntp@ietf.org>; Wed, 16 Feb 2022 12:01:35 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 16 Feb 2022 12:01:36 +0100
Message-Id: <620CD98E020000A100047D42@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Wed, 16 Feb 2022 12:01:34 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, stenn@nwtime.org
References: <164494786706.31921.2790066397538591891@ietfa.amsl.com> <4f29532c-281c-3002-c968-d121ba7fa03b@nwtime.org>
In-Reply-To: <4f29532c-281c-3002-c968-d121ba7fa03b@nwtime.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/jQQ3AtEanxZxtKhUNlucsRWJyMU>
Subject: [Ntp] Antw: [EXT] Re: 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 11:01:47 -0000

>>> Harlan Stenn <stenn@nwtime.org> schrieb am 16.02.2022 um 04:07 in
Nachricht
<4f29532c-281c-3002-c968-d121ba7fa03b@nwtime.org>:
> 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.

Maybe it's like alcohol: Government does not want you to drink, but people
like to do so from time to time ;-)

> 
> 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 mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp