Re: [Ntp] Martin Duke's No Objection on draft-ietf-ntp-mode-6-cmds-09: (with COMMENT)

Hal Murray <hmurray@megapathdsl.net> Sat, 29 August 2020 09:31 UTC

Return-Path: <hmurray@megapathdsl.net>
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 953443A1277 for <ntp@ietfa.amsl.com>; Sat, 29 Aug 2020 02:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.137
X-Spam-Level: *
X-Spam-Status: No, score=1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HDRS_LCASE=0.1, HELO_DYNAMIC_IPADDR=1.951, PDS_RDNS_DYNAMIC_FP=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LcZSxUAhTXUt for <ntp@ietfa.amsl.com>; Sat, 29 Aug 2020 02:31:17 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id B92663A1276 for <ntp@ietf.org>; Sat, 29 Aug 2020 02:31:15 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 1805440605C; Sat, 29 Aug 2020 02:31:12 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Brian Haberman <brian@innovationslab.net>
cc: Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
From: Hal Murray <hmurray@megapathdsl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 29 Aug 2020 02:31:12 -0700
Message-Id: <20200829093112.1805440605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/y9HFZ8IGzztmVBI7CfIv3TdBzPo>
Subject: Re: [Ntp] Martin Duke's No Objection on draft-ietf-ntp-mode-6-cmds-09: (with COMMENT)
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: Sat, 29 Aug 2020 09:31:19 -0000

brian@innovationslab.net said:
>> With a document of this type, I am not sure if all of these type codes
>> and bit settings should be IANA registries or not.

I don't think it's appropriate to standardize the status words. 

> The WG discussed this option several years ago and decided that there wasn't
> any expectation of new mode 6 commands being added beyond the ones added
> between RFC 1305 and RFC 5905. 

That opens an interesting can of worms.

A significant fraction of the document is describing the details of 4 status 
words.  There is no corresponding description of the variables you can 
read/write via the Read Variables command and friends.

I think the status word descriptions should be moved to an appendix.  Some 
introductory material needs to explain that the details of what you can 
read/write are vendor dependent.  If you are going to use this document, you 
also need documentation (or code) for the implementation you are going to 
talke to that enumerates the names of variables you can access and describes 
their meaning.  RFC 5905 covers some of that for one implementation.  It 
doesn't describe the status words.  Their description is included here so you 
don't have to dig it out of the code.

-- 
These are my opinions.  I hate spam.