IETF Logo Mail Archive

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

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 18 October 2021 05:55 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 963B03A1187 for <ntp@ietfa.amsl.com>; Sun, 17 Oct 2021 22:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NH9hs4FhFxQa for <ntp@ietfa.amsl.com>; Sun, 17 Oct 2021 22:55:17 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (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 31FE93A11A8 for <ntp@ietf.org>; Sun, 17 Oct 2021 22:55:16 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F3E42600004F for <ntp@ietf.org>; Mon, 18 Oct 2021 07:55:13 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id BE39C600004D for <ntp@ietf.org>; Mon, 18 Oct 2021 07:55:13 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 18 Oct 2021 07:55:13 +0200
Message-Id: <616D0C40020000A100044871@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Mon, 18 Oct 2021 07:55:12 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Rich Salz <rsalz=40akamai.com@dmarc.ietf.org>, james.ietf@gmail.com, doug.arnold@meinberg-usa.com, mayer@pdmconsulting.net
Cc: "ntp@ietf.org" <ntp@ietf.org>
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> <1985d4ff-d4a9-5ca3-e1b8-3d5f9a2fcc4b@pdmconsulting.net> <05E3CA12-9828-4EF6-8C47-20A7D07788AA@akamai.com> <fda9f648-5f63-e33d-6604-42db3a83a073@pdmconsulting.net>
In-Reply-To: <fda9f648-5f63-e33d-6604-42db3a83a073@pdmconsulting.net>
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/-7d0q_mvyhN9n9BelYi78FwXwa8>
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: Mon, 18 Oct 2021 05:55:26 -0000

>>> Danny Mayer <mayer@pdmconsulting.net> schrieb am 15.10.2021 um 19:29 in
Nachricht <fda9f648-5f63-e33d-6604-42db3a83a073@pdmconsulting.net>:

> On 10/15/21 1:03 PM, Salz, Rich wrote:
>> ➢ Encryption needs to be off the table. It's not just a bad idea, it 
> provides no benefits. Time is not a confidential matter. If you have some
use 
> cases for encryption, please state them.
>>
>> I am not so sure it provides no benefits.  We used to think that DNS was a

> public repository and that there were no privacy concerns, and it turns out

> we were wrong.  Sure, time itself is not confidential -- anyone can buy a 
> watch :) -- but the story around the meta-data for time services is not as 
> clear.
>>
> The reason to do encryption is to make the contents confidential so 
> noone else can know what the contents are. There's nothing in the NTP 
> packet that needs to be hidden from prying eyes. The DNS issue is again 
> not a matter of confidentiality. As a former DNS Developer I can tell 
> you that the issue resolved with DNSSEC was to prevent spoofing. The DNS 
> packet is NOT encrypted, it just has content to prevent spoofing. The 
> Kaminsky attack shows an example of that.

Maybe you missed DNSCrypt, DNS-over-Quic (DoQ) and DNS-over-HTTPS
(DoH).

> 
> Danny
> 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp

v2.23.0 | Report a Bug | By Email