Re: [Ntp] [EXT] I-D Action: draft-ietf-ntp-ntpv5-requirements-04.txt

Paul Gear <ntp@libertysys.com.au> Mon, 18 March 2024 04:15 UTC

Return-Path: <ntp@libertysys.com.au>
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 E5235C14F6F1 for <ntp@ietfa.amsl.com>; Sun, 17 Mar 2024 21:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=libertysys.com.au
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 3tMBzg4mxJU9 for <ntp@ietfa.amsl.com>; Sun, 17 Mar 2024 21:15:11 -0700 (PDT)
Received: from mail.libertysys.com.au (2001-44b8-2100-3f00-0000-0000-0000-0019.static.ipv6.internode.on.net [IPv6:2001:44b8:2100:3f00::19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 C6B98C14F6E1 for <ntp@ietf.org>; Sun, 17 Mar 2024 21:15:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.libertysys.com.au (Postfix) with ESMTP id 80AED3001D1 for <ntp@ietf.org>; Mon, 18 Mar 2024 14:15:05 +1000 (AEST)
X-Virus-Scanned: Debian amavis at mail.libertysys.com.au
Received: from mail.libertysys.com.au ([150.101.186.52]) by localhost (mail.libertysys.com.au [127.0.0.1]) (amavis, port 10024) with ESMTP id 4kZu5QmPWOCK for <ntp@ietf.org>; Mon, 18 Mar 2024 14:15:01 +1000 (AEST)
Authentication-Results: mail.libertysys.com.au; dmarc=fail (p=quarantine dis=none) header.from=libertysys.com.au
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=libertysys.com.au; s=2016; t=1710735293; bh=rK7euVux6xm/wn4fsu8YXc14LKUDDUBHg01vynXygcE=; h=Date:Subject:To:References:From:In-Reply-To:From; b=WDmBlJbQ1buNcivnlam+6KlhPoZabGLGzaiZKS+bhyJfiiPpjPUsuICL6mEBG1Wms FhvUpeNuW63qzGICrSOE4iL/iVIqUZwEVMnFVRFF/aYd/xNWguopPWx9Lt6KUOyiZG NKGKgfVoVmV1xI1joN+TF3UNxFPt6QsDMeMlRBVo=
Received: from [IPV6:2001:67c:370:128:be65:d730:a166:ea5a] (unknown [IPv6:2001:67c:370:128:be65:d730:a166:ea5a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.libertysys.com.au (Postfix) with ESMTPSA id 10DF9316D8C for <ntp@ietf.org>; Mon, 18 Mar 2024 14:14:53 +1000 (AEST)
Message-ID: <3cc4002a-e41e-4697-a9de-64db77d11944@libertysys.com.au>
Date: Mon, 18 Mar 2024 14:14:51 +1000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-AU
To: ntp@ietf.org
References: <170620320947.44305.3312905112123700132@ietfa.amsl.com> <bc89de0cdeb5486da5a762cf59afd914@ukr.de>
From: Paul Gear <ntp@libertysys.com.au>
In-Reply-To: <bc89de0cdeb5486da5a762cf59afd914@ukr.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/4lXzAOe5tsBMt_ATlWto3Kn09rs>
Subject: Re: [Ntp] [EXT] I-D Action: draft-ietf-ntp-ntpv5-requirements-04.txt
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: Mon, 18 Mar 2024 04:15:15 -0000

I've created a pull request to address some of the feedback from 
Ulrich.  It can be viewed at:

https://github.com/fiestajetsam/draft-gruessing-ntp-ntpv5-requirements/pull/43/files

I have not attempted to address every point Ulrich raised, nor have I 
incorporated wording changes where I deemed that they did not improve 
the original.  In my opinion, one think which Ulrich raised is important 
to address in future updates, which is adding references or explanatory 
text to justify the choice to allow server identifiers to change over 
time.  Possibly adding references to explain leap second events in NTP 
might be useful as well.

I have added my own wording adjustments in some cases where I thought 
Ulrich's points were good but the wording could be further improved.  
James, please feel free to adjust as you see fit.

On 27/2/24 17:43, Windl, Ulrich wrote:
> Hi!
>
> Most likely not the format in which contributions are expected, but I commented on the TXT representation, creating a PDF from the ODT document.
> So in case you cannot work with the ODT, you could use the PDF. The ODT was created with LibreOffice Writer, but MS-Word seems to open it as well.
>
> Kind regards,
> Ulrich
>
> -----Original Message-----
> From: ntp <ntp-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, January 25, 2024 6:20 PM
> To: i-d-announce@ietf.org
> Cc: ntp@ietf.org
> Subject: [EXT] [Ntp] I-D Action: draft-ietf-ntp-ntpv5-requirements-04.txt
>
> Internet-Draft draft-ietf-ntp-ntpv5-requirements-04.txt is now available. It
> is a work item of the Network Time Protocols (NTP) WG of the IETF.
>
>     Title:   NTPv5 Use Cases and Requirements
>     Author:  James Gruessing
>     Name:    draft-ietf-ntp-ntpv5-requirements-04.txt
>     Pages:   11
>     Dates:   2024-01-25
>
> Abstract:
>
>     This document describes the use cases, requirements, and
>     considerations that should be factored in the design of a successor
>     protocol to supersede version 4 of the NTP protocol presently
>     referred to as NTP version 5 ("NTPv5").  It aims to define what
>     capabilities and requirements such a protocol possesses, informing
>     the design of the protocol in addition to capturing any working group
>     consensus made in development.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5-requirements/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ntp-ntpv5-requirements-04.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ntp-ntpv5-requirements-04
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> 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