Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTPv5?
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 29 July 2022 05:39 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 032FDC13C50F for <ntp@ietfa.amsl.com>; Thu, 28 Jul 2022 22:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 uuHHtxzZKwfx for <ntp@ietfa.amsl.com>; Thu, 28 Jul 2022 22:39:04 -0700 (PDT)
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 7822BC15C509 for <ntp@ietf.org>; Thu, 28 Jul 2022 22:39:03 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5DF38600005D for <ntp@ietf.org>; Fri, 29 Jul 2022 07:38:58 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 4A5ED600004D for <ntp@ietf.org>; Fri, 29 Jul 2022 07:38:55 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 29 Jul 2022 07:38:56 +0200
Message-Id: <62E3726E020000A10004BF1E@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.0
Date: Fri, 29 Jul 2022 07:38:54 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: mlichvar@redhat.com
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>
In-Reply-To: <YuJrgS7UQJ0FTAET@localhost>
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/aYy_4oD34pbaXI70cSvSk4Oar8E>
Subject: Re: [Ntp] 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 05:39:06 -0000
>>> 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. Regards, Ulrich > > ‑‑ > Miroslav Lichvar
- [Ntp] Local time in NTPv5? Miroslav Lichvar
- Re: [Ntp] Local time in NTPv5? Doug Arnold
- Re: [Ntp] Local time in NTPv5? Hal Murray
- Re: [Ntp] Local time in NTPv5? Paul Gear
- Re: [Ntp] Local time in NTPv5? Miroslav Lichvar
- Re: [Ntp] Local time in NTPv5? Martin Burnicki
- Re: [Ntp] Local time in NTPv5? David Venhoek
- [Ntp] Antw: [EXT] Local time in NTPv5? Ulrich Windl
- Re: [Ntp] Local time in NTPv5? Hal Murray
- Re: [Ntp] Antw: [EXT] Local time in NTPv5? Miroslav Lichvar
- [Ntp] Antw: [EXT] Re: Local time in NTPv5? Ulrich Windl
- [Ntp] Antw: Re: Antw: [EXT] Local time in NTPv5? Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Ulrich Windl
- [Ntp] Antw: Re: Antw: Re: Antw: [EXT] Local time … Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Hal Murray
- Re: [Ntp] Local time in NTPv5? Danny Mayer
- Re: [Ntp] Local time in NTPv5? Warner Losh
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Danny Mayer
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… James
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Steve Allen
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Hal Murray
- [Ntp] Antw: Re: Antw: Re: Antw: [EXT] Local time … Ulrich Windl
- Re: [Ntp] Local time in NTPv5? Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: [EXT] Local time in NTP… Miroslav Lichvar
- [Ntp] Antw: [EXT] Re: Local time in NTPv5? Ulrich Windl
- [Ntp] Antw: Re: Antw: Re: Antw: [EXT] Local time … Ulrich Windl