Re: [Ntp] NTPv5 modular architecture update
Hal Murray <hmurray@megapathdsl.net> Thu, 23 July 2020 22:14 UTC
Return-Path: <hmurray@megapathdsl.net>
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 968473A0743 for <ntp@ietfa.amsl.com>; Thu, 23 Jul 2020 15:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.036
X-Spam-Level: *
X-Spam-Status: No, score=1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 pT6HWrxgJXEP for <ntp@ietfa.amsl.com>; Thu, 23 Jul 2020 15:14:03 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id A8BDF3A060A for <ntp@ietf.org>; Thu, 23 Jul 2020 15:14:03 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 2BCAF40605C; Thu, 23 Jul 2020 15:14:03 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: "Salz, Rich" <rsalz@akamai.com>
cc: Hal Murray <hmurray@megapathdsl.net>, "ntp@ietf.org" <ntp@ietf.org>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from "Salz, Rich" <rsalz@akamai.com> of "Thu, 23 Jul 2020 21:52:33 -0000." <65A4CB03-4E75-4B39-A43A-B31E5E386017@akamai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 23 Jul 2020 15:14:03 -0700
Message-Id: <20200723221403.2BCAF40605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/PbeCDrZ4YpXMbYGKIXPTKzVAid8>
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 22:14:05 -0000
rsalz@akamai.com said: > One argument against it is that client code probably needs to know how long > the decryption took, to correct for it. Decryption is not the problem - you get the time stamp before you even look at the packet. Encryption would be a problem. Same for the transmit side of NTS and shared-key authentication. -- These are my opinions. I hate spam.
- [Ntp] NTPv5 modular architecture update Doug Arnold
- Re: [Ntp] NTPv5 modular architecture update Dieter Sibold
- Re: [Ntp] NTPv5 modular architecture update Danny Mayer
- Re: [Ntp] NTPv5 modular architecture update Hal Murray
- Re: [Ntp] NTPv5 modular architecture update Salz, Rich
- Re: [Ntp] NTPv5 modular architecture update Hal Murray
- [Ntp] Antw: [EXT] Re: NTPv5 modular architecture … Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: NTPv5 modular architect… Hal Murray