[Ntp] Re: [NTP] Roughtime: Inadequate Explanation of Protocol's Unique Feature? (Question to all WG members)

Watson Ladd <watsonbladd@gmail.com> Tue, 03 September 2024 16:02 UTC

Return-Path: <watsonbladd@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 90F5DC14F700 for <ntp@ietfa.amsl.com>; Tue, 3 Sep 2024 09:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpZdzFyI5_rT for <ntp@ietfa.amsl.com>; Tue, 3 Sep 2024 09:02:56 -0700 (PDT)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 247DBC1D4A86 for <ntp@ietf.org>; Tue, 3 Sep 2024 09:02:56 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id 5b1f17b1804b1-42bbd16fcf2so38245335e9.2 for <ntp@ietf.org>; Tue, 03 Sep 2024 09:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725379374; x=1725984174; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=313DnI4r6fPnTPz8smOGLPIsiNZ73nEzo3yW+RAOrzg=; b=CgoUKh+Th3ihEFxya8hUc+dgbxr5fqSupkYAnH7e4KsQAnhETokj65blkT+D4lyel6 D5trrpc2+l72WZv6xYWL0+4aef2/U3EDEtL67Of85PeeKPAQlqVhtI2Uf89s/7wkMOdc gw8d8J7g/9FblCIhgSCAJrDjdGnsFwDqwI011frMtbbb3SY8O5oDoA4k4lVbRv4ZUauB Tg4C1gS1dge99WzOW4xq6latPb0VjwPiFzua+HypcVChY5EuF1503/4kpI3NwAsvyq0T VNPzuiDLEL1TDt/DQ6SAasY2J8IATqHaLNIS+5ddq/bDcyAd1CIttOGGn/+DdugIBwfE WE5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725379374; x=1725984174; h=content-transfer-encoding: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=313DnI4r6fPnTPz8smOGLPIsiNZ73nEzo3yW+RAOrzg=; b=CRXDw1dyTbQF+FFFYBG0Tjcu+tl5DNFW5aPImsqSKK818aTCMlj2luEGMR5Rl7gRoT vg7hlCqvfDex1ON4xGcfhmj//p1Mo0wdJUtekqcPevqoS3AXGAX7vSzzgyLIWK7ld0kV jcWGtZFspCWYhSCsY++joDwPLfTnQu15T9Hy48qJa4bpOMRVkRitqUvKffl6vOBlPbDU 2niHCuMiqRIQMrgTjwT8/d2aoVqAlaPjXjfiBadjEckU/CCPzxUYWhNDdBrYePKkS7sG kOQA7uS5L/doe3zxRNlXFc91sjjRI3ioY2qpg7Vje0zgyiJJz0oaxUECy4okk3cBXpo9 rdKA==
X-Gm-Message-State: AOJu0YxZ8xlKmDmEMMefFs0yEOgSgDJii2DWsFbnr3sIqVgWXR4xjs08 3U8SvZmTN3CGvvpq4T4NriqdcEXJ6Su6ms0ggqWGJr0z+zpTMjH7ID/8KVlP/wgzf89OZo5ydQ5 IQcaRSRJbaVGTjAeqR8Eq4QAGYH0=
X-Google-Smtp-Source: AGHT+IEkk7aE8ZJT43TDkSLu/Nvtq+zdjYl19VwDlfjiU4dmWPlV+b7LHD8+vaVAazHJr/Xdvn1RKUVl8jBBUP75N9A=
X-Received: by 2002:adf:f34b:0:b0:374:ca16:e09b with SMTP id ffacd0b85a97d-374ca16e226mr4871465f8f.9.1725379373002; Tue, 03 Sep 2024 09:02:53 -0700 (PDT)
MIME-Version: 1.0
References: <CACsn0c=EE1XfdqPSXUBBRNxCx-q-kujRvfYt8y_HpWKKhNkY=Q@mail.gmail.com> <OF2CFF35FC.75A6A341-ONC1258B78.0038739B-C1258B78.00390D28@ptb.de> <CACsn0c=K0dHULBVvXB+Hhd+S6TB8PDsEB68DiLR+t8gpfzP_GQ@mail.gmail.com> <OF8A6D8203.9F157312-ONC1258B8D.002DDF63-C1258B8D.002F5442@ptb.de>
In-Reply-To: <OF8A6D8203.9F157312-ONC1258B8D.002DDF63-C1258B8D.002F5442@ptb.de>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Tue, 03 Sep 2024 09:02:40 -0700
Message-ID: <CACsn0ckTqUVWhOQm+ZFaV1s_ftuyUaG1f_Ot=hi+4uQDZ8Dqtg@mail.gmail.com>
To: kristof.teichel@ptb.de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: 6TYDVQBGHOQQ4GUHGUWPKAGQUNEXI62A
X-Message-ID-Hash: 6TYDVQBGHOQQ4GUHGUWPKAGQUNEXI62A
X-MailFrom: watsonbladd@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: NTP WG <ntp@ietf.org>, Marcus Dansarie <marcus@dansarie.se>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: [NTP] Roughtime: Inadequate Explanation of Protocol's Unique Feature? (Question to all WG members)
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/uacsNM7VyLnz0c86ZF7af47--QY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>

On Tue, Sep 3, 2024 at 1:37 AM <kristof.teichel@ptb.de> wrote:
>
> @watson/ben: thanks for your replies
> Can the information about the ecosystem and reporting system be found anywhere else?
> Not necessarily about a server list or who runs them, but about how the logic works, how reporting should roughly be done, etc.?

First let me say I very much appreciate the effort you are spending on
improving the draft. It's very easy for me as author to think I have
explained things well when I have not. I think what I have in the
draft is there but is fairly telegraphic. A client queries multiple
servers, and through the chaining mechanism can determine if they give
inconsistent results (Section 4 and 9.2). When there is an
inconsistency the client reports, and we have a format for doing that
(might need more explication). When the client reports, and what
happens after is currently beyond scope.

I'm not sure what logic you are discussing. We certainly can put in
more examples and explanations of how having three causally related
measurements can impeach a server giving the incorrect time.
Ultimately though distrust comes about through human understanding of
which one was wrong.

> (If so, could you link to that?)
> Or are you saying it's okay for this to not be documented anywhere?

Part of the problem is that we do not have any such program operating
to describe, and being very prescriptive about things that don't yet
exist is a losing battle.

>
> Let's remember that this is Roughtime's supposed core technical feature.

I think roughtime has this feature and it's just a matter of
documentation. But we can't dictate the human bits come into
existence: they either will or will not, and will operate according to
their needs. Mozilla has a very different root program than Apple.

Sincerely,
Watson Ladd

>
> @ntp-wg: I was really looking for input on this from people who didn't have an active role in developing Roughtime.
> I ask you all again to provide a short opinion, please.

Yes, please chime in!

>
>
> Besten Gruß / Kind regards,
> Kristof Teichel
> (and Martin Langer)



-- 
Astra mortemque praestare gradatim