IETF Logo Mail Archive

Re: [Ntp] Finding leap-seconds.list

Dieter Sibold <dsibold.ietf@gmail.com> Tue, 13 November 2018 12:39 UTC

Return-Path: <dsibold.ietf@gmail.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 30110129619 for <ntp@ietfa.amsl.com>; Tue, 13 Nov 2018 04:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aAUIizNJUxWr for <ntp@ietfa.amsl.com>; Tue, 13 Nov 2018 04:39:29 -0800 (PST)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01462126DBF for <ntp@ietf.org>; Tue, 13 Nov 2018 04:39:28 -0800 (PST)
Received: by mail-ed1-x52f.google.com with SMTP id 14so1142866eds.8 for <ntp@ietf.org>; Tue, 13 Nov 2018 04:39:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=TvY3Krr7kR7B65z0QPCTpo0k5unq5ihYjLnsPlIe6JI=; b=b/x3yGf/+n+O4cUY24WwJHoY+T6xtD2qVVqmnHAVftpfmVjBBvKdgl3XXFLbuOtsh4 3jr94xXK8+W1hYi/4jOM3NraLJdPkzknqoMBDHvqB1C/oI62gRfUe/jKl4eNhbrPCxva oSktbqt4PsPzE0ZXiBnE7si37VHEkN/JpZgdMzg6WFBA7C752GPQSn0K6QWNESfN5a28 mGuj0Rm0CX6BIlb+AQoMPHaNozjFhtOObmlzgz95QfU6LmXIwV9fWoqEmYR80+ZXR8+L 1Tvj5fbr956UNvkea7tSpKcx/kO39w5cZf7SHIfc9J25nezpm20CzuL/a4bOPewqCevx O/yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-transfer-encoding:mime-version; bh=TvY3Krr7kR7B65z0QPCTpo0k5unq5ihYjLnsPlIe6JI=; b=kLbDmd0rgBtu7DACgYOv3sYrH7KOiiXgUyqykWYAKwmSTLSlpVSk0/rEtlbhrZGQpe mYXiMLzONQD1ec9m5YxL63gfAHhsrsoSndKGbd667xeCfJ5etL2hiuXVheuGxBDpprPN iwioS7i1hS7iqO/UKZVPqUoVbjunddsJShe8rJKdikGiyY+g0u6sHlg+ZqfWmdd9RsEL gCkIBrKY8m+5hhy2NsulhpTvzLeZPGFFGPRjYkpG615GaimSfr6F84chTUYb4/rmtqCp us6AYGd3tJeCzkMgTflHiVFKs6fOjJ8drYy0ENSnix4l75z0WwXC+aSStHk1QqBMbqgD DWHg==
X-Gm-Message-State: AGRZ1gJO688wavFRbDVELXfT3yBy3gzUqs0Kab+bPqByltA7qSzOkdQC ilTgFoJ+aRUBShGosaL+BjnFSxuK
X-Google-Smtp-Source: AJdET5fm0BLgsFcg8NtVjlDEkVBNdpF3RuMheexI+h81p+P/PuP9sFNx3BK/27rXk3HLKLXXH7uIsA==
X-Received: by 2002:a17:906:5803:: with SMTP id m3-v6mr7077682ejq.33.1542112767282; Tue, 13 Nov 2018 04:39:27 -0800 (PST)
Received: from AM4PR0801MB2738.eurprd08.prod.outlook.com ([40.101.16.141]) by smtp.gmail.com with ESMTPSA id z50sm122764edz.1.2018.11.13.04.39.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Nov 2018 04:39:26 -0800 (PST)
From: Dieter Sibold <dsibold.ietf@gmail.com>
To: Martin Burnicki <martin.burnicki@meinberg.de>
CC: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: [Ntp] Finding leap-seconds.list
Thread-Index: AUZDMzRBN+v/FyhiF38JS+okbuL7RWJiYzUwMDFBQTA0MjU0QWViODQ5NDU3MWI5MTQ5NTBjZTQzYWZmZTKLFXMhGg==
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Tue, 13 Nov 2018 12:39:25 +0000
Message-ID: <AM4PR0801MB2738AE5108E8F2BAFDCCE3FCF8C20@AM4PR0801MB2738.eurprd08.prod.outlook.com>
References: <5884DA3A-B95B-4D6B-9A31-E964CE4F02EF@gmail.com> <53bc1310-c198-557a-54ca-57b5b0af9bcb@meinberg.de> <AM6PR0602MB3733A11C62B7A0ED49F318B5FFC40@AM6PR0602MB3733.eurprd06.prod.outlook.com> <9A89609A-9A4E-41EB-A857-91252E5F6D04@gmail.com> <43c65279-12fa-4510-1d8f-b6e1b03caf7e@gmail.com> <a7d8d58b-7370-1b4c-0c70-fd775dfbf854@cs.ucla.edu> <5f8998a5-d550-95b8-fa46-5e1c1ca7b0e9@meinberg.de> <733a2063-f557-459e-b4e9-0db6c88ab430@ntp.org> <13b61f22-1651-eb22-7af6-6c6cf8031b0a@meinberg.de>
In-Reply-To: <13b61f22-1651-eb22-7af6-6c6cf8031b0a@meinberg.de>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/6Mvpjh09T-pnNk3Y8Wk4w-yMZC4>
Subject: Re: [Ntp] Finding leap-seconds.list
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: Tue, 13 Nov 2018 12:39:31 -0000

