[Ntp] Antw: [EXT] Draft rechartering text for NTP working group

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 26 July 2021 07:50 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 1AC7A3A1F9E for <ntp@ietfa.amsl.com>; Mon, 26 Jul 2021 00:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vO4BelmByE-h for <ntp@ietfa.amsl.com>; Mon, 26 Jul 2021 00:50:39 -0700 (PDT)
Received: from mx4.uni-regensburg.de (mx4.uni-regensburg.de []) (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 780C83A1FA3 for <ntp@ietf.org>; Mon, 26 Jul 2021 00:50:39 -0700 (PDT)
Received: from mx4.uni-regensburg.de (localhost []) by localhost (Postfix) with SMTP id D7B646000065 for <ntp@ietf.org>; Mon, 26 Jul 2021 09:50:33 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de []) by mx4.uni-regensburg.de (Postfix) with ESMTP id E496A6000060 for <ntp@ietf.org>; Mon, 26 Jul 2021 09:50:25 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 26 Jul 2021 09:50:25 +0200
Message-Id: <60FE693F020000A100042AA6@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Mon, 26 Jul 2021 09:50:23 +0200
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>,<odonoghue@isoc.org>
References: <CO6PR06MB70583CA81F4F4415EE3815BCC2E69@CO6PR06MB7058.namprd06.prod.outlook.com>
In-Reply-To: <CO6PR06MB70583CA81F4F4415EE3815BCC2E69@CO6PR06MB7058.namprd06.prod.outlook.com>
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/enW675184nCBkkYkW977IQAikDg>
Subject: [Ntp] Antw: [EXT] Draft rechartering text for NTP working group
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: Mon, 26 Jul 2021 07:50:44 -0000

Sounds good IMHO.

>>> Karen O'Donoghue <odonoghue@isoc.org> schrieb am 24.07.2021 um 14:50 in

> Below is draft text for the rechartering of the NTP working group. Please 
> review and comment. This will be on the agenda for next week’s meeting.
> Regards,
> Karen and Dieter
> Good quality time is a key component of all modern systems, devices, and 
> applications. This quality time requires reliable and accurate network time

> synchronization over modern IP‑based networks.  The Network Time Protocols 
> working group is focused on enhancing existing network time synchronizsation

> protocols, such as the Network Time Protocol (NTP), and specifing new
> time related protocols or extensions for purposes which the existing 
> protocols are not well suited to address.
> NTP was first defined in the IETF in RFC 958 in 1985. It has been through 
> several iterations in the IETF. The latest, NTPv4 (RFC 5905) was published
> 2010.  Today it is the most widely used time synchronization protocol for
> synchronization of clocks of various digital systems including computers, 
> networks, and a myriad of devices. Despite NTP's wide‑spread success it has

> become apparent that it needs further development in order to adequately
> the modern requirements of time synchronization protocols and to meet the 
> increasing security threats of the Internet.
> The working group will continue to to address the maintenance of NTPv4 
> including extensions and corrections. This includes the introduction of a 
> interleave mode in order to enhance the accuracy of the network time 
> synchronization and the introduction of alternative selection algorithms in

> order to enhance robustness against delay attacks.
> Despite its increasing importance, NTP remains vulnerable to many types of 

> attacks. Therefore, in 2020 the working group published Network Time
> (NTS) as RFC 8915. NTS extends NTP with an authentication approach to ensure

> authenticity of NTP time servers and protects the integrity of exchanged NTP

> packets. The working group will work on extending NTS to cover the remaining

> modes of service for NTP not covered by the initial version. The working 
> group will also work on extending NTS for PTP(1) in collaboration with the 
> IEEE 1588 working group.
> The working group shall also develop an updated version of NTP (preliminarly

> known as NTPv5) addressing a number of identified weaknesses. The new 
> specification shall comprise of a set of documents, in order to distinguish

> between the on‑wire protocol engine and the timing engine of NTP clients and

> servers.  The updated version of NTP will address the security requirements

> specified in RFC 7384 and leverage the work completed in RFC 8915.
> Finally, the working group, will address other network time related 
> protocols in the IETF (e.g. Roughtime).
> (1) PTP is the Precision Time Protocol as defined by the IEEE 1588. The 
> latest version is IEEE 1588‑2019 ‑ IEEE Standard for a Precision Clock 
> Synchronization Protocol for Networked Measurement and Control Systems.