[Ntp] Antwort: more comments on Roughtime (draft-11)

kristof.teichel@ptb.de Thu, 05 September 2024 15:42 UTC

Return-Path: <kristof.teichel@ptb.de>
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 5A2A2C14F6E4 for <ntp@ietfa.amsl.com>; Thu, 5 Sep 2024 08:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.629
X-Spam-Level:
X-Spam-Status: No, score=-6.629 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, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ptb.de
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 vekpzNM2GCuZ for <ntp@ietfa.amsl.com>; Thu, 5 Sep 2024 08:42:36 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FE27C16942B for <ntp@ietf.org>; Thu, 5 Sep 2024 08:42:34 -0700 (PDT)
Received: from s23397.bs.ptb.de ([172.21.101.132]) by mx1.bs.ptb.de with ESMTP id 485FgNQ9020353-485FgNQB020353 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Thu, 5 Sep 2024 17:42:23 +0200
MIME-Version: 1.0
Sensitivity:
In-Reply-To: <OF304539A4.FF655D5C-ONC1258B8F.004E086A-C1258B8F.00544DB8@ptb.de>
References: <OF304539A4.FF655D5C-ONC1258B8F.004E086A-C1258B8F.00544DB8@ptb.de>
From: kristof.teichel@ptb.de
To: martin.langer=40ptb.de@dmarc.ietf.org
Message-ID: <OF24B859B4.32CE200C-ONC1258B8F.00563D0B-C1258B8F.005646D7@ptb.de>
X-Priority: 3 (Normal)
Importance: Normal
Date: Thu, 05 Sep 2024 17:42:22 +0200
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-FEAS-Client-IP: 172.21.101.132
X-FE-Policy-ID: 5:5:5:SYSTEM
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=ptb.de; s=s1-ptbde; c=relaxed/relaxed; h=mime-version:references:subject:from:to:cc:message-id:date:content-type; bh=lRH2CHZt2yqgkiH9+eCrcIP95ZbMKIimz07huhAi8zU=; b=YcxAj8h+wYwQhhzcU8XgrTn9tJh9RJXGUlROqyqY9HiFT+TlDQVk/GYv6q4gB2EzHejRGctCna4q Dg2HTFeQHgAhnnWuSW+tKUaPPwEgDmzAYyf/75NAq4MbY88XhDwwBfJj9yQjYEXHPuVwah4Affj0 nBchB4JHGD7XLWmpe/8ZPc4QCwMWeBw1GzOSBKUORYZlw0UgtJF0fIE65d/nW8bHMx96HoodIFCj OvQwPe/kf49LEjp59L+IjsLEBp5DLm8p7pwwT/uH1rbyW3G/sbY+ym7OGDntLPMUfJFCqallKtk1 wvW5lKCaH67rDXXQlnWgW4lfndNxruevISWJgg==
Message-ID-Hash: 4D6NYYSNEO7G5LTGKEN6Q5PNYRDMSDIO
X-Message-ID-Hash: 4D6NYYSNEO7G5LTGKEN6Q5PNYRDMSDIO
X-MailFrom: kristof.teichel@ptb.de
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: watsonbladd@gmail.com, ntp@ietf.org, marcus@dansarie.se
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Antwort: more comments on Roughtime (draft-11)
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ZkJbpll5WnpadV1J0X0vzfR1UYg>
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>

Yeah, I second all of that.


I will say that the intended 'informational' status makes most of our points less pressing (and sorry for being a blockhead about it).
It does, however, make one point even more urgent: the draft/RFC needs to clarify what it is, and what it isn't!
I really want to make sure that no one reads one of those blog posts or papers from before 2020 that laud Roughtime as the Next Big Thing and expects to just run it - or just implement it from this draft in a couple weeks.
If there is no ecosystem yet, and no rules for one either, and the ecosystem is critical for the operation, then let's just clearly state that.

As an almost-aside, the intended informational status means I no longer follow any view of let's-not-be-overly-prescriptive-in-advance.
The document can just describe possible solutions with some "for example..." paragraph and be absolutely okay as an informational RFC, in my opinion.

But the good news is that with this misunderstanding out of the way, we now see a clear way forward, because the RFC doesn't actually need to prove anything, or even solve any specific goals (as long as it doesn't claim to). 

I have begun with adding suggested changes in the Github repo, since this realization really made me feel much easier about just making textual suggestions to fix what I still see as gaps.


Besten Gruß / Kind regards,
Kristof Teichel

__________________________________________

Dr.-Ing. Kurt Kristof Teichel
Physikalisch-Technische Bundesanstalt (PTB)
Arbeitsgruppe 4.42 "Zeitübertragung"
Bundesallee 100
38116 Braunschweig (Germany)
Tel.: +49 531 592-4471
E-Mail: kristof.teichel@ptb.de
__________________________________________


An: watsonbladd@gmail.com
Von: martin.langer=40ptb.de@dmarc.ietf.org
Datum: 05.09.2024 17:23
Kopie: ntp@ietf.org, marcus@dansarie.se
Betreff: [Ntp] more comments on Roughtime (draft-11)

Hey Watson, editors, WG members,

First of all, I'd like to point out that Kristof and I have only recently realized that
the Roughtime draft is intended to be 'informational'. This makes the discussions
much easier from our point of view, as many of our previous criticisms and
comments were based strictly on the assumption that the draft would become
a 'standards track'. We were therefore very eager to get the draft to a high
level of detail, fully describing all the necessary security features and proofs.

Since this is not the case, we feel that it is sufficient to mention ideas and 
concepts in various sections of the draft, but not to describe them in detail.

I have just re-read the current version (draft-11) and added many comments 
that help improve it. I think that if the abstract and the introduction are a bit 
more precise and the comments in the PDF are taken into account, then I will 
not oppose further steps (like the WGLC).

Best regards,
Martin

__________________________________________
Dr.-Ing. Martin Langer
Physikalisch-Technische Bundesanstalt (PTB)
Working Group 4.42 "Dissemination of Time"
Bundesallee 100,
38116 Braunschweig (Germany)
Tel.: +49 531 592-4470
E-Mail: martin.langer@ptb.de
__________________________________________
_______________________________________________
ntp mailing list -- ntp@ietf.org
To unsubscribe send an email to ntp-leave@ietf.org


[Anhang 'draft-ietf-ntp-roughtime-11 - ml.pdf' entfernt von Kristof Teichel/PTB]