IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 07 January 2021 08:23 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 9874D3A09BD for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 00:23:18 -0800 (PST)
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 7i8qWi1H6zVI for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 00:23:16 -0800 (PST)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 3870E3A003E for <ntp@ietf.org>; Thu, 7 Jan 2021 00:23:16 -0800 (PST)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3B1CD6000050 for <ntp@ietf.org>; Thu, 7 Jan 2021 09:23:14 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 9EDB0600004D for <ntp@ietf.org>; Thu, 7 Jan 2021 09:23:11 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 07 Jan 2021 09:23:11 +0100
Message-Id: <5FF6C4EC020000A10003E041@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Thu, 07 Jan 2021 09:23:08 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, emmanuel.fuste@thalesgroup.com
References: <20210105124544.5EF5C40605C@ip-64-139-1-69.sjc.megapath.net> <f876a3ff-16ee-fc63-c27c-d5a3cb847a3d@meinberg.de> <59A706AB-A151-4779-989B-B957F2C50FD0@redfish-solutions.com> <f6871e77-7130-0234-b30f-a1efd7fc501d@meinberg.de> <5d9b2399-dbb4-99c8-4495-69ad03479a23@thalesgroup.com>
In-Reply-To: <5d9b2399-dbb4-99c8-4495-69ad03479a23@thalesgroup.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/7K4_BHsYg5BWEUi96HiN_9lrgZI>
Subject: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
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: Thu, 07 Jan 2021 08:23:19 -0000

>>> FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com> schrieb am 06.01.2021 um
12:43
in Nachricht <5d9b2399-dbb4-99c8-4495-69ad03479a23@thalesgroup.com>:
> Le 06/01/2021 à 11:58, Martin Burnicki a écrit :
>>
>> Or you would have to provide (and maintain) an NTP server implementation
>> that supports both v4 and v5, depending on the version of the request.
> As the vast majority of today ones which still support v1/v2/v3/v4, 
> being based on ntpd,  and v3/v4 for most of the others.

My initial feeling is that a NTPv5 server should respond to v3 and v4
requests. If networks really have v2 clients or older, they'd need some
"gateway" to translate the time.

> 
> Emmanuel.
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp

v2.23.0 | Report a Bug | By Email