IETF Logo Mail Archive

Re: [Ntp] NTPv5 modular architecture update

Danny Mayer <mayer@ntp.org> Thu, 23 July 2020 21:26 UTC

Return-Path: <mayer@ntp.org>
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 7DF043A0E04 for <ntp@ietfa.amsl.com>; Thu, 23 Jul 2020 14:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.164
X-Spam-Level:
X-Spam-Status: No, score=0.164 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, NICE_REPLY_A=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 mbqrs4IruNXq for <ntp@ietfa.amsl.com>; Thu, 23 Jul 2020 14:26:46 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (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 9CC503A0D66 for <ntp@ietf.org>; Thu, 23 Jul 2020 14:26:46 -0700 (PDT)
Received: from l34097ous.rpega.com (unknown [198.22.153.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4BCQPw0N41zL7f for <ntp@ietf.org>; Thu, 23 Jul 2020 21:26:43 +0000 (UTC)
To: ntp@ietf.org
References: <DB8PR02MB5481C1EBE9C74F1EFD2E5372CF760@DB8PR02MB5481.eurprd02.prod.outlook.com> <64189FBD-C5F7-496E-9373-8ACE0EB8969E@gmail.com>
From: Danny Mayer <mayer@ntp.org>
X-Pep-Version: 2.0
Message-ID: <ff1dce38-c395-9265-2b59-e4b2ae1d557c@ntp.org>
Date: Thu, 23 Jul 2020 17:26:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <64189FBD-C5F7-496E-9373-8ACE0EB8969E@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/rrH6RxaArOUBp0qUmCvemW1MPps>
Subject: Re: [Ntp] NTPv5 modular architecture update
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Thu, 23 Jul 2020 21:26:50 -0000

On 7/23/20 5:02 PM, Dieter Sibold wrote:

> 3. Security
>
> Security should be the default. I would even propose to encrypt the
> timing packets per default.
>
What are you trying to hide and why? There is no reason at all that I
can tell to encrypt a timing packet. Securing a packet only requires
that it has not been tampered with between sending and receiving.

Danny

v2.23.0 | Report a Bug | By Email