Re: [Ntp] New rev of the NTP port randomization I-D (Fwd: New Version Notification for draft-gont-ntp-port-randomization-01.txt)

Danny Mayer <mayer@ntp.org> Wed, 29 May 2019 08:48 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 0EB5112010E for <ntp@ietfa.amsl.com>; Wed, 29 May 2019 01:48:35 -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 IoSHiUvoQzoa for <ntp@ietfa.amsl.com>; Wed, 29 May 2019 01:48:33 -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 5E08C120147 for <ntp@ietf.org>; Wed, 29 May 2019 01:48:33 -0700 (PDT)
Received: from [10.10.10.122] (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 45DPWP0VBFzL7W for <ntp@ietf.org>; Wed, 29 May 2019 08:48:32 +0000 (UTC)
From: Danny Mayer <mayer@ntp.org>
To: ntp@ietf.org
References: <E1hVrbd-000Dp4-8Q@elasmtp-kukur.atl.sa.earthlink.net> <c5f6dec6-1086-bd98-59a1-0cd9742d9da5@nwtime.org> <059808b4-b74b-0741-8b62-5a60752195c7@si6networks.com> <835e7b1a-ed19-471c-bbc5-55849ce829bf@nwtime.org> <53d36548-16c3-6f9b-941b-bfb921f19eab@si6networks.com>
Message-ID: <75fcff90-dd60-3b35-564f-3c5c693f5232@ntp.org>
Date: Wed, 29 May 2019 04:48:32 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <53d36548-16c3-6f9b-941b-bfb921f19eab@si6networks.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/9TJEQ0C_mxwff_D3yqPogMYULsI>
Subject: Re: [Ntp] New rev of the NTP port randomization I-D (Fwd: New Version Notification for draft-gont-ntp-port-randomization-01.txt)
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: Wed, 29 May 2019 08:48:35 -0000

On 5/29/19 4:41 AM, Fernando Gont wrote:
> On 29/5/19 04:30, Harlan Stenn wrote:
>> On 5/29/2019 12:07 AM, Fernando Gont wrote:
>>> On 29/5/19 02:06, Harlan Stenn wrote:
>>>> On 5/28/2019 10:58 PM, tglassey@earthlink.net wrote:
>>>>> Yes Harlen if you know you are being attacked the server can set itself
>>>>> as unavailable or untrustable until it recertifies. Information
>>>>> integrity is key for historical auditing of timestamps 
>>>> What about attacks against the client?
>>>>
>>>> Is there benefit to the client knowing it is being attacked?
>>> If you want that, you are free to run a NIDS. You get attack detection,
>>> without leaking the "session ID".
>> Sorry, I'm not buying that.
>>
>> It cost-shifts too much, and it isn't feasible for a number of
>> significant use cases.
> I don't get why you'd want a known port number. You want attack packets
> to hit the session, and count packets for which the org timer fails to
> validate?
>
> If so: what's the point?
>
What session? There is no session in either UDP or NTP. If you think
there is, please tells us where to find it.

Danny