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

"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> Tue, 19 September 2017 06:52 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 7774F1342D3 for <ntp@ietfa.amsl.com>; Mon, 18 Sep 2017 23:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 7zEA_CWDyOjJ for <ntp@ietfa.amsl.com>; Mon, 18 Sep 2017 23:52:48 -0700 (PDT)
Received: from rrzmta1.uni-regensburg.de (rrzmta1.uni-regensburg.de [194.94.155.51]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 214CA133023 for <ntp@ietf.org>; Mon, 18 Sep 2017 23:52:47 -0700 (PDT)
Received: from rrzmta1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 451BD5CDF0 for <ntp@ietf.org>; Tue, 19 Sep 2017 08:52:46 +0200 (CEST)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta1.uni-regensburg.de (Postfix) with ESMTP id E51D45DD8B for <ntp@ietf.org>; Tue, 19 Sep 2017 08:52:45 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Tue, 19 Sep 2017 08:52:45 +0200
Message-Id: <59C0BEBB020000A100027F1A@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 14.2.2
Date: Tue, 19 Sep 2017 08:52:43 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, brian@innovationslab.net
References: <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net>
In-Reply-To: <d5a5ba98-65f2-f2e0-a0ec-40114213fc03@innovationslab.net>
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/djkIkx1znXXxxysynbzRwzyv2yA>
Subject: [Ntp] 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: Tue, 19 Sep 2017 06:52:50 -0000

>>> 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)

Regards,
Ulrich