[Ntp] Antw: [EXT] Re: Mirja Kühlewind's Discuss on draft-ietf-ntp-using-nts-for-ntp-24: (with DISCUSS and COMMENT)

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 20 March 2020 07:13 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 39AB03A0A56; Fri, 20 Mar 2020 00:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 vkOL1gl0E4KW; Fri, 20 Mar 2020 00:13:39 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FEF33A0A39; Fri, 20 Mar 2020 00:13:32 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5AB5D600004D; Fri, 20 Mar 2020 08:13:12 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 391C56000049; Fri, 20 Mar 2020 08:13:12 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 20 Mar 2020 08:13:12 +0100
Message-Id: <5E746D06020000A100037E45@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.1
Date: Fri, 20 Mar 2020 08:13:10 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: stenn@nwtime.org
Cc: draft-ietf-ntp-using-nts-for-ntp@ietf.org, The IESG <iesg@ietf.org>, "ntp@ietf.org" <ntp@ietf.org>, odonoghue@isoc.org
References: <20200320044743.AC9DA40605C@ip-64-139-1-69.sjc.megapath.net> <31041_1584680845_5E744F8D_31041_97_1_ced12651-75fb-d5ee-3ea6-95a1e1a6aaaf@nwtime.org>
In-Reply-To: <31041_1584680845_5E744F8D_31041_97_1_ced12651-75fb-d5ee-3ea6-95a1e1a6aaaf@nwtime.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/IG2qxS889srrgg3mubt7hpZalvk>
Subject: [Ntp] Antw: [EXT] Re: Mirja Kühlewind's Discuss on draft-ietf-ntp-using-nts-for-ntp-24: (with DISCUSS and COMMENT)
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, 20 Mar 2020 07:13:42 -0000

Hi Harlan,

it's obvious that you want to keep port 123/TCP reserved for NTP. However
there were no projects in the last 20 years that would have wanted that port.
Aslo Dave Mills once said NTP over TCP does not make sense at all, and the
whole protocol design is incompatible with it. So at best the stil-to-be-done
NTP v5 could use that port.

Sorry I did not attend the meetings you are referring to, but still from time
to time you could repeat the facts instead of referring to them.

Regards,
Ulrich

>>> Harlan Stenn <stenn@nwtime.org> schrieb am 20.03.2020 um 06:06 in
Nachricht
<31041_1584680845_5E744F8D_31041_97_1_ced12651-75fb-d5ee-3ea6-95a1e1a6aaaf@nwtim
.org>:

> 
> On 3/19/2020 9:47 PM, Hal Murray wrote:
>> 
>> stenn@nwtime.org said:
>>> The NTP Project has sent its plans for TCP/123 to the working group, to
be
>>> used by "NTP TCP Services".  We intend this to be used for a variety of
>>> NTP‑related TCP services.  That is a work in progress.  Otherwise, the
NTP
>>> Project remains strongly opposed to using TCP/123 for NTS‑KE because of
<good
>>> reasons we have stated before to the WG, and I want to save everybody the
>>> drama so I won't go in to them now>. 
>> 
>> Your "good reasons" would carry more weight in my view if you would provide

> a 
>> reference to your ideas.
> 
> Hal, I'm pretty sure you at least virtually attended the meetings where
> this was discussed.
> 
> I've also posted various emails about it.
> 
>> Google found 2 drafts from 2018.  The total useful content was 2 paragraphs

>> with few details.  Maybe I didn't search for the right thing.  The first 
> said 
>> TCP and STARTTLS.  The second said key exchange.  In my opinion, both have

>> been superseded by NTS‑KE.
>> 
>> Are there other ideas I didn't find?
>> 
>> I think it would be a good idea to move ntpq operations to a secure
channel. 
>  
>> NTS‑KE uses ALPN.  Is there any reason not to take advantage of ALPN so we

> can 
>> share port 123 with future ideas?
> 
> Please look at what I have said before.
> 
> ‑‑ 
> Harlan Stenn <stenn@nwtime.org>
> http://networktimefoundation.org ‑ be a member!
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp