IETF Logo Mail Archive

Re: [Ntp] NTPv5: big picture

Hal Murray <hmurray@megapathdsl.net> Tue, 05 January 2021 09:52 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 6A4593A0927 for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 01:52:45 -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 AzitI5rWnIpq for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 01:52:44 -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 CC93A3A08FA for <ntp@ietf.org>; Tue, 5 Jan 2021 01:52:43 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 0703940605C; Tue, 5 Jan 2021 01:52:40 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Miroslav Lichvar <mlichvar@redhat.com>
cc: NTP WG <ntp@ietf.org>, Hal Murray <hmurray@megapathdsl.net>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Miroslav Lichvar <mlichvar@redhat.com> of "Tue, 05 Jan 2021 10:07:53 +0100." <20210105090753.GC3008666@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 05 Jan 2021 01:52:39 -0800
Message-Id: <20210105095240.0703940605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/djwWK2bR-oOV9630lYsSTN9IhUg>
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: Tue, 05 Jan 2021 09:52:45 -0000

mlichvar@redhat.com said:
> NTS-KE is supposed to be used only rarely (clients should save cookies and
> keys), so I don't think it would be a good mechanism for discovery of the
> server's capabilities, even if NTS was required by NTPv5. They can change due
> to an upgrade or reconfiguration without breaking the NTS context (requiring
> new NTS-KE session). 

Agreed.

But given that you have to talk to the KE server before contacting the NTP 
server we should consider taking advantage of that connection.  (The answer 
might be "no".)

I could see additions like "I need a server that supports the xxx time scale." 
or "TAI offset is xxx, next leap at yyy."

I don't know the details of TLS.  Can I change hats without reopening a 
connection??


-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email