[Cbor] LTC timescale (Re: [dtn] Question regarding RFC 9171 - How to incorporate "Coordinated Lunar Time")

Carsten Bormann <cabo@tzi.org> Fri, 12 April 2024 05:58 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 72DAEC14F689; Thu, 11 Apr 2024 22:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 9ktv2dr_zXJw; Thu, 11 Apr 2024 22:58:42 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 6BC9AC14F686; Thu, 11 Apr 2024 22:58:39 -0700 (PDT)
Received: from smtpclient.apple (p5089a101.dip0.t-ipconnect.de [80.137.161.1]) (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 4VG5Tl1xMxzDCgB; Fri, 12 Apr 2024 07:58:35 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <PH8PR09MB89262F746957EAA771951CC8F1042@PH8PR09MB8926.namprd09.prod.outlook.com>
Date: Fri, 12 Apr 2024 07:58:24 +0200
Cc: "dtn@ietf.org" <dtn@ietf.org>, cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <47C6C7B3-E997-4B66-B2D6-372E4726A3AF@tzi.org>
References: <PH8PR09MB89262F746957EAA771951CC8F1042@PH8PR09MB8926.namprd09.prod.outlook.com>
To: "Rieber, Richard R (US 347R)" <richard.r.rieber=40jpl.nasa.gov@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/XRvArG_9LsumNs0I7BlDCiXmLm4>
Subject: [Cbor] LTC timescale (Re: [dtn] Question regarding RFC 9171 - How to incorporate "Coordinated Lunar Time")
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: Fri, 12 Apr 2024 05:58:46 -0000

Hi Richard,

I read your message with interest.

draft-ietf-cbor-time-tag [1], an approved specification that is currently in the RFC editor queue for publication as an RFC, defines a versatile representation of timestamps in CBOR.
While DTN BP does not directly use this extended time tag currently, I would imagine that any evolution of its time representations would coordinate to maintain interoperability with the extended time tag.

[1]: https://datatracker.ietf.org/doc/draft-ietf-cbor-time-tag/

The extended time tag defines a way to indicate the timescale in use [2].
This is based on a IANA registry [3] that is currently just listing UTC and TAI [4].

[2]: https://www.ietf.org/archive/id/draft-ietf-cbor-time-tag-12.html#section-3.4
[3]: https://www.ietf.org/archive/id/draft-ietf-cbor-time-tag-12.html#section-7.2
[4]: https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml#timescales

I would expect that LTC should be added to this registry, and that a short specification could provide information about how this is to be used and how this timescale interoperates with the existing ones.

Grüße, Carsten


> On 12. Apr 2024, at 06:46, Rieber, Richard R (US 347R) <richard.r.rieber=40jpl.nasa.gov@dmarc.ietf.org> wrote:
> 
> Hello DTN leads,
>  I am a DTN advocate at JPL and working as the Mission Operations Systems Engineer on the CADRE mission. This mission is slated to send 3 shoe-box sized rovers to the moon on Intuitive Machine’s IM-3 lander in Q1 2025. Needless to say, I’m paying attention to all things moon-related and DTN-related.
>  There are two things I want to highlight:
>     • NASA’s SCaN office has released the LunaNet Interoperability specification, which mandates the use of DTN for communications in Feb. 2023, and
>     • On 4/2/2024, the White House has tasked NASA with developing a “Coordinated Lunar Time”, amongst other planetary time systems.
>  BP’s DTN Time (see 4.2.6 of RFC-9171) is defined as milliseconds since 2000-001T00:00:00 UTC. How should this change if there is a lunar time system?
>  I would imagine that Lunar spacecraft use LTC for their internal clocks. How do they interpret bundles sent from Earth that are stamped with UTC? Must they internally convert the current LTC to UTC to compare to that bundle’s DTN Time? Similarly, what time system is used in the DTN Time field for bundles created by a lunar spacecraft?
>  Now imagine the Artemis Gateway that may act as a communication relay node. Some bundles would be from Earth and tagged with UTC. Some bundles would be from the moon and may be tagged in LTC. This gets quite confusing.
>  Needless to say, I think the DTN community needs to have a conversation about if and how the protocol must be modified to support different time systems across the solar system. What’s the venue for having that conversation? How would one go about proposing a protocol modification?
>  Thanks in advance,
> ~Rich
>    Richard Rieber
> NASA/JPL
> Robotics Systems Engineer
> 347R – Robotics Operations and V&V
> Richard.R.Rieber@jpl.nasa.gov
> +1-818-480-2861
> _______________________________________________
> dtn mailing list
> dtn@ietf.org
> https://www.ietf.org/mailman/listinfo/dtn