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

Miroslav Lichvar <mlichvar@redhat.com> Tue, 19 October 2021 07:35 UTC

Return-Path: <mlichvar@redhat.com>
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 186F33A0805 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 00:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 MjqH2uCehu6S for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 00:35:25 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (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 1C8113A07F7 for <ntp@ietf.org>; Tue, 19 Oct 2021 00:35:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634628922; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Eio8Z+0l251BiF7K7EyumyN/XVamYZlq/KPTlLxQ9lM=; b=ZLEuQ0oB/jU8NEL5CNV2QBYg7396Nvp99Iyq7yQzXWk49yl9BPHCFNrCSO6Ym9CgcYpyz+ cmWlkDDXBPvSGTGfTFKEY8ROkmvnEwdPu17z2m3yALlEmvNc7dnQKMsLW5ULeDeH2yyMIL olDitXrKx1RPH/CleAzkxTu9i4UDRyc=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-362-ho-a1cEZNxGyNqxwB34M9Q-1; Tue, 19 Oct 2021 03:35:19 -0400
X-MC-Unique: ho-a1cEZNxGyNqxwB34M9Q-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0E69C10A8E00; Tue, 19 Oct 2021 07:35:18 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EFC7869214; Tue, 19 Oct 2021 07:35:15 +0000 (UTC)
Date: Tue, 19 Oct 2021 09:35:07 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: James <james.ietf@gmail.com>, NTP WG <ntp@ietf.org>, Doug Arnold <doug.arnold@meinberg-usa.com>
Message-ID: <YW51K0w2UeOjY3g0@localhost>
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>
MIME-Version: 1.0
In-Reply-To: <C3F52D0C-911B-4084-B4DF-1CF5C80906C7@akamai.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/NXplbpra8oZV67At4-pKmGSVQvY>
Subject: Re: [Ntp] 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 07:35:33 -0000

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?

-- 
Miroslav Lichvar