IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 07 January 2021 08:17 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 5E35B3A09B7 for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 00:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 EXx7e35CUudW for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 00:16:58 -0800 (PST)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BA053A09B5 for <ntp@ietf.org>; Thu, 7 Jan 2021 00:16:58 -0800 (PST)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A81CF6000050 for <ntp@ietf.org>; Thu, 7 Jan 2021 09:16:55 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 8C10F600004D for <ntp@ietf.org>; Thu, 7 Jan 2021 09:16:55 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 07 Jan 2021 09:16:55 +0100
Message-Id: <5FF6C375020000A10003E02F@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Thu, 07 Jan 2021 09:16:53 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "philipp@redfish-solutions.com" <philipp@redfish-solutions.com>, magnus@rubidium.se
Cc: "ntp@ietf.org" <ntp@ietf.org>, mlichvar@redhat.com
References: <20210102081603.1F63C40605C@ip-64-139-1-69.sjc.megapath.net> <cecaf661-92af-8b35-4c53-2f025c928144@rubidium.se> <20210104164449.GE2992437@localhost> <b1e61f7d-6cea-5e99-69f0-7eae815d9e19@rubidium.se> <20210105083328.GA3008666@localhost> <ba5d2cde-6b5e-d9b6-1877-c4060bf43e80@rubidium.se> <20210105144225.GH3008666@localhost> <35c4be55-b6af-82b5-aacd-d5a591383dec@rubidium.se> <63ED96A2-7296-4389-AFB2-0597A514623B@redfish-solutions.com> <307609DF020000627ED719BE@gwsmtp.uni-regensburg.de> <BC392A58020000606A6A8CFC@gwsmtp.uni-regensburg.de> <6F8C195D020000117ED719BE@gwsmtp.uni-regensburg.de> <1C9DBBA8020000BAD2E74B8B@gwsmtp.uni-regensburg.de>
In-Reply-To: <1C9DBBA8020000BAD2E74B8B@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/7Za_CJRPRU0S8iCi7pTF9wBtJBM>
Subject: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was 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: Thu, 07 Jan 2021 08:17:01 -0000

>>> Philip Prindeville <philipp@redfish-solutions.com> schrieb am 06.01.2021
um
04:59 in Nachricht
<63ED96A2-7296-4389-AFB2-0597A514623B@redfish-solutions.com>:

> 
>> On Jan 5, 2021, at 8:51 AM, Magnus Danielson <magnus@rubidium.se> wrote:
>> 
>> You could use DNS based methods.
> 
> 
> I want to quash this approach.
> 
> DNS has means to attempt some form of weak security, but a lot of people 
> don’t do it or don’t do it properly.
> 
> This will be a weakness in time, plus it introduces circular dependencies 
> since DNS records are themselves timestamped for expiration (TTL’s), though

> that’s an offset from now and not an absolute time…
> 
> We already bloat DNS with too much, such as RSA keys and SPF… we’re 
> attempting to use it as a distributed clearinghouse database, which it was 
> never meant to be.

But compared to LDAP it's still "light-weight".

> 
> Oh, for the love of Grapevine.
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp

v2.23.0 | Report a Bug | By Email