Re: [Ntp] Leap second draft

"Patrik Fältström " <paf@frobbit.se> Fri, 24 January 2020 18:59 UTC

Return-Path: <paf@frobbit.se>
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 C9D1A1200C4 for <ntp@ietfa.amsl.com>; Fri, 24 Jan 2020 10:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 KFwSifbfrDaU for <ntp@ietfa.amsl.com>; Fri, 24 Jan 2020 10:59:21 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8CEE12004C for <ntp@ietf.org>; Fri, 24 Jan 2020 10:59:20 -0800 (PST)
Received: from [192.165.72.241] (unknown [IPv6:2a02:80:3ffc:0:84ed:768a:866d:6af5]) by mail.frobbit.se (Postfix) with ESMTPSA id EFDAB26F6F; Fri, 24 Jan 2020 19:59:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1579892357; bh=9Fsn6yDRFKMX19TC8PqNqTumJcZKLZOaBGyW76+d2l4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ljbhOw2eMcy6qa3O7JLDGfmbQl4JY6Bu3Yrg1WwrEx7le3j9secEgNtyGp75F7K83 slEEMAW/H1Y6Q4fdhtcFS8fYE+IcGAvTxofAdmp80OktJDfR2HYmoz1vJGUDt0CHt6 ca4kRIhVHu3fhwaMTAMenokR2tRqrjjbxXbAcysI=
From: Patrik Fältström <paf@frobbit.se>
To: Watson Ladd <watsonbladd@gmail.com>
Cc: NTP WG <ntp@ietf.org>, Daniel Franke <dfoxfranke@gmail.com>, Warner Losh <imp@bsdimp.com>
Date: Fri, 24 Jan 2020 19:59:15 +0100
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <4E76AC4C-38F7-4086-B118-C85D279CF4DF@frobbit.se>
In-Reply-To: <CACsn0ckf91GH7tSr6d2KEz7T6N7z0t7LyF6JSr66dn0OA5m2Tg@mail.gmail.com>
References: <CAJm83bD5Ozkpg5TpkogOW6xeeNQL3ZziLO9URM7haqN8Wrp=Wg@mail.gmail.com> <CACsn0cmZkRifrnbVbPw2=9ww+ttmbAGCW39LhT+jhDLLyU8e+A@mail.gmail.com> <CANCZdfo_cbo3UngOWEc4mM4_nLK=J81zSiF0shvsu5mENUGPMw@mail.gmail.com> <CANCZdfo-OW7d454Qqo9eqfOpw367A4gg4-2UJ5XdC=n0u_t+BQ@mail.gmail.com> <F7D6BF99-260C-467B-9AF7-94F1F5E2721B@frobbit.se> <CACsn0ckf91GH7tSr6d2KEz7T6N7z0t7LyF6JSr66dn0OA5m2Tg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_ABEAFA9B-06C1-46C2-A6AA-4BFF8C387CE7_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/EK7pHHbxBchZcnVrZL_-lzmIMvk>
Subject: Re: [Ntp] Leap second draft
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: Fri, 24 Jan 2020 18:59:23 -0000

On 24 Jan 2020, at 16:04, Watson Ladd wrote:

> Why does POSIX matter for NTP timestamps? We can always clarify the language independently.

I completely agree, but so much discussions about NTP today are built upon the POSIX definitions. For example by having Google (and possibly others) having NTP servers that do smear.

<https://developers.google.com/time/smear>

Personally, I find the fact the leap second itself is undefined is of no problem for NTP or implementations. The problem is when the implementations have to push the response from NTP into a POSIX based environment that do not take leap seconds into account.

   Patrik