IETF Logo Mail Archive

[Ntp] Re: [EXT] Re: I-D Action: draft-ietf-ntp-ntpv5-02.txt

"Windl, Ulrich" <u.windl@ukr.de> Mon, 29 July 2024 06:04 UTC

Return-Path: <u.windl@ukr.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 6F5FCC14F701; Sun, 28 Jul 2024 23:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=unavailable 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 awQYpJwCICr5; Sun, 28 Jul 2024 23:04:15 -0700 (PDT)
Received: from mail01.ukr.de (mail01.ukr.de [193.175.194.181]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06444C14F6FB; Sun, 28 Jul 2024 23:04:12 -0700 (PDT)
X-CSE-ConnectionGUID: psJCZi9+QcWGPtdyINwJrw==
X-CSE-MsgGUID: O77612JFT0WWSupWT5+Uhw==
X-ThreatScanner-Verdict: Negative
X-IronPort-AV: E=McAfee;i="6700,10204,11147"; a="940698"
X-IronPort-AV: E=Sophos;i="6.09,245,1716242400"; d="scan'208,217";a="940698"
Received: from unknown (HELO ukr-excmb02.ukr.local) ([172.24.6.62]) by dmz-infcsg01.ukr.dmz with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2024 08:04:09 +0200
Received: from ukr-excmb03.ukr.local (172.24.6.63) by ukr-excmb02.ukr.local (172.24.6.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 29 Jul 2024 08:04:08 +0200
Received: from ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0]) by ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0%4]) with mapi id 15.01.2507.039; Mon, 29 Jul 2024 08:04:08 +0200
From: "Windl, Ulrich" <u.windl@ukr.de>
To: Dieter Sibold <dsibold.ietf@gmail.com>, Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org>
Thread-Topic: [EXT] [Ntp] Re: I-D Action: draft-ietf-ntp-ntpv5-02.txt
Thread-Index: AQHaxooffQwy92Ap80SPHR09fesp0LIJcd8AgAP6xyA=
Date: Mon, 29 Jul 2024 06:04:08 +0000
Message-ID: <48ffc62398b24b4da623c2bfe3c924a4@ukr.de>
References: <171880149775.17275.17603202157290281888@ietfa.amsl.com> <AM7PR02MB576576740392B0B63189B4EFCFD42@AM7PR02MB5765.eurprd02.prod.outlook.com> <CAKtkH6yn4X1Eo8Mh1LY0zC9doX_Yxh8Aw=7iPHDxg1p=K0dERA@mail.gmail.com>
In-Reply-To: <CAKtkH6yn4X1Eo8Mh1LY0zC9doX_Yxh8Aw=7iPHDxg1p=K0dERA@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.3.1]
Content-Type: multipart/alternative; boundary="_000_48ffc62398b24b4da623c2bfe3c924a4ukrde_"
MIME-Version: 1.0
Message-ID-Hash: GIY3TI7ZNYDSQVWU6UQSEPSXUBM3MKXC
X-Message-ID-Hash: GIY3TI7ZNYDSQVWU6UQSEPSXUBM3MKXC
X-MailFrom: u.windl@ukr.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "i-d-announce@ietf.org" <i-d-announce@ietf.org>, "ntp@ietf.org" <ntp@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: [EXT] Re: I-D Action: draft-ietf-ntp-ntpv5-02.txt
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/cfFyzBepyBpUR_mzC1l8kzoRkyY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>

Hi!

I’m afraid LI=3 semantics is “traditional” (mixing “sync” state with “leap second information”). Whether it was a good idea back then is herd to decide now, but it is like it is.
Another question is whether we want a “radical redesign” for v5.

Regards,
Ulrich


From: Dieter Sibold <dsibold.ietf@gmail.com>
Sent: Friday, July 26, 2024 9:16 PM
To: Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org>
Cc: i-d-announce@ietf.org; ntp@ietf.org
Subject: [EXT] [Ntp] Re: I-D Action: draft-ietf-ntp-ntpv5-02.txt

Hi Miroslav,

thanks for this well written document.

Working group chair's hat off:
I have a question regarding the header fields LI and Flags. According to the draft:
- LI=3 signals to the client that the server is not synchronised
- Flag=1 signals to the client that the server does not have a source of time which provides leap information (unknown leap)

I'm wondering why the information about the unknown leap is transmitted by the field Flags and not bei the field LI? Would it not make sense that all leap seconds related information is transmitted by the Leap Indicator field LI? Could the meaning of LI=3 and Flag=1 be swapped? Or are there technical reasons against this?

- Dieter

Am Di., 25. Juni 2024 um 00:57 Uhr schrieb Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org<mailto:40meinberg-usa.com@dmarc.ietf.org>>:
The corrections and additions to ntpv5 in this draft all look like improvements to me.
________________________________
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Sent: Wednesday, June 19, 2024 8:51 AM
To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: ntp@ietf.org<mailto:ntp@ietf.org> <ntp@ietf.org<mailto:ntp@ietf.org>>
Subject: [Ntp] I-D Action: draft-ietf-ntp-ntpv5-02.txt

Internet-Draft draft-ietf-ntp-ntpv5-02.txt is now available. It is a work item
of the Network Time Protocols (NTP) WG of the IETF.

   Title:   Network Time Protocol Version 5
   Author:  Miroslav Lichvar
   Name:    draft-ietf-ntp-ntpv5-02.txt
   Pages:   31
   Dates:   2024-06-19

Abstract:

   This document describes the version 5 of the Network Time Protocol
   (NTP).

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-ntpv5-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-ntp-ntpv5-02

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
ntp mailing list -- ntp@ietf.org<mailto:ntp@ietf.org>
To unsubscribe send an email to ntp-leave@ietf.org<mailto:ntp-leave@ietf.org>
_______________________________________________
ntp mailing list -- ntp@ietf.org<mailto:ntp@ietf.org>
To unsubscribe send an email to ntp-leave@ietf.org<mailto:ntp-leave@ietf.org>

v2.26.15 | Report a Bug | By Email | System Status