IETF Logo Mail Archive

Re: [Ntp] NTS IANA request

Danny Mayer <mayer@ntp.org> Fri, 07 June 2019 14:31 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 736CD12016E for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 07:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01] 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 nTf9dBByvOM7 for <ntp@ietfa.amsl.com>; Fri, 7 Jun 2019 07:31:09 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C08A12008A for <ntp@ietf.org>; Fri, 7 Jun 2019 07:31:09 -0700 (PDT)
Received: from L34097OUS.local (pool-71-174-223-53.bstnma.east.verizon.net [71.174.223.53]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 45L4hW119qzL7N for <ntp@ietf.org>; Fri, 7 Jun 2019 14:31:07 +0000 (UTC)
To: ntp@ietf.org
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>
From: Danny Mayer <mayer@ntp.org>
Message-ID: <de0c6296-7152-044a-5613-dfdc8d924c2f@ntp.org>
Date: Fri, 07 Jun 2019 10:31:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CAJm83bBkU91st1CFAsx+JCLpxXyWOQnSTY9sXeuA96R8pqXdCA@mail.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/58ceFW7kNqoMP740_Wc7csBVEwU>
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 14:31:17 -0000

On 6/6/19 2:28 PM, Daniel Franke wrote:
> 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:
>
> 1. We're never going to persuade enough ISPs to change their policy,
> making 123/udp basically doomed.
> 2. NTS-KE's port negotiation record gives us all the mechanism we need
> in order to run NTP-with-NTS over an alternate port.

We do what we did for EDNS0, get the firewall folks to change their
policies to allow for larger payloads. It will takes years but firewall
people have to move with changes as they happen.

Danny

v2.23.0 | Report a Bug | By Email