IETF Logo Mail Archive

Re: [Ntp] NTPv5 draft

Hal Murray <hmurray@megapathdsl.net> Mon, 07 December 2020 23:03 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 473DC3A0C36 for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 15:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.037
X-Spam-Level: *
X-Spam-Status: No, score=1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, PDS_RDNS_DYNAMIC_FP=0.001, 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 KmFXiw4WNee4 for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 15:03:55 -0800 (PST)
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 589713A0C27 for <ntp@ietf.org>; Mon, 7 Dec 2020 15:03:55 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id C8B7440605C; Mon, 7 Dec 2020 15:03:54 -0800 (PST)
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 "Mon, 07 Dec 2020 22:34:54 GMT." <68F98780-9762-4D1B-885A-EF080F51EEFF@akamai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 07 Dec 2020 15:03:54 -0800
Message-Id: <20201207230354.C8B7440605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/eCETsXvqk5vQWXONddc5rFD67os>
Subject: Re: [Ntp] NTPv5 draft
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: Mon, 07 Dec 2020 23:03:56 -0000

rsalz@akamai.com said:
>>    Assuming you do mean requires, I'll pay a lot more attention to your
>> argument if you outline a plan for getting the existing user base to demand
>> authenticated time.

> NTPv5, a new version of the NTP protocol, will include authenticated servers.
> NTPv5 clients will also be able to detect if server messages were modified
> in-transit.

> NTPv5 is the carrot, or the stick, depending on how you want to look at it. 

Why will NTPv5 be more interesting than NTPv4+NTS which is already available?


-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email