Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and leap second smearing
"Windl, Ulrich" <u.windl@ukr.de> Fri, 30 June 2023 10:32 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 12F84C151099 for <ntp@ietfa.amsl.com>; Fri, 30 Jun 2023 03:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, 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 YxrsUIYwz_sm for <ntp@ietfa.amsl.com>; Fri, 30 Jun 2023 03:32:16 -0700 (PDT)
Received: from mail02.ukr.de (mail02.ukr.de [193.175.194.182]) (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 C6C4AC15106F for <ntp@ietf.org>; Fri, 30 Jun 2023 03:32:15 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="6600,9927,10756"; a="254459"
X-IronPort-AV: E=Sophos;i="6.01,170,1684792800"; d="scan'208";a="254459"
Received: from unknown (HELO ukr-excmb01.ukr.local) ([172.24.6.61]) by dmz-infcsg02.ukr.dmz with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Jun 2023 12:32:15 +0200
Received: from ukr-excmb03.ukr.local (172.24.6.63) by ukr-excmb01.ukr.local (172.24.6.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.27; Fri, 30 Jun 2023 12:32:13 +0200
Received: from ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0]) by ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0%5]) with mapi id 15.01.2507.027; Fri, 30 Jun 2023 12:32:13 +0200
From: "Windl, Ulrich" <u.windl@ukr.de>
To: David Venhoek <david@venhoek.nl>, Paul Gear <ntp=40libertysys.com.au@dmarc.ietf.org>
CC: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: [EXT] Re: [Ntp] Consensus call: NTPv5 and leap second smearing
Thread-Index: AQHZqiQ/Cj/pLAYOIk6tkrOvrFRgGa+i70GAgAA4pEA=
Date: Fri, 30 Jun 2023 10:32:13 +0000
Message-ID: <83633d47eecd4e039111fa85e1d40e39@ukr.de>
References: <29343948-036E-4514-8B42-689C19A61813@gmail.com> <a8671454-775c-014b-12df-66dffbe01e39@libertysys.com.au> <CAPz_-SXEqSWvxAZB+qPix31fF077Po3C9XkMzTTLeOTAr44uQA@mail.gmail.com>
In-Reply-To: <CAPz_-SXEqSWvxAZB+qPix31fF077Po3C9XkMzTTLeOTAr44uQA@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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/5JDBQHZG-EdYXUt1SLc3nPlDUk4>
Subject: Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and leap second smearing
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, 30 Jun 2023 10:32:20 -0000
Also acceptable IMHO (+1) -----Original Message----- From: ntp <ntp-bounces@ietf.org> On Behalf Of David Venhoek Sent: Friday, June 30, 2023 11:09 AM To: Paul Gear <ntp=40libertysys.com.au@dmarc.ietf.org> Cc: ntp@ietf.org Subject: [EXT] Re: [Ntp] Consensus call: NTPv5 and leap second smearing I wholly concur with Paul's view on this. Kind regards, David Venhoek On Thu, Jun 29, 2023 at 2:54 AM Paul Gear <ntp=40libertysys.com.au@dmarc.ietf.org> wrote: > > On 29/6/23 05:55, Dieter Sibold wrote: > > Dear all, > > at IETF 116 we decided to have two consensus calls regarding the content of the NTPv5 requirement draft. These are consensus calls that we would like to conduct to help progress the NTPv5 requirements document (https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5-requirements/). Both consensus calls will run until July 21st 2023 and will be discussed at the next NTP wg meeting at IETF 117 in San Francisco. > > The second consensus call: > > Regarding leap second smearing: > > Currently, the NTPv5 requirement draft states that NTP servers should not apply leap second smearing to transmitted timestamps. Shall NTPv5 support leap second smearing? If yes, shall the NTP server apply leap smearing to the transmitted timestamps or otherwise shall the client perform leap second smearing? > > > The reason smearing gets used under current NTP versions is because the people using it have large-scale issues with timestamp-sensitive software, and it's more efficient to implement the smearing on the servers than on the clients, which can be orders of magnitude greater in terms of scale. If we prevent this, we will only hinder the adoption of newer versions. > > So, yes, NTPv5 should support leap second smearing, and yes, it should be possible to apply that smearing to the transmitted timestamps so that clients don't have to be configured for it. > > My suggestion in terms of BCP 14 (RFC 2119/8174) terminology is that NTPv5: > > MUST support sending non-leap-smeared timestamps > MAY support sending leap-smeared timestamps > SHOULD send non-leap-smeared timestamps by default > if it sends leap-smeared timestamps MUST provide indication (via a flag or extension) that they are in use > if it sends leap-smeared timestamps, SHOULD send indication (via an extension?) of the current UTC-to-smeared-time offset > > Regards, > Paul > > _______________________________________________ > 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
- [Ntp] Consensus call: NTPv5 and leap second smear… Dieter Sibold
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Salz, Rich
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Paul Gear
- Re: [Ntp] Consensus call: NTPv5 and leap second s… David Venhoek
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Windl, Ulrich
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Dave Hart
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Steven Sommars
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Harlan Stenn
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Harlan Stenn
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Danny Mayer
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Daniel Franke
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Harlan Stenn
- Re: [Ntp] Consensus call: NTPv5 and leap second s… James Browning
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Harlan Stenn
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Danny Mayer
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Martin Burnicki
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Dieter Sibold
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Doug Arnold
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Denis Reilly
- Re: [Ntp] Consensus call: NTPv5 and leap second s… James
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Martin Burnicki
- Re: [Ntp] Consensus call: NTPv5 and leap second s… kristof.teichel
- Re: [Ntp] Consensus call: NTPv5 and leap second s… martin.langer
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Miroslav Lichvar
- Re: [Ntp] [EXTERNAL] Re: Consensus call: NTPv5 an… Denis Reilly
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Daniel Franke
- [Ntp] Antwort: Re: Consensus call: NTPv5 and leap… kristof.teichel
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Warner Losh
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Steve Allen
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Watson Ladd
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Harlan Stenn
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Dave Hart
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Windl, Ulrich
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Martin Burnicki
- Re: [Ntp] [EXTERNAL] Re: Consensus call: NTPv5 an… Martin Burnicki
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Martin Burnicki
- Re: [Ntp] [EXTERNAL] Re: Consensus call: NTPv5 an… Denis Reilly
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Martin Burnicki
- Re: [Ntp] [EXTERNAL] Re: Consensus call: NTPv5 an… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Consensus call: NTPv5 and… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Windl, Ulrich
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Consensus call… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Re: Consensus call: NTPv5 and… Harlan Stenn
- Re: [Ntp] [EXT] Re: Re: Re: Consensus call: NTPv5… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Re: Consensus call: NTPv5… Harlan Stenn
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Consensus call: NTPv5 and… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Re: Re: Consensus call: N… Windl, Ulrich
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Consensus call… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Re: Consensus call: NTPv5… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Re: Re: Re: Consensus call: N… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: Re: Re: Consensus call: N… Harlan Stenn
- Re: [Ntp] [EXT] Re: Re: Re: Consensus call: NTPv5… Harlan Stenn
- Re: [Ntp] [EXT] Re: Re: Re: Re: Re: Consensus cal… Windl, Ulrich
- Re: [Ntp] [EXTERNAL] Re: [EXT] Re: Consensus call… Denis Reilly
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Miroslav Lichvar
- Re: [Ntp] [EXTERNAL] Re: [EXT] Re: Consensus call… Martin Burnicki
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Daniel Franke
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Warner Losh
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Warner Losh
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Re: Consensus … Windl, Ulrich
- Re: [Ntp] [EXT] Re: Re: Consensus call: NTPv5 and… Windl, Ulrich
- Re: [Ntp] Consensus call: NTPv5 and leap second s… Miroslav Lichvar
- Re: [Ntp] [EXT] Re: Consensus call: NTPv5 and lea… Martin Burnicki
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Re: Consensus … Martin Burnicki
- Re: [Ntp] [EXTERNAL] Re: [EXT] Re: Consensus call… Danny Mayer
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Re: Consensus … Windl, Ulrich
- Re: [Ntp] [EXTERNAL] Re: [EXT] Re: Consensus call… Martin Burnicki
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Re: Consensus … Harlan Stenn
- Re: [Ntp] [EXT] Re: [EXTERNAL] Re: Re: Consensus … Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: [EXTERNAL] Re: Re: Consen… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Re: [EXTERNAL] Re: Re: Consen… Martin Burnicki
- Re: [Ntp] [EXT] Re: Re: [EXTERNAL] Re: Re: Consen… Windl, Ulrich
- Re: [Ntp] [EXT] Re: Re: [EXTERNAL] Re: Re: Consen… Martin Burnicki