IETF Logo Mail Archive

Re: [Ntp] NTS IANA request

"Majdi S. Abbas" <msa@latt.net> Fri, 07 June 2019 20:55 UTC

Return-Path: <msa@latt.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 4A2DE12026F for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 13:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 O9PYfhx_u_Rk for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 13:55:05 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2B76120298 for <ntp@ietf.org>; Fri, 7 Jun 2019 13:55:05 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 504) id 28632540ADA; Fri, 7 Jun 2019 16:55:05 -0400 (EDT)
Date: Fri, 07 Jun 2019 16:55:05 -0400
From: "Majdi S. Abbas" <msa@latt.net>
To: Daniel Franke <dfoxfranke@gmail.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "ntp@ietf.org" <ntp@ietf.org>, "Gary E. Miller" <gem@rellim.com>
Message-ID: <20190607205505.GA27315@puck.nether.net>
References: <CAN2QdAH9Uh_wYSEizgYTjd4Q6VFQT+tvH8dnbPgKKc59+vEfng@mail.gmail.com> <a123d81b-4994-9e35-58eb-6845cf439f91@nwtime.org> <20190605164753.6e71fcaa@rellim.com> <03055E77-EB42-494E-A231-039C4603E256@akamai.com> <CAJm83bDYZ+vcwkhFEf2YCAVwKcSm7rEgbuB0Wwsvm5XVVAMjuQ@mail.gmail.com> <C8E4189E-E3A1-4926-AF0F-93BE9C7255C8@akamai.com> <CAJm83bBkU91st1CFAsx+JCLpxXyWOQnSTY9sXeuA96R8pqXdCA@mail.gmail.com> <20190607200832.GA19127@puck.nether.net> <CAJm83bCrdrKh+D8ytdd7DfnyV8HbN7vmiqCm7tgC9LAoEGowaw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAJm83bCrdrKh+D8ytdd7DfnyV8HbN7vmiqCm7tgC9LAoEGowaw@mail.gmail.com>
X-Message-Flag: Follow up
User-Agent: Mutt/1.11.4 (2019-03-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/_KFJcLv1mqfl_kRdrLfZlAvk5Ik>
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 20:55:18 -0000

On Fri, Jun 07, 2019 at 04:32:11PM -0400, Daniel Franke wrote:
> It's been ours. We've encountered such filtering issues in all three
> NTS hackathons. At any rate, as Watson said, data is coming. We should
> rely on that rather than anecdotes.

	Sure, but if you can tell me which providers/networks are
involved, I'd be happy to have a chat with them.

> This isn't an issue of system ports (< 1024) vs. user ports, it's an
> issue of a single IANA-registered port vs. everyone who runs a server
> being told to choose their own (and advertise it via NTS-KE port
> negotiation). In the latter case it becomes both harder to block if
> you have a default-allow policy like an ISP would, and harder to allow
> if you have a default-deny policy like a corporate firewall would.

	Well, so far we've already had one assertion that NTS
"needs" a privileged port on this list -- it may not have been yours,
but that was the assertion I was replying to.

	Thanks!

	--msa

v2.23.0 | Report a Bug | By Email