IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt

Hal Murray <halmurray+ietf@sonic.net> Tue, 19 October 2021 10:59 UTC

Return-Path: <halmurray+ietf@sonic.net>
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 40E333A0B18 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 03:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWfrLmYkQ8ie for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 03:59:53 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F03C3A096F for <ntp@ietf.org>; Tue, 19 Oct 2021 03:59:15 -0700 (PDT)
Received: from 107-137-68-211.lightspeed.sntcca.sbcglobal.net (107-137-68-211.lightspeed.sntcca.sbcglobal.net [107.137.68.211]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id 19JAxEek012368 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 19 Oct 2021 03:59:14 -0700
Received: from hgm (localhost [IPv6:::1]) by 107-137-68-211.lightspeed.sntcca.sbcglobal.net (Postfix) with ESMTP id 294F728C0F3; Tue, 19 Oct 2021 03:59:14 -0700 (PDT)
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1
To: Miroslav Lichvar <mlichvar@redhat.com>
cc: "ntp@ietf.org" <ntp@ietf.org>, Hal Murray <halmurray+ietf@sonic.net>
From: Hal Murray <halmurray+ietf@sonic.net>
In-Reply-To: Message from Miroslav Lichvar <mlichvar@redhat.com> of "Tue, 19 Oct 2021 11:54:00 +0200." <YW6VuMQ1/qUhxnh+@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 19 Oct 2021 03:59:14 -0700
Message-Id: <20211019105914.294F728C0F3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Sonic-CAuth: UmFuZG9tSVY5zsZUmS6cvY6Nzcuk+k3gCp/8KEh5iLXOe8lZOKEhJWyw7plWaQTXUMpc9v6Di5RBUzibdCsgcEz5mrB+ePFfjia6aBrJcTQ=
X-Sonic-ID: C;MkfvmMsw7BGYEyx66Nu5DA== M;7Ikfmcsw7BGYEyx66Nu5DA==
X-Sonic-Spam-Details: -1.5/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/EdVH1WJWQleos9Q9yUNvIDUDY64>
Subject: Re: [Ntp] Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Oct 2021 10:59:54 -0000

mlichvar@redhat.com said:
> One of the requirements for NTPv5 should be that it can be properly
> implemented on current versions of all major systems, i.e. TAI cannot be the
> only supported timescale. 

Depends on what you mean by "supported".

I think we should split things into two parts.

The time used in time-transfer should be TAI to keep things clean.  No leap.  
No smear.

We need something else to cover conversion from TAI to leaping UTC and/or 
smearing UTC.  That info doesn't change very often.  I'd like to see it in a 
separate packet or maybe even a separate RFC.

The client does the conversion.  That means the client has to know if it is 
leaping or smearing.  But it needs that anyway if it is going to ask for leap 
or smear.

We could put all the authentication in a 3rd RFC.



-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email