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

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 01 August 2022 06:47 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 BCEA3C14F736 for <ntp@ietfa.amsl.com>; Sun, 31 Jul 2022 23:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 7lQJihCwymwG for <ntp@ietfa.amsl.com>; Sun, 31 Jul 2022 23:47:49 -0700 (PDT)
Received: from mx4.uni-regensburg.de (mx4.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:4:4e7a]) (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 AC5C5C1594A8 for <ntp@ietf.org>; Sun, 31 Jul 2022 23:47:47 -0700 (PDT)
Received: from mx4.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B23906000059 for <ntp@ietf.org>; Mon, 1 Aug 2022 08:47:41 +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 91F436000056 for <ntp@ietf.org>; Mon, 1 Aug 2022 08:47:38 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 01 Aug 2022 08:47:38 +0200
Message-Id: <62E77708020000A10004BF9E@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.0
Date: Mon, 01 Aug 2022 08:47:36 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: james.ietf@gmail.com, mayer@pdmconsulting.net
Cc: "ntp@ietf.org" <ntp@ietf.org>, mlichvar@redhat.com, halmurray@sonic.net
References: <20220729162741.6E52D28C1CA@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <a61f270a-837f-b1be-15e4-835cd50899cf@pdmconsulting.net> <BF45EFF3-E992-4C4E-BB80-78061B60678F@gmail.com> <62E26A1B020000A10004BEF0@gwsmtp.uni-regensburg.de> <C7D2CA5A0200009E6A6A8CFC@gwsmtp.uni-regensburg.de> <62E3726E020000A10004BF1E@gwsmtp.uni-regensburg.de> <5641805A0200008B6A6A8CFC@gwsmtp.uni-regensburg.de> <46B361EB020000DBFDA5B133@gwsmtp.uni-regensburg.de> <815562A9020000655AEBDC6A@gwsmtp.uni-regensburg.de> <8FDB03C402000067824A10E1@gwsmtp.uni-regensburg.de>
In-Reply-To: <8FDB03C402000067824A10E1@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/efcOkA6QRtPzeo0Ms42rzXZaxgM>
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: Mon, 01 Aug 2022 06:47:52 -0000

Hi!

I wonder whether BCP-43  may be relevant. I found a manual page stating:

       option ntp-servers ip-address [, ip-address...  ];

         This  option  specifies  a  list of IP addresses indicating NTP (RFC
         5905) servers available to the client.  Servers should be listed  in
         order of preference.

       option tcode text;

         This option specifies a name of a zone entry in the TZ database.

         This option is included based on RFC 4833.

       option dhcp6.new-posix-timezone text;

         This option specifies a string suitable for the TZ variable.

         This option is included based on RFC 4833.

       option dhcp6.new-tzdb-timezone text;

         This option specifies a name of a zone entry in the TZ database.

         This option is included based on RFC 4833.


RFC-4833 is "Timezone Options for DHCP" (April, 2007)

Regards,
Ulrich


>>> James <james.ietf@gmail.com> schrieb am 01.08.2022 um 00:55 in Nachricht
<BF45EFF3-E992-4C4E-BB80-78061B60678F@gmail.com>:
> Danny,
> It would be very much appreciated if you could dig out the RFC number or 
> point to wherever DHCP specification, because I'm unable to find reference
to 
> anything that may hint, noting that the IANA registries for DHCP and DHCPv6

> options, there is RFC 5908 mentioned which covers DHCPv6, but I am unable to

> find anything in reference to DHCPv4 ‑ all that appears immediately obvious
is 
> Tag 4, which refers to RFC 2132, which in turn refers to the Time Protocol 
> defined in RFC 868.
> 
> ‑ J
> 
>> On 1 Aug 2022, at 00:27, Danny Mayer <mayer@pdmconsulting.net> wrote:
>> 
>> 
>> On 7/29/22 12:27 PM, Hal Murray wrote:
>>> mlichvar@redhat.com said:
>>>> You mean the TZ POSIX string (option 100) from RFC4833? That looks like
it
>>>> could work, even for announcing the DST change.
>>>> So, I guess the question is now are there any use cases for the local
time 
> in
>>>> NTP without DHCP?
>> That's irrelevant. NTP knows nothing about time zones.
>>> That only works if the DHCP servers in use actually support it.
>>> 
>>> Is there a tool for poking at DHCP servers to see what they provide?  I 
> poked
>>> around a bit but diddn't find one.
>>> 
>>> I scanned the man page for the ISC DHCP server and didn't find any mention

> of
>>> NTP or time zones.  (ntp was mentioned as a logging option.)
>> 
>> DHCP supports NTP server provisioning. I worked with the DHCP WG on it a 
> number of years ago. I don't know the RFC number.
>> 
>> 
>>> If a client gets its IP Address from a server, does it latch on to that 
> server
>>> and ignore others?  Or will it try broadcasting to find other servers
before
>>> giving up?  Can we setup a DHCP server that only provides time zone info?
>>> 
>> Read the DHCP RFCs. I don't know if there is provisioning for time zones.
>> 
>> Danny
>> 
>> _______________________________________________
>> ntp mailing list
>> ntp@ietf.org 
>> https://www.ietf.org/mailman/listinfo/ntp 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp