Re: [Ntp] draft-ietf-ntp-mode-6-cmds : Issue 1

Harlan Stenn <stenn@nwtime.org> Mon, 18 September 2017 23:37 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 52BB1133055 for <ntp@ietfa.amsl.com>; Mon, 18 Sep 2017 16:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 mknib1j7Wij1 for <ntp@ietfa.amsl.com>; Mon, 18 Sep 2017 16:36:59 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01917132981 for <ntp@ietf.org>; Mon, 18 Sep 2017 16:36:58 -0700 (PDT)
Received: from [10.66.3.3] (96-41-166-181.dhcp.mdfd.or.charter.com [96.41.166.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id BB440B864; Mon, 18 Sep 2017 23:36:58 +0000 (UTC)
To: ntp@ietf.org
References: <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net>
From: Harlan Stenn <stenn@nwtime.org>
Message-ID: <ad816de0-b31e-2b06-a628-28fc32d9a2f1@nwtime.org>
Date: Mon, 18 Sep 2017 16:36:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/LD6DPHwQhHVyDhag4pVYDmT9vrQ>
Subject: Re: [Ntp] draft-ietf-ntp-mode-6-cmds : Issue 1
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 18 Sep 2017 23:37:00 -0000


On 9/18/2017 10:10 AM, Brian Haberman wrote:
> Ulrich noted that this document does not specify a version number for
> the mode 6 commands. I had suggested specifying it as "version 4 (or
> earlier)" given that the introduction of mode 6 commands has occurred at
> various versions of the protocol starting at RFC 1305. Ulrich pointed
> out that the version number drives the interpretation of the status words.
> 
> For people who have implemented or use mode 6 commands, what makes sense
> here? Do we need to specify a version number per mode 6 command?

I've long wanted a way to identify more information about information
about what information is available via mode6 commands, and the format
of that information.

While some of this information is part of the "core", a lot of it is
implementation-specific, and can easily change from one code version to
the next.

I don't think we want to cast any of this into concrete.

On the other hand, we do need a way to figure out what's available
(which may changed based on authorization levels) and the format in
which it's presented.

-- 
Harlan Stenn, Network Time Foundation
http://nwtime.org - be a Member!