[Ntp] Antw: [EXT] Opsdir last call review of draft-ietf-ntp-mode-6-cmds-08

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 09 June 2020 06:32 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 F29183A096E; Mon, 8 Jun 2020 23:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 knbS7Q3gRSEq; Mon, 8 Jun 2020 23:32:42 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (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 494813A09FC; Mon, 8 Jun 2020 23:32:26 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 07AC76000056; Tue, 9 Jun 2020 08:32:24 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 7DF416000050; Tue, 9 Jun 2020 08:32:15 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 09 Jun 2020 08:32:15 +0200
Message-Id: <5EDF2CEC020000A100039793@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.1
Date: Tue, 09 Jun 2020 08:32:12 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: linda.dunbar@futurewei.com, ops-dir@ietf.org
Cc: draft-ietf-ntp-mode-6-cmds.all@ietf.org, last-call@ietf.org, "ntp@ietf.org" <ntp@ietf.org>
References: <14380_1591656804_5EDEC163_14380_220_1_159165674337.26758.11645384633524120985@ietfa.amsl.com>
In-Reply-To: <14380_1591656804_5EDEC163_14380_220_1_159165674337.26758.11645384633524120985@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/8YFj5B_NAkwpDwWqa7Z_vgV0iYM>
Subject: [Ntp] Antw: [EXT] Opsdir last call review of draft-ietf-ntp-mode-6-cmds-08
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Tue, 09 Jun 2020 06:32:46 -0000

>>> Linda Dunbar via Datatracker <noreply@ietf.org> schrieb am 09.06.2020 um 00:52
in Nachricht
<14380_1591656804_5EDEC163_14380_220_1_159165674337.26758.11645384633524120985@i
tfa.amsl.com>:
> Reviewer: Linda Dunbar
> Review result: Has Nits
> 
> I have reviewed this document as part of the Ops area directorate's ongoing
> effort to review all IETF documents being processed by the IESG.  These
> comments were written primarily for the benefit of the Ops area directors.
> Document editors and WG chairs should treat these comments just like any 
> other
> last call comments.
> 
> This document describes the structure of the control messages that were
> historically used with the Network Time Protocol. Being historical document, 
> I
> would expect the document to give a description on what the Control Message 
> are
> for, who is the sender, and who is the receiver, is the Control Message
> broadcast to every node in the network? or only between some nodes? The
> document describes the bits in detail for Mode =6 and Mode =7. The RFC1305 
> has
> a lot of information, but can't pinpoint the Control message's purpose. Are 
> the
> control messages for distributing time from Stratum 0 to Stratum 1?  or 
> between
> network nodes?

Hi!

I think these question (if not answered in the document) are very valid ones.
In my view of things the control protocol (both mode 6 and 7) was designed and used to "control" (surprise!) a running NTP daemon, where "controlling" means "see what it is doing" and "change (some) settings". You can also get the current time, but not for adjusting purposes, but for monitoring purposes (more or less at a one-second resolution).
Servers never echange control messages; only admin type of users (processes) initiate requests, and servers answer them (hopefully).

That was my little view of things.

Regards,
Ulrich

> 
> Thank you.
> Linda Dunbar
> 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp