Re: [calsify] New Timestamp Draft

Ujjwal Sharma <ryzokuken@igalia.com> Fri, 22 January 2021 16:16 UTC

Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781D23A12B9 for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.861
X-Spam-Level:
X-Spam-Status: No, score=-0.861 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, NICE_REPLY_A=-0.262, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
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 sHTJaacBuJQh for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:16:17 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F13EC3A12B7 for <calsify@ietf.org>; Fri, 22 Jan 2021 08:16:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=cJwsORnd7eyDJVejJXLB5DM5c1tiMWEWcrq97SXquk4=; b=HxuPI6ny3MQ8Rutbak9jxFAlfdMnagsXi/jQZRtH5vMMGU7JIr2dwvduSlhPxLdWkfNLFuzsduI1+J/J4zJ51eH0xjm37px+ItqTYuumzI5dZwpeu/2XW6Gdo7LMPHTJZZWOH+iEP44/UFMnGWkH7vZ39b/Y3trcwuCT5xDJJvyedKmRYz7SfJo3m73Yv+BKlqZ8tmMr2dri4i/MXwkKqhxvsikoERElJAAj9HvkaNcvblyiKLSjIIJQ3umnpm83Y/PQEHrCvyh62LujCakke+drfkHcPOi5XfXCSmtEal8dD6MNiH00XYAx4pbBc4tqdUwwnoQu3buDo9clo6QUMw==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l2z6b-00028Y-74; Fri, 22 Jan 2021 17:16:13 +0100
To: Steve Allen <sla@ucolick.org>
Cc: calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
Date: Fri, 22 Jan 2021 21:46:02 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <20210114164646.GA4932@ucolick.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/43a7gJyPb2-GOsO7RMlDWvYrbDA>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 16:16:23 -0000

Hi Steve!

Sorry for taking a while before responding to your emails.

Talking specifically about your concerns:

> This document needs to define the meaning of time using a term other
> than UTC for any date prior to 1960.


and

> Also note that cesium hyperfine frequency ... cesium second

> was not adopted by the SI until 1967 August.

For both of these, I like have to point out that none of these
definitions were added in this update and belong to the original RFC
(RFC 3339). That said, if folks agree that the original RFC incorrectly
defines these terms and they need to be updated, I'd be happy to correct
them in the next revision of the draft.

That said, I would have to point out that my knowledge in this space is
rather limited and therefore it would be best if you recommended exactly
what the replacement should be. To take things further, you could also
make a pull request to the project at
https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
or email me a git patch if you prefer that.

Thanks,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker