Re: [Ntp] Antw: Re: Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com> Mon, 11 January 2021 11:02 UTC

Return-Path: <emmanuel.fuste@thalesgroup.com>
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 16F1B3A0A21 for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 03:02:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=thalesgroup.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRIEVf90FR8H for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 03:02:01 -0800 (PST)
Received: from thsbbfxrt01p.thalesgroup.com (thsbbfxrt01p.thalesgroup.com [192.54.144.131]) (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 2CBB63A0A1E for <ntp@ietf.org>; Mon, 11 Jan 2021 03:02:01 -0800 (PST)
Received: from thsbbfxrt01p.thalesgroup.com (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4DDrPg6gFHz45Pr for <ntp@ietf.org>; Mon, 11 Jan 2021 12:01:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thalesgroup.com; s=xrt20181201; t=1610362919; bh=oW/svVmsT+WPhElKEvHD9fd7SJ7coGwtAeneHAp/wAE=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Transfer-Encoding:MIME-Version:From; b=XZJDcxn4jZoWSfwtTYflKaM6Pi4bqM4/SH0mci5Peti7KgZVk9aKyKf5bi4GeqHO5 u+NAYsFDCATr/6CIjXi39cB6qyG2GZi4AaAG6reMLc9BHTsNPrkHBUypvrsE816Vc/ OQq+WSD+CZ0wI5ApOKBWDaUSz4V4tJi6atLDI3NIfR1sOpUwwdN60fPFCgH64nMONa ipt+CFsAdSgzf4cZ7JGWFILai8r6tBlXx5KwMNPft6FJGVREOPnlq6lY6VfN2Nn77w sigDYQnyZLtAbrM9BgXLqOshw+zxjLoPmtCyorKKluFcEXa0koMtWerNOIHECiXzPD qZRlnoZdIbdXg==
From: FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com>
To: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: [Ntp] Antw: Re: Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
Thread-Index: AQHW6Afkhkmv+LN1jEyMPYU7A9zu2aoiMYgA
Date: Mon, 11 Jan 2021 11:01:59 +0000
Message-ID: <83983db1-9362-dff4-5fe3-277fefe12b3d@thalesgroup.com>
References: <20210111105245.BB97740605C@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20210111105245.BB97740605C@ip-64-139-1-69.sjc.megapath.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
x-pmwin-version: 4.0.3, Antivirus-Engine: 3.79.0, Antivirus-Data: 5.80
Content-Type: text/plain; charset="utf-8"
Content-ID: <961ECB8B64299E4EB577CCB435F45594@iris.infra.thales>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/bX6IZO8ITBd2bIcTBocvzilgXN8>
Subject: Re: [Ntp] Antw: Re: Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 11 Jan 2021 11:02:03 -0000

Le 11/01/2021 à 11:52, Hal Murray a écrit :
> Martin Burnicki said:
>> The reason for letting the NTP server send smeared time to its clients is
>> that you *only* have to configure your server(s) accordingly, and *all* NTP
>> clients get the same, smeared time.
> Another consideration tangled up in this mess is the availability of client
> software.
>
> If you are a single organization with several NTP servers and many clients running different OSes and/or different versions, it's much simpler to modify the servers.  (Of course you have to make sure that those servers aren't serving any clients who don't want smeared time.)
>
> If the context is something like the pool, it will be much simpler if the servers distribute unsmeared time and the clients turn on the smear-me option.  That assumes the NTP software on the clients gets updated which may not work for people who run old/stable software.  I don't see a simple solution.  My guess is that anybody with that problem will have to continue to run old/smearing NTP servers until their clients are all, eventually, upgraded.
>
> Actually, they don't have to upgrade all the servers, only the ones that have to run over a leap second.  They can turn off the others and turn them back on after the leap.
>
> What's the effective lifetime of long-lifetime distros?  Typical numbers that I see are 5 years.  I think we could live with that.  I think a few entries in a FAQ would explain most of the problems.
>
> But how many sites keep running the old distro, perhaps paying for extended support?
Your observation is right, but we are talking about NTPv5 which is today 
implemented and deployed nowhere.
For me it advocate for the "smear-me" client side option only for v5.

Emmanuel.