[Ntp] Antw: [EXT] I‑D Action: draft‑ietf‑ntp‑chronos‑03.txt

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 23 August 2021 07:47 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 BCC443A0B6B; Mon, 23 Aug 2021 00:47:04 -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 kWNGb3000zyd; Mon, 23 Aug 2021 00:46:58 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.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 A42B23A0B67; Mon, 23 Aug 2021 00:46:56 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost []) by localhost (Postfix) with SMTP id AC104600004F; Mon, 23 Aug 2021 09:46:52 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de []) by mx3.uni-regensburg.de (Postfix) with ESMTP id C288C600004D; Mon, 23 Aug 2021 09:46:48 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 23 Aug 2021 09:46:48 +0200
Message-Id: <61235267020000A100043657@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Mon, 23 Aug 2021 09:46:47 +0200
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <i-d-announce@ietf.org>
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <162957269575.27856.15768575668621490186@ietfa.amsl.com>
In-Reply-To: <162957269575.27856.15768575668621490186@ietfa.amsl.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/40eTLGzPrC43ogylBv8N9bKxXQc>
Subject: [Ntp] =?utf-8?b?QW50dzogW0VYVF0gIEnigJFEIEFjdGlvbjogZHJhZnTigJFp?= =?utf-8?b?ZXRm4oCRbnRw4oCRY2hyb25vc+KAkTAzLnR4dA==?=
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, 23 Aug 2021 07:47:05 -0000


I wonder: Shouldn't "chronos" be included in the RFC title, like "Chronos, a
secure Selection and ..."?
And if the title isn't too long alrerady, what about also including "(NTP)" 
after "etwork Time Protocol"?

I mean: If some user searches RFCs by title, what will help to make the search
results more relevant?

Ulrich Windl

>>> <internet-drafts@ietf.org> schrieb am 21.08.2021 um 21:04 in Nachricht

> A New Internet‑Draft is available from the on‑line Internet‑Drafts
> This draft is a work item of the Network Time Protocol WG of the IETF.
>         Title           : A Secure Selection and Filtering Mechanism for the

> Network Time Protocol
>         Authors         : Neta Rozen‑Schiff
>                           Danny Dolev
>                           Tal Mizrahi
>                           Michael Schapira
> 	Filename        : draft‑ietf‑ntp‑chronos‑03.txt
> 	Pages           : 11
> 	Date            : 2021‑08‑21
> Abstract:
>    The Network Time Protocol version 4 (NTPv4), as defined in RFC 5905,
>    is the mechanism used by NTP clients to synchronize with NTP servers
>    across the Internet.  This document specifies an extension to the
>    NTPv4 client, named Chronos, which is used as a "watchdog" alongside
>    NTPv4, and provides improved security against time shifting attacks.
>    Chronos involves changes to the NTP client's system process only and
>    is backwards compatible with NTPv4 servers.  Chronos is also
>    applicable to the emerging NTPv5, since it does not affect the wire
>    protocol.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑chronos/ 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft‑ietf‑ntp‑chronos‑03 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft‑ietf‑ntp‑chronos‑03 
> Internet‑Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet‑drafts/ 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp