IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

Philip Prindeville <philipp@redfish-solutions.com> Thu, 07 January 2021 19:07 UTC

Return-Path: <philipp@redfish-solutions.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 17FCD3A0ADF; Thu, 7 Jan 2021 11:07:01 -0800 (PST)
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 oibgNS5UQz8U; Thu, 7 Jan 2021 11:07:00 -0800 (PST)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [45.33.216.244]) (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 E172E3A0AA7; Thu, 7 Jan 2021 11:06:49 -0800 (PST)
Received: from [192.168.3.4] ([192.168.3.4]) (authenticated bits=0) by mail.redfish-solutions.com (8.16.1/8.16.1) with ESMTPSA id 107J6mtg382333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 7 Jan 2021 12:06:48 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <1e858329-983b-99d0-d3b2-204c6092ff9e@meinberg.de>
Date: Thu, 07 Jan 2021 12:06:48 -0700
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, "ntp@ietf.org" <ntp@ietf.org>, emmanuel.fuste@thalesgroup.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDD03990-1197-4BDA-BBD6-6022943BF6AD@redfish-solutions.com>
References: <20210105124544.5EF5C40605C@ip-64-139-1-69.sjc.megapath.net> <f876a3ff-16ee-fc63-c27c-d5a3cb847a3d@meinberg.de> <4E78BB38-5FA2-4974-AB25-85C5AD9E7DBE@redfish-solutions.com> <8cdc69d3-c795-6fee-3e5c-9ae11694e3da@meinberg.de> <1af7e53f-1251-ea15-dde9-da165c3b5b49@thalesgroup.com> <0af0e655-9f1b-7407-9065-9e3aa7b057d6@meinberg.de> <5FF6C679020000A10003E046@gwsmtp.uni-regensburg.de> <1e858329-983b-99d0-d3b2-204c6092ff9e@meinberg.de>
To: Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/-RkTBw7rC-aj9giZc35SGAIuvbw>
Subject: Re: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
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: Thu, 07 Jan 2021 19:07:01 -0000


> On Jan 7, 2021, at 8:35 AM, Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> wrote:
> 
> Since most systems use UTC or local time derived from it, that is IMO
> what should be in the base packet.


Protocols shouldn’t concern themselves with what “most systems” use.

Are we going to change from big-endian to little-endian when the majority of systems use that?

Or are we continue to say that “we have a canonical format, that is convertible to/from little-endian, and even PDP-endian”?

In the case of network byte order, either one would have been fine and we could have used a coin-toss.

But in the case of timescale, we should go with whatever is the most universally (losslessly) convertible.

v2.23.0 | Report a Bug | By Email