Hello Martin,

not speaking as WG chair. 

I want to support Danny's intention. Albeit I appreciate this comprehensive discussion it is obvious that the TZDB is of low relevance for NTP. The discussion about the leap second file is another story. It is most helpful to disseminate leap seconds in a predictable and robust way. However usage and interpretation of the leap second file is not standardized and hence depends on the NTP implementation considered. Taken that probably most of the current NTP clients are not based on ntpd anymore, the failure not to specify how the leap second file is maintained, disseminated, and how it interacts with the leap second information disseminated by upstream servers via the NTP leap second bit is a somewhat unsatisfactory situation.

I also want to mention that the leap second file is in my opinion not a requisite for a fully featured NTP server. You can disseminate a forthcoming leap second event without a leap second file. RFC 5905 does not mandate a leap second file to achieve this.

- Dieter



Am 12.11.18, 09:26 schrieb "Martin Burnicki" <martin.burnicki@meinberg.de>:

    Danny,
    
    Danny Mayer wrote:
    > I have been following this discussion and I'd like to push the reset
    > button. Discussion about the tz database is not just off-topic but is
    > irrelevant to this working group. Many people on this list may be
    > interested but there are other forums for that.
    
    The folks in the NTP WG are discussing how NTP is supposed to work.
    
    The leap second file which is (among other ways) distributed via TZDB is
    an important requisite for a full featured NTP server operation.
    
    Of course there are other platforms to discuss more details, but you
    don't always know who is on which platform.
    
    It's very important that the WG folks at least know that this stuff and
    variants of it exist, so IMO it's perfectly fine to discuss at least
    some basics here.
    
    Martin
    -- 
    Martin Burnicki
    
    Senior Software Engineer
    
    MEINBERG Funkuhren GmbH & Co. KG
    Email: martin.burnicki@meinberg.de
    Phone: +49 5281 9309-414
    Linkedin: https://www.linkedin.com/in/martinburnicki/
    
    Lange Wand 9, 31812 Bad Pyrmont, Germany
    Amtsgericht Hannover 17HRA 100322
    Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg,
    Andre Hartmann, Heiko Gerstung
    Websites: https://www.meinberg.de  https://www.meinbergglobal.com
    Training: https://www.meinberg.academy

v2.23.0 | Report a Bug | By Email