[Ntp] Mail regarding draft-ietf-ntp-nts-keyexchange-pool: style question
"Windl, Ulrich" <u.windl@ukr.de> Tue, 18 August 2026 04:54 UTC
Return-Path: <prvs=6837f831f=u.windl@ukr.de>
X-Original-To: ntp@mail2.ietf.org
Delivered-To: ntp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E5F4112B63594 for <ntp@mail2.ietf.org>; Mon, 17 Aug 2026 21:54:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787028898; bh=96LZqkOVDqQmbKSK6l9/gaMoJh9wzB7TqutHQRJ42Rk=; h=From:To:Subject:Date; b=K1+9CmdWMkU832PYprfZy8l+jhPby4r7whkywEDI6bbJ6OKIoU+scZI+tdnF/Yrj2 SpDEnREy10jGTwrhBXR0i4mx308MGnVpAR6JStb0ucE65U/JYb7LBE/P5pEe4peS6h XzjqotrsQsIyh5yY6YHPrx+GyJDOwQ0FpYn1uczk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=ukr.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IaaJP90JAHz5 for <ntp@mail2.ietf.org>; Mon, 17 Aug 2026 21:54:58 -0700 (PDT)
Received: from mail01.ukr.de (mail01.ukr.de [193.175.194.181]) (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 mail2.ietf.org (Postfix) with ESMTPS id 25A8312B63589 for <ntp@ietf.org>; Mon, 17 Aug 2026 21:54:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ukr.de; i=@ukr.de; q=dns/txt; s=ukr; t=1787028898; x=1818564898; h=from:to:subject:date:message-id:mime-version; bh=96LZqkOVDqQmbKSK6l9/gaMoJh9wzB7TqutHQRJ42Rk=; b=PyjEBTzgffw3TYLnQ0FT+nTNKw68rzO5FHFN6Oa9eEWvroDaFhkBTS7w 40Q7UOS+b7Z6A3sz1a1wmNv6jjUfD5hXqI7VsiRUCN04ot+R9TOb8BQ99 2aVDxbl7IOtlpb3XAwPQLO/aI19/FpJBsFtMz6IGGnr7uHd/nBuKKzX9s joskuA9IUhbiReQ7TzrvIqhqveywdeoOEPad6gg1+LbQkfkk3VDjHXFnr 15onuxYduOyCkaleqWAWyAt4B7W/STS/V8S0MRm9gsXdJYV7kzJ+PZqFB aMJgnWZCS13oxEGQ8Vh4pcE9yUrsZ4VOUAPtZ5CnCLbh9Y+m1NpciJNT5 Q==;
X-CSE-ConnectionGUID: voblVDoST5e+vRUkQ3P9GA==
X-CSE-MsgGUID: i7c9l/pVTuSiWWvArIHeWw==
X-ThreatScanner-Verdict: Negative
X-IronPort-AV: E=McAfee;i="6800,10657,11878"; a="10757172"
X-IronPort-AV: E=Sophos;i="6.25,230,1779141600"; d="scan'208,217";a="10757172"
Received: from unknown (HELO ukr.de) ([172.24.2.105]) by dmz-infcsg01.ukr.dmz with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Aug 2026 06:54:57 +0200
Received: from ukr-excmb07.ukr.local (172.24.2.107) by ukr-excmb05.ukr.local (172.24.2.105) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.46; Tue, 18 Aug 2026 06:54:56 +0200
Received: from ukr-excmb07.ukr.local ([fe80::4dee:3e0b:b33f:60ac]) by ukr-excmb07.ukr.local ([fe80::4dee:3e0b:b33f:60ac%8]) with mapi id 15.02.2562.046; Tue, 18 Aug 2026 06:54:56 +0200
From: "Windl, Ulrich" <u.windl@ukr.de>
To: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: Mail regarding draft-ietf-ntp-nts-keyexchange-pool: style question
Thread-Index: Ad0uzQg0F7sYWcuzRJ65X3m38PTPaw==
Date: Tue, 18 Aug 2026 04:54:56 +0000
Message-ID: <0a89cc3fe1b54f5eb4f070d732cc47b2@ukr.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.3.2]
x-tm-snts-smtp: 876E017B9A99134557F162AE4F967EFB25CAC3A50EB1E52E66B0216F5E8E500A2000:8
Content-Type: multipart/alternative; boundary="_000_0a89cc3fe1b54f5eb4f070d732cc47b2ukrde_"
MIME-Version: 1.0
Message-ID-Hash: QXSVFPBNZW3GS2NLBR5D3UEJN3L7GUO5
X-Message-ID-Hash: QXSVFPBNZW3GS2NLBR5D3UEJN3L7GUO5
X-MailFrom: prvs=6837f831f=u.windl@ukr.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ntp] Mail regarding draft-ietf-ntp-nts-keyexchange-pool: style question
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/MyGT6H9uciWdqcLB2dI7UAg6eOI>
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>
Hi! I don’t know if some style guide exists on this, but I wonder: Shouldn’t some “key terms” be emphasized in plain text even? For example consider: The Supported Next Protocol List (Section 6.2), Supported Algorithm List (Section 6.3) and List Server Names (Section 6.4) records allow the pool to ask a time source which protocols and algorithms it supports, … in contrast (my proposal): The “Supported Next Protocol List” (Section 6.2), “Supported Algorithm List” (Section 6.3) and “List Server Names” (Section 6.4) records allow the pool to ask a time source which protocols and algorithms it supports, … I see that there is capitalization for the phrases, but I still wonder if that’s good enough; maybe let a screen reader read that to you… Kind regards, Ulrich Windl
- [Ntp] Mail regarding draft-ietf-ntp-nts-keyexchan… Windl, Ulrich