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

John Dowdell <john.dowdell.ietf@gmail.com> Fri, 12 April 2024 09:42 UTC

Return-Path: <john.dowdell.ietf@gmail.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962A3C14F683; Fri, 12 Apr 2024 02:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 z86RSK6NqX2t; Fri, 12 Apr 2024 02:42:17 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 968B1C14F602; Fri, 12 Apr 2024 02:42:17 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-417d029bf15so4767645e9.3; Fri, 12 Apr 2024 02:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712914936; x=1713519736; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=qrSNJ2IQdUiEVaiR9wIx7X/Kjcg+PzI7qebcUZyFJSk=; b=jld8SbrNvsg9F/vLtLa2YosIeCL0diz0jWn91X6ZMWAEg/M8jGj8K/KlW8ZBdlPgBu 0asjf5hXqVT0KUZvQww+PZtR5GPXIp7/8X4iVTGN4z7Lymq4p0guaTgHwoy8rMkHwLza vqndnnGwvnHALaCssMK+8Mb7++p+Wsngy8+9rc88C5sVn7tgVpHD3EycP34nSV1/7RYT wFZyeKPdOi037D71b+5/hUvQWuf2nfie+ZbKgYgSUv8DoeluPX/nrDz6VoIHFVxg5VWW /C1S2PNL6kDag+aEM2/+rrkGCRbJotCF3JW4hDS1dSsW7AEEhoNTJtB0D5QNGKBjIXxE qmSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712914936; x=1713519736; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=qrSNJ2IQdUiEVaiR9wIx7X/Kjcg+PzI7qebcUZyFJSk=; b=qTgsSOjO8BjPkCPeKBQ1Nq69BrC3zYnmDLg5O9Jo6P5iFVpfSb5VB07Yhaj1+HLTNB KQPF/aZQkoC+KfVK2ZrBe+CqYeX92zSJ5r2tBU7Zz0+UN/v60BR06fgK218p+CTLMmf/ djscxAXpWGcwF9Hl01g5JPERhVIO7nmkvEdEmUv0dSJYQ84YFXqE4OlK99b4sWVIo9HQ 1Kgv6G0y1yBbSn3pp6MG0jdjtLthiAmPI6jNWJBYx2XxatcPy95gtxIIbSS/IGbYx/yJ UBJLFnj/jdyK+yJQubMOOkmMX6n06lfguBX62ywYC07Hu1W5rHgltdIXnio9KRW3chdT kkDQ==
X-Forwarded-Encrypted: i=1; AJvYcCXOD3fHHoWaBkXCi1zjGfZiuKuEX0zQ/za04MUyYO0+Wle8JykqbGS1KaMUN3Ueoy6Q0nF43C8nKq2dbCS5f1LJ/30/XyD6yqPtfrU=
X-Gm-Message-State: AOJu0Yy2oSKX6672Do4mHhEe99WtM5SYzGXrNWpw3Ptyu7cyPy5mEoOT O8KKedsfoOSaZySaQHAsiic3kohptqGGr4fMccnvV+v7xXdySlgX
X-Google-Smtp-Source: AGHT+IGZAqy1UeqEKY28HmQ2x8JbNnh1y1oi2qzaMLGXSS+mb+w1Zeo0ndV3jHYzuVU1pwdmSA6f1Q==
X-Received: by 2002:a05:600c:1907:b0:416:b21e:22a8 with SMTP id j7-20020a05600c190700b00416b21e22a8mr1775579wmq.40.1712914935493; Fri, 12 Apr 2024 02:42:15 -0700 (PDT)
Received: from smtpclient.apple (98.38-255-62.static.virginmediabusiness.co.uk. [62.255.38.98]) by smtp.gmail.com with ESMTPSA id z17-20020a05600c0a1100b00416b8da335esm5104693wmp.48.2024.04.12.02.42.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2024 02:42:14 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: John Dowdell <john.dowdell.ietf@gmail.com>
In-Reply-To: <47C6C7B3-E997-4B66-B2D6-372E4726A3AF@tzi.org>
Date: Fri, 12 Apr 2024 10:42:02 +0100
Cc: "Rieber, Richard R (US 347R)" <richard.r.rieber=40jpl.nasa.gov@dmarc.ietf.org>, DTN WG <dtn@ietf.org>, cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <85584DCA-C858-4298-B0F4-555FC42138F1@gmail.com>
References: <PH8PR09MB89262F746957EAA771951CC8F1042@PH8PR09MB8926.namprd09.prod.outlook.com> <47C6C7B3-E997-4B66-B2D6-372E4726A3AF@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/uC9L-Gcjx9QSj1AJxbg2REidXYY>
Subject: Re: [dtn] LTC timescale (Re: Question regarding RFC 9171 - How to incorporate "Coordinated Lunar Time")
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2024 09:42:21 -0000

Hi Carsten and Richard

As a comms engineer working on ESA Moonlight, I’m also interested in resolving this. Given timescales, I guess we’ll end up going with UTC even on the moon, but in the longer term there is a need for a standards-based resolution.

- John

> On 12 Apr 2024, at 06:58, Carsten Bormann <cabo@tzi.org> wrote:
> 
> 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
> 
> 
> _______________________________________________
> dtn mailing list
> dtn@ietf.org
> https://www.ietf.org/mailman/listinfo/dtn