[Cbor] MJD ➔ 60000
Carsten Bormann <cabo@tzi.org> Mon, 20 February 2023 21:56 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DECF6C14F748; Mon, 20 Feb 2023 13:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.697
X-Spam-Level:
X-Spam-Status: No, score=-3.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=0.5, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbPw0LS6Y5_5; Mon, 20 Feb 2023 13:56:27 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08402C14E511; Mon, 20 Feb 2023 13:56:26 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4PLGTL5ZMSzDCcW; Mon, 20 Feb 2023 22:56:22 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 20 Feb 2023 22:56:22 +0100
Cc: ntp@ietf.org
X-Mao-Original-Outgoing-Id: 698622982.338395-a1746cb97ebefb55a15303867d779909
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AB2FE7D-0928-42A0-87ED-E7AB2D1BBF3B@tzi.org>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/h1cP7PfC8NNh8_npBNQ6xYBGJ0c>
Subject: [Cbor] MJD ➔ 60000
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2023 21:56:32 -0000
While we are looking ahead to a rather sobering anniversary this week, it may be interesting to take note of another anniversary, or really zeroing of digits: MJD 60000 = 2023-02-25T00:00:00Z (Saturday in Europe, still Friday in the US.) We discussed MJD (Modified Julian Date [1]) briefly when completing RFC 8943 [2]. I still marvel at how Sputnik and the 18-bit halfword of the IBM 704 shaped this now quite widely used date/time format. Most users of MJD haven’t seen any MJD that didn’t start with a 5 (or 4, if they are old enough), so brace for some software breakage when the first digit turns 6... We now return you to less geeky subjects… Grüße, Carsten [1]: https://en.wikipedia.org/wiki/Julian_day#Variants Chrome-only link: https://en.wikipedia.org/wiki/Julian_day#:~:text=The%20Modified,2400000.5 [2]: https://www.rfc-editor.org/rfc/rfc8943#section-1-3 (It will take another 587 days until we reach date-tag 20000 on 2024-10-04.)
- [Cbor] MJD ➔ 60000 Carsten Bormann