Re: [Ntp] Leap smearing

"Gary E. Miller" <gem@rellim.com> Thu, 10 December 2020 21:21 UTC

Return-Path: <gem@rellim.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 D68C33A12FF for <ntp@ietfa.amsl.com>; Thu, 10 Dec 2020 13:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 0F0cQDExF3R9 for <ntp@ietfa.amsl.com>; Thu, 10 Dec 2020 13:21:29 -0800 (PST)
Received: from rellim.com (spidey.rellim.com [204.17.205.8]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E817C3A12E5 for <ntp@ietf.org>; Thu, 10 Dec 2020 13:21:28 -0800 (PST)
Received: from spidey.rellim.com (spidey.rellim.com [204.17.205.8]) by rellim.com (Postfix) with ESMTPSA id AC45820014B; Thu, 10 Dec 2020 13:21:27 -0800 (PST)
Date: Thu, 10 Dec 2020 13:21:22 -0800
From: "Gary E. Miller" <gem@rellim.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org>, ntp@ietf.org
Message-ID: <20201210132122.5035169d@spidey.rellim.com>
In-Reply-To: <20201210203301.0EE8840605C@ip-64-139-1-69.sjc.megapath.net>
References: <540f9f25-5c7a-b6ac-9fcf-6eeb3162dcac@meinberg.de> <20201210203301.0EE8840605C@ip-64-139-1-69.sjc.megapath.net>
Organization: Rellim
X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/_pX9L8VRP4ad78CcgpVP+a."; protocol="application/pgp-signature"; micalg="pgp-sha512"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/P-FeKMeBi43d_MY28qQc2TKMi5k>
Subject: Re: [Ntp] Leap smearing
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: Thu, 10 Dec 2020 21:21:31 -0000

Yo Hal!

On Thu, 10 Dec 2020 12:33:01 -0800
Hal Murray <hmurray@megapathdsl.net> wrote:

> martin.burnicki=40meinberg.de@dmarc.ietf.org said:
> > However, if you have "normal" clients and you just want to prevent
> > your applications from hickups when the system time is stepped
> > back, it's easier to let the server smear the time, because you
> > only have to configure this once, and all clients behave the same.
> >  
> 
> That seems appropriate when you have an existing installed base using
> an existing protocol.
> 
> But we are talking about a new protocol so there is no installed
> base.  It seems reasonable to me to move the smear decision to the
> client side. 

+1

Removing it from the wire protocol make one less thing to get wrong on
the wire.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin