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

"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> Fri, 22 September 2017 06:02 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 48ECD132939 for <ntp@ietfa.amsl.com>; Thu, 21 Sep 2017 23:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 gdDET-RJr6tW for <ntp@ietfa.amsl.com>; Thu, 21 Sep 2017 23:02:23 -0700 (PDT)
Received: from rrzmta2.uni-regensburg.de (rrzmta2.uni-regensburg.de [194.94.155.52]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8CBE1321A1 for <ntp@ietf.org>; Thu, 21 Sep 2017 23:02:22 -0700 (PDT)
Received: from rrzmta2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C4423795C2 for <ntp@ietf.org>; Fri, 22 Sep 2017 08:02:20 +0200 (CEST)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta2.uni-regensburg.de (Postfix) with ESMTP id 99D97793FD for <ntp@ietf.org>; Fri, 22 Sep 2017 08:02:20 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Fri, 22 Sep 2017 08:02:20 +0200
Message-Id: <59C4A769020000A100028053@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 14.2.2
Date: Fri, 22 Sep 2017 08:02:17 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, stenn@nwtime.org
References: <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net> <59C0BEBB020000A100027F1A@gwsmtp1.uni-regensburg.de> <90ca0015-6ff4-9f68-20c9-a978fea6f491@innovationslab.net> <fd938fee-ed5c-a0ca-148f-a20a8c72aaa5@nwtime.org>
In-Reply-To: <fd938fee-ed5c-a0ca-148f-a20a8c72aaa5@nwtime.org>
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/SyMeRJjX8uQsrcAydYDZL1WNYbk>
Subject: [Ntp] Antw: Re: Antw: 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: Fri, 22 Sep 2017 06:02:25 -0000

>>> Harlan Stenn <stenn@nwtime.org> schrieb am 21.09.2017 um 00:42 in Nachricht
<fd938fee-ed5c-a0ca-148f-a20a8c72aaa5@nwtime.org>:

> 
> On 9/20/17 12:10 PM, Brian Haberman wrote:
>> 
>> 
>> On 9/19/17 2:52 AM, Ulrich Windl wrote:
>>>>>> Brian Haberman <brian@innovationslab.net> schrieb am 18.09.2017 um 19:10 in
>>> Nachricht <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net>:
>>>> 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?
>>>
>>> Hi!
>>>
>>> I think there are several issues:
>>>
>>> 1) Assuming there are different versions (there are!), how can one find out 
> which version the server implements? See 2)
>>>
>>> 2) if a client requests a version different from the server, what should the 
> server do? The server could respond with a different version number, 
> indicating that it is not willing to respond / privide the information in the 
> format requested. Or the server could respond with a "bad request" status. 
> Finally the server could respond in the format requested... I have slight 
> favor for the first variant unless there is a command to find out what 
> message format versions the server can provide.
>>>
>>> 3) As it seems to be now, the server ignores the version (versions 2, 3, and 
> 4 all seem to work)
>>>
>> 
>> The above seems to argue for two things:
>> 
>> 1) A preliminary handshake between an NTP server and the mode6-speaking
>> client to determine what version is in use.
>> 
>> 2) A change to the operating basis of the mode 6 commands in that the
>> above mentioned handshake occurs before actually sending the mode 6 command.
>> 
>> Is that a good representation of what is being asked for?
> 
> If it is, I'm thinking we'd want a mode 6 "Identify" command, that would
> have this information in a response.  This response would likely contain
> different data before/after authentication.

Why that? You should elaborate on the role of authentication.

> 
> I'd also much rather we had changes to do this that are tested and known
> to do what we want instead of codifying what folks hope will be a good
> solution.
> 
> I'm happy to work with collaborative folks, experienced or not, who want
> to dig in to this.
> 
> -- 
> Harlan Stenn <stenn@nwtime.org>
> http://networktimefoundation.org - be a member!
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp