[Ntp] RoughTime running-code - Re: [ripe-list] RIPE NCC Community Projects Fund Recipients 2023
Michael Richardson <mcr+ietf@sandelman.ca> Sat, 04 November 2023 05:57 UTC
Return-Path: <mcr+ietf@sandelman.ca>
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 A5C45C1B0311; Fri, 3 Nov 2023 22:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 wxoFz1loXByV; Fri, 3 Nov 2023 22:56:58 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 709DBC17A743; Fri, 3 Nov 2023 22:56:55 -0700 (PDT)
Received: from dyas.sandelman.ca (dynamic-046-114-090-024.46.114.pool.telefonica.de [46.114.90.24]) by relay.sandelman.ca (Postfix) with ESMTPS id 255CF20B44; Sat, 4 Nov 2023 05:56:54 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 1DD7DA1B53; Sat, 4 Nov 2023 01:56:07 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 1AB4EA1361; Sat, 4 Nov 2023 06:56:07 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iotops@ietf.org, ntp@ietf.org
CC: draft-ietf-ntp-roughtime@ietf.org
In-reply-to: <BF3F6457-3073-4C10-8BCF-3C9C0056EFC8@ripe.net>
References: <BF3F6457-3073-4C10-8BCF-3C9C0056EFC8@ripe.net>
Comments: In-reply-to projectsfund@ripe.net message dated "Fri, 03 Nov 2023 12:25:58 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 04 Nov 2023 06:56:07 +0100
Message-ID: <3414172.1699077367@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/YQol8cmUgmmqQTgUmWqHKA8W67U>
Subject: [Ntp] RoughTime running-code - Re: [ripe-list] RIPE NCC Community Projects Fund Recipients 2023
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: Sat, 04 Nov 2023 05:57:02 -0000
projectsfund@ripe.net wrote: > Netnod AB - Secure time for IoT devices: developing the > Roughtime proposed standard > Read more about these projects: > https://www.ripe.net/support/cpf/funding-recipients-2023 Always cool to see running-code: draft-ietf-ntp-roughtime-08 I believe that there has been some controversy about how much traffic RoughTime might actually cause to NTP servers, and I have wondered how this might be reconciled with challenged networks. (I'm not on ntp@. It was not my intention to re-litigate things) I'm hoping that the Netnod people will come to IOTOPS in the future and tell us more about their experiments. The writeup from the RIPE site, which did not include contact info: Netnod AB Recognizing the essential role of time synchronisation in internet security and the shortcomings of existing protocols for IoT devices, this project aims to advance the Roughtime proposed standard. By reigniting efforts to develop an IETF standard for Roughtime, the project aspires to provide a quick and secure method for time synchronisation on IoT devices, addressing the security vulnerabilities inherent in widely deployed protocols like the Network Time Protocol (NTP) and Network Time Security (NTS). Netnod will spearhead this initiative, leveraging expertise from previous successful Roughtime projects and leading the IETF work on the recent NTS Proposed Standard. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS*
- [Ntp] RoughTime running-code - Re: [ripe-list] RI… Michael Richardson