Re: [Ntp] NTPv5: big picture

Hal Murray <hmurray@megapathdsl.net> Sat, 02 January 2021 06:02 UTC

Return-Path: <hmurray@megapathdsl.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 20EE33A0D50 for <ntp@ietfa.amsl.com>; Fri, 1 Jan 2021 22:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.036
X-Spam-Level: *
X-Spam-Status: No, score=1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, PDS_RDNS_DYNAMIC_FP=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 WQRpE7adLZvT for <ntp@ietfa.amsl.com>; Fri, 1 Jan 2021 22:02:27 -0800 (PST)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id E426A3A0D4B for <ntp@ietf.org>; Fri, 1 Jan 2021 22:02:21 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 6E00D40605C; Fri, 1 Jan 2021 22:02:21 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Magnus Danielson <magnus@rubidium.se>
cc: Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Magnus Danielson <magnus@rubidium.se> of "Fri, 01 Jan 2021 13:29:58 +0100." <e7d72afa-7cff-3158-f930-81d3510100a0@rubidium.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 01 Jan 2021 22:02:21 -0800
Message-Id: <20210102060221.6E00D40605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/IdyDzrDUnO68qjJPCO2OKx443N4>
Subject: Re: [Ntp] NTPv5: big picture
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Sat, 02 Jan 2021 06:02:28 -0000

>> I'd like the basic document not to include the words "leap second", except 
>> possibly for a chunk that says we-don't-do-that, look-over-there.
> I think that might be a mistake, even if I can understand the ambition. I
> think carrying the leap-second difference TAI-UTC is mandatory, and as such,
> the reference to that other document, if indeed handled as separate
> documents, needs to say so. 

I think this is exposing an interesting area we need to work on.

Both TAI-UTC and security have been nominated as requirements.  Yet a TAI 
based protocol makes perfect sense without either.

I think it will be inappropriate to just drop a MUST in the description.  We 
need a way to say that most of today's implementations will need them but 
there are reasonable use cases today and things may change.  I don't want the 
baggage of a MUST to complicate or distort future work.


-- 
These are my opinions.  I hate spam.