Re: [Ntp] Antw: Re: [EXT] Re: NTPv5 draft suggestion to move timescale offset into extension fields.

David Venhoek <david@venhoek.nl> Tue, 17 January 2023 12:26 UTC

Return-Path: <david@venhoek.nl>
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 98F96C15257C for <ntp@ietfa.amsl.com>; Tue, 17 Jan 2023 04:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venhoek-nl.20210112.gappssmtp.com
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 D-jqFUZo4Mff for <ntp@ietfa.amsl.com>; Tue, 17 Jan 2023 04:26:32 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC431C1524B2 for <ntp@ietf.org>; Tue, 17 Jan 2023 04:26:31 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id 20so17888657pfu.13 for <ntp@ietf.org>; Tue, 17 Jan 2023 04:26:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venhoek-nl.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=w1kvKDowBpqgNW+YlAFFzdf1tiFghj3Iqx9SHAlxYCA=; b=r68GACmhdItY60RwiibbG1LwDATWb3QGfT06L/cpgjOJbvGz+DvxalH+59rm//m2wZ G/FlLV2Fqrt3/lzxlMQtSPVMNYGRydFG7fUU2ZqC/IgiIg3OER+d4zPE/LzRX8RfZYIb IO5CYtv7zYjO2FBo4B0oqyfSi8aqtjA/5j+TnbBC21GvtNmXJCiddfstQGpTFbXeWqbd VPNxXCCfoabkVyfAuGFWYhTVc6pRzPHrHLpQSvmQ4gkBVAtERJeDmiIjLqni0yZOhky1 8pGB2zITHi6DEbAj9Lt4bh9bq2DwjsDqzSiuv2XQHLxFt0LfMIIlZ3sEzPC6ma5U6M3S l5nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=w1kvKDowBpqgNW+YlAFFzdf1tiFghj3Iqx9SHAlxYCA=; b=BKJKmkI46plujnRoNvWIewEN6AsIp1wBcDsFudPJG20QfWPNRIG0xGcIwQ6oFKC+ty zUBeoT/V5u02u1b22hE2rBhZG+EyLpv2zopBKlbVjDZh33X4Cv9rJTUispOoMuTzGHC5 yS/pPPRj6bdey34erFlhx9fe1lPO4jb4TsnWPb2+Sn0ld/yloXV+D+bZVOPeUjjIl/Sq Vl8XJ13pbwwmedct0m6MCzfhnbDTemv6VZHx4CPqCz5Biqb2UcoNpxlS1eRmQnj9+Df+ HV+P3aUs7V/m7bWbcBiZxXrEfyyUNGwN/ySGRhbx7GKNEIThFXoostno2p/i4Yq9zY8L 3YsA==
X-Gm-Message-State: AFqh2kqMriOBay0l+5AdRO7tReB4mZavVT1vUCkd+FwGBJgYO0xuX8VO VyU2Xfp6kRxoZnPtITExrJLauYduAx2oGA3R5hX9lA==
X-Google-Smtp-Source: AMrXdXu+zyZalctBJIECw9tYkOzZpTxj6z4t/jKUg64jJmE/J+7+U7FkhP1HSpV4XJoNM/dsoydjfn0oTB2wylb6mlE=
X-Received: by 2002:a63:5753:0:b0:499:7f08:40c3 with SMTP id h19-20020a635753000000b004997f0840c3mr228300pgm.80.1673958390912; Tue, 17 Jan 2023 04:26:30 -0800 (PST)
MIME-Version: 1.0
References: <CAPz_-SU7rctchBVvm59YAoEA7p8Or9aqdGovJ2E98Tp85jVsWQ@mail.gmail.com> <Y2jCtzeJZfz2daYJ@localhost> <CAPz_-SVkFZaycpimBGy-pZRgwxo9pdnrmh7QDd-=+qvXfdFKRw@mail.gmail.com> <63691D61020000A10004F69D@gwsmtp.uni-regensburg.de> <CAPz_-SWE0UxBoRe6Orr0-t7Mq7z5O-QnyGk+zBNDjDcTd5TxpQ@mail.gmail.com> <Y8UfskkHan7Te8dA@localhost> <CAPz_-SUvMH4DuQzjhFiAGm34v3UE89tb4UqJ=tB63taAK_jLCw@mail.gmail.com> <Y8aA97ioVN6n7/ai@localhost> <63C68CA5020000A10005150D@gwsmtp.uni-regensburg.de>
In-Reply-To: <63C68CA5020000A10005150D@gwsmtp.uni-regensburg.de>
From: David Venhoek <david@venhoek.nl>
Date: Tue, 17 Jan 2023 13:26:38 +0100
Message-ID: <CAPz_-SUwp89zvP-GOxWtG7j2kdLWuLRBELU_dq3Teqkqqed2kw@mail.gmail.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: mlichvar@redhat.com, "ntp@ietf.org" <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/RqP5ivLkbylgvxTesRU-v161V2Q>
Subject: Re: [Ntp] Antw: Re: [EXT] Re: NTPv5 draft suggestion to move timescale offset into extension fields.
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: Tue, 17 Jan 2023 12:26:36 -0000

The problem with TAI (or any other fixed timescale) for all time
exchanges is that this forces every node to know that timescale.
However you then can run into the problem that it is not available to
the system via any route, inhibiting any time exchange.

On Tue, Jan 17, 2023 at 12:55 PM Ulrich Windl
<Ulrich.Windl@rz.uni-regensburg.de> wrote:
>
> >>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 17.01.2023 um 12:05 in
> Nachricht <Y8aA97ioVN6n7/ai@localhost>:
>
> ...
> > What do others think?
>
> Actually I don't know, but it seems we need to support UTC for compatibility with the past; otherwise I'd tend to suggest a radical approach:
> Use TAI for time exchanges only, and insert a "time converter" between the NTP clock model and the host clock model (bi-directional). So one could have any type of local time one would like.
>
> Regards,
> Ulrich
>
> >
> > --
> > Miroslav Lichvar
> >
> > _______________________________________________
> > 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