[Ntp] Antw: Re: Antw: Re: Antw: [EXT] Local time in NTPv5?

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 29 July 2022 07:04 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 94675C159496 for <ntp@ietfa.amsl.com>; Fri, 29 Jul 2022 00:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fiOAecGoGosh for <ntp@ietfa.amsl.com>; Fri, 29 Jul 2022 00:04:17 -0700 (PDT)
Received: from mx4.uni-regensburg.de (mx4.uni-regensburg.de [194.94.157.149]) (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 21765C157B4B for <ntp@ietf.org>; Fri, 29 Jul 2022 00:04:15 -0700 (PDT)
Received: from mx4.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6B38D600005B for <ntp@ietf.org>; Fri, 29 Jul 2022 09:04:11 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx4.uni-regensburg.de (Postfix) with ESMTP id 4BA5D600005A for <ntp@ietf.org>; Fri, 29 Jul 2022 09:04:10 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 29 Jul 2022 09:04:11 +0200
Message-Id: <62E38668020000A10004BF40@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.0
Date: Fri, 29 Jul 2022 09:04:08 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: mlichvar@redhat.com, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <YuFTPU4kvL+4teZO@localhost> <62E2597A020000A10004BED0@gwsmtp.uni-regensburg.de> <YuJfL7C4fHJ7N6Rm@localhost> <62E26A1B020000A10004BEF0@gwsmtp.uni-regensburg.de> <YuJrgS7UQJ0FTAET@localhost> <62E3726E020000A10004BF1E@gwsmtp.uni-regensburg.de>
In-Reply-To: <62E3726E020000A10004BF1E@gwsmtp.uni-regensburg.de>
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/K4yh32aHJL_Too-rrnCgZoOBIqg>
Subject: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] Local time in NTPv5?
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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, 29 Jul 2022 07:04:21 -0000

>>> "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> schrieb am 29.07.2022
um
07:38 in Nachricht <62E3726E020000A10004BF1E@gwsmtp.uni-regensburg.de>:
>>>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 28.07.2022 um 12:57 in
> Nachricht <YuJrgS7UQJ0FTAET@localhost>:
>> On Thu, Jul 28, 2022 at 12:51:07PM +0200, Ulrich Windl wrote:
>>> >>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 28.07.2022 um 12:04
> in
>>> Nachricht <YuJfL7C4fHJ7N6Rm@localhost>:
>>> > The device may no longer support the time zone. In countries that
>>> > decide to stop switching to/from DST, they would need to upgrade the
>>> > firmware, assuming one was actually provided by the vendor.
>>> 
>>> So if the vendor won't update the firmware for timezone changes, will the
>>> vendor update the firmware to implement new NTP features (like the one
>>> proposed)?
>> 
>> No, but new devices can support NTPv5 and it would be easier for
>> them to do if they don't have to care about time zones anymore.
>> 
>>> > That depends on the device. I'm sure there are some that have buttons
>>> > that need to be pressed and can forget the setting after power loss.
>>> 
>>> And what about the IP address then?
>> 
>> That is provided by DHCP.
> 
> So the IP will be supplied by DCHP, and the timezone (while possible with
> DHCP) will be ignored and gotten from NTP instead?
> A really strange concept to ignore what's existing already while demanding
a
> new mechnism that really does not fin into NTP IMHO.

s/fin/fit; # Sorry!

> 
> Regards,
> Ulrich
> 
>> 
>> ‑‑ 
>> Miroslav Lichvar
> 
> 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp