Re: [Ntp] NTS IANA request

Hal Murray <hmurray@megapathdsl.net> Fri, 07 June 2019 10: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 2D86C120110 for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 03:14:37 -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 HrKayGmjekeZ for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 03:14:36 -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 6CD86120071 for <ntp@ietf.org>; Fri, 7 Jun 2019 03:14:35 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id EB1C640605C; Fri, 7 Jun 2019 03:14:34 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Harlan Stenn <stenn@nwtime.org>
cc: ntp@ietf.org, hmurray@megapathdsl.net
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Harlan Stenn <stenn@nwtime.org> of "Thu, 06 Jun 2019 20:24:42 PDT." <0e4e607c-15b6-bb20-5e43-7fadeaf36471@nwtime.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 07 Jun 2019 03:14:34 -0700
Message-Id: <20190607101434.EB1C640605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ROMNK7ga_VXlKSd7btXSrOKAwJg>
Subject: Re: [Ntp] NTS IANA request
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: Fri, 07 Jun 2019 10:14:37 -0000

stenn@nwtime.org said:
> My response was intended to be a technical response.

There is no technical content in "total rubbish". 

> I don't have the time or the desire to refute all of the wrong claims in this
> thread. 

I thought Daniel's message looked good.

If it's "total rubbish", it shouldn't take long to point out some of the problems and/or point out the most obvious fatal flaw.

--------

I have a data point to contribute.

>From Daniel's message:
> As a slight tangent, we never concluded the discussion as to what we're going
> to do about the fact that so many ISPs are dropping 123/udp traffic with
> payloads larger than 48 bytes. I think we got as far as concluding: 

I have 2 cloud servers in the pool, one in San Francisco, the other in London.  As part of the NTS hackathon a month or two ago, they were helping to debug NTS.

There were problems getting NTP+NTS packets to the server in London.  I forget the details.  Nobody seemed surprised.  There was at least one "we've seen it before" comment.


Has anybody done a survey?  Is there a non-NTS packet over 48 bytes that most servers will respond to?

-- 
These are my opinions.  I hate spam.