[Ntp] Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 19 October 2021 09:31 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 728293A096D for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 02:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 Sj-GqLZMXAw7 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 02:31:40 -0700 (PDT)
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 9AE913A0964 for <ntp@ietf.org>; Tue, 19 Oct 2021 02:31:40 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 37F996000054 for <ntp@ietf.org>; Tue, 19 Oct 2021 11:31:37 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 22FE8600004D for <ntp@ietf.org>; Tue, 19 Oct 2021 11:31:37 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 19 Oct 2021 11:31:36 +0200
Message-Id: <616E9077020000A10004494F@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Tue, 19 Oct 2021 11:31:35 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Rich Salz <rsalz@akamai.com>, mlichvar@redhat.com
Cc: james.ietf@gmail.com, "ntp@ietf.org" <ntp@ietf.org>, doug.arnold@meinberg-usa.com
References: <163386015957.12424.6997038478834885480@ietfa.amsl.com> <CAO+dDx=6baLhf9LwSMvR1F0ieuLO6NXmExYLDvcCF2tgchHs8w@mail.gmail.com> <DB8PR02MB5772AC97BFE2D7C1139EFDC0CFB89@DB8PR02MB5772.eurprd02.prod.outlook.com> <E469D9A7-7445-49D9-A8A2-82BA7BF1FA27@gmail.com> <YW2FvUiaHC/hbxkG@localhost> <C953CCDB-8338-4CD8-BFB2-7DC1F880B341@gmail.com> <C3F52D0C-911B-4084-B4DF-1CF5C80906C7@akamai.com> <YW51K0w2UeOjY3g0@localhost>
In-Reply-To: <YW51K0w2UeOjY3g0@localhost>
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/ixftjDRRUx21EU_5KqQtgxibE-c>
Subject: [Ntp] Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
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: Tue, 19 Oct 2021 09:31:46 -0000

>>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 19.10.2021 um 09:35 in
Nachricht <YW51K0w2UeOjY3g0@localhost>:
> On Mon, Oct 18, 2021 at 04:50:52PM +0000, Salz, Rich wrote:
>>     > For NTPv5 to be successful in replacing NTPv4, I think it needs to
>>     > support no authentication, symmetric keys and NTS.
>> 
>> NTPv4 and NTS are not going to go away in the next few years.  I see no 
> reason why NTPv5 has to support them, other than coexist.  It's more like 
> IPv4 and IPv6 than it is like TLS 1.0/1.1 and TLS 1.2/1.3 in my view.
> 
> I think it's the latter. NTPv4 has a number of issues that were
> identified and need to be fixed. That's the reason why I wrote my
> draft. But now it seems there are people trying to turn NTP into
> something else, with different ideas how an ideal protocol for time
> synchronization should look like, but making it less practical, not
> covering the common NTPv4 use cases.
> 
> Would it make sense to put this effort on a separate path and call it
> NTPv6 or something else?

I think we are still in the discussion phase, not in the implementation
phase.
Let's make a "good version", not a "quick version".

> 
> ‑‑ 
> Miroslav Lichvar
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp