IETF Logo Mail Archive

Re: [Ntp] I-D Action: draft-ietf-ntp-using-nts-for-ntp-26.txt

Miroslav Lichvar <mlichvar@redhat.com> Mon, 23 March 2020 08:52 UTC

Return-Path: <mlichvar@redhat.com>
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 4D69A3A0938 for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 01:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 74LEvlczPI4L for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 01:52:51 -0700 (PDT)
Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [63.128.21.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EACDB3A0937 for <ntp@ietf.org>; Mon, 23 Mar 2020 01:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1584953564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SlE55ZiSfLgos+dy0HA83HUKA5HS+65JbyOBGvnAzho=; b=D3RjRPL0dAyZBV5kwpiTgjMEh2NJeSunRgR/d2ncdlrGL8Nsb89+nqe+ilMw+/0o5UMtaI pBRebCkRrXA5QBa4njzAom+HtPbXMyiiiwhjg2dNJgP/Cr0vAv+UiHR+03PrOrmJp/TQv4 vTYnAqSyzyBvrv5JeikGqnpIFu4mBbs=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-258-0g6J-DZXMU-hT6iIRSQT3w-1; Mon, 23 Mar 2020 04:52:42 -0400
X-MC-Unique: 0g6J-DZXMU-hT6iIRSQT3w-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 07C31192605F for <ntp@ietf.org>; Mon, 23 Mar 2020 08:50:16 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7E3649B921 for <ntp@ietf.org>; Mon, 23 Mar 2020 08:50:15 +0000 (UTC)
Date: Mon, 23 Mar 2020 09:50:12 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: ntp@ietf.org
Message-ID: <20200323085012.GG28883@localhost>
References: <mlichvar@redhat.com> <20200323081913.GF28883@localhost> <20200323083703.57E9D40605C@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
In-Reply-To: <20200323083703.57E9D40605C@ip-64-139-1-69.sjc.megapath.net>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/IypT_1p33YPy_zPyL1XRVrpwkSc>
Subject: Re: [Ntp] I-D Action: draft-ietf-ntp-using-nts-for-ntp-26.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: Mon, 23 Mar 2020 08:52:53 -0000

On Mon, Mar 23, 2020 at 01:37:03AM -0700, Hal Murray wrote:
> mlichvar@redhat.com said:
> > If there is a flag day, I'd prefer if it was the same as for the NTS-KE port.
> 
> We don't need a flag day for the port.  The server can easily listen to both 
> old and new.

It could, but I suspect more people would use the old port in future
than now due to obsolete documentation or configuration examples
coming up in search results, and closing the port later would actually
cause more problems. I'm not planning to support the old port.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email