IETF Logo Mail Archive

Re: [Ntp] NTS IANA request

"Gary E. Miller" <gem@rellim.com> Wed, 05 June 2019 23:48 UTC

Return-Path: <gem@rellim.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 E2B46120142 for <ntp@ietfa.amsl.com>; Wed, 5 Jun 2019 16:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level:
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4ikD9EGQhsyF for <ntp@ietfa.amsl.com>; Wed, 5 Jun 2019 16:48:26 -0700 (PDT)
Received: from rellim.com (spidey.rellim.com [204.17.205.8]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EC21120121 for <ntp@ietf.org>; Wed, 5 Jun 2019 16:48:26 -0700 (PDT)
Received: from localhost (spidey.rellim.com [204.17.205.8]) by rellim.com (Postfix) with ESMTPSA id C2E932025D0 for <ntp@ietf.org>; Wed, 5 Jun 2019 16:48:24 -0700 (PDT)
Date: Wed, 05 Jun 2019 16:48:13 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: ntp@ietf.org
Message-ID: <20190605164753.6e71fcaa@rellim.com>
In-Reply-To: <a123d81b-4994-9e35-58eb-6845cf439f91@nwtime.org>
References: <CAN2QdAH9Uh_wYSEizgYTjd4Q6VFQT+tvH8dnbPgKKc59+vEfng@mail.gmail.com> <a123d81b-4994-9e35-58eb-6845cf439f91@nwtime.org>
Organization: Rellim
X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; boundary="Sig_/TQu.Zr6N.DLE0aAPXVlPrV8"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/zlpU4FQI7zO0roHBUJrSvO49Yn0>
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: Wed, 05 Jun 2019 23:48:28 -0000

Yo Harlan!

On Wed, 5 Jun 2019 15:21:10 -0700
Harlan Stenn <stenn@nwtime.org> wrote:

> > We could also use 123 tcp which is assigned to NTP but not used.  
> 
> No.  The "NTP TCP Services" proposal is expecting to use TCP/123.

What services would they be?  Could some adjustments be made to make
NTP/TCP and NTS commpatible?

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin

v2.23.0 | Report a Bug | By Email