Re: [calsify] New Timestamp Draft
Ujjwal Sharma <ryzokuken@igalia.com> Fri, 22 January 2021 21:08 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 108ED3A0A1C for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:08:55 -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 DIl_-oqdCF9W for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:08:53 -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 2C7633A14FE for <calsify@ietf.org>; Fri, 22 Jan 2021 13:08:52 -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=RBkExbl+dEnbcIGpEEnUs4nc2Bjav9myks9gPBDNivI=; b=DFKvLjIdbmtLJws3/uVUia1B6EjfT4d+FguG8VPN9m0sUw8rWGz8WwkL4onEPWfB0rWdkFv3JktpBXuMx7aYQKRlkfvv42DFd4aBsrDaGzDY9KE3KDrSjwn+e9UqvOgtJWWY6Y/WT+TuLTpRw876tGmRw/GcvD5O8BrE73xtLGXfMLWmRoVSUE1Xf1wryo64rlxtVjnUOf1HYgneS6gLimhDd6a1T+LrKQCBmeH/y6sMDSqkSt0gC2sichUIw/xVT9OHg1hs+xHMsQKlV/hfoU7t8yzWbrMA4zG71d5QTtVpuyjWZIy8ZFdmK+NGqnLaYRxQfho9p1T1fTcWrDbhrg==;
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 1l33fl-0006it-4a; Fri, 22 Jan 2021 22:08:49 +0100
To: Eliot Lear <lear@cisco.com>
Cc: Steve Allen <sla@ucolick.org>, 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> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com> <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <4c9b5edf-93fb-d211-ff41-f7ecc4d5b8ab@igalia.com>
Date: Sat, 23 Jan 2021 02:38:36 +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: <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/-YgpHVbP34F_VQUnayZQwoN_AkQ>
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 21:08:55 -0000
Hey Elliot! I answered a couple of these questions in a previous CalExt meeting, but here goes another attempt at getting them out in writing: On 22/01/2021 10.09 pm, Eliot Lear wrote: > RFC 3339 or ISO 8601 is used all over the place. It’s used in logging, email, and a great many other things. Before the IETF goes monkeying with it, could the authors discuss what is driving this change? What do you want people to do that they didn’t do before, and what do you want them to stop doing, and why? There are many cases in which the information stored within a timestamp is not enough and implementations need to include additional information for various reasons. It is common knowledge that Java and Linux among other implementations include an IANA timezone id suffixed to the regular timestamp, but I think of it as an unfortunate situation that this format is not standardized. The aim of this proposal is to: 1. Standardize the existing format. 2. Expand the format to include more information (in case of us, ECMA TC39, this includes the calendar information which is the biggest reason that drives us to expand the currently existing format). 3. Make the expansions generalizable enough to allow any additional future information to be included. 4. Make certain parts of the RFC further future-proof, for example remove the 2/3-year deprecated format and allow the expanded 6-year format, which makes this RFC up to date with the newer versions of ISO8601. > Also, I suggest that this work should go through DISPATCH. There are a lot of other questions. Here’s one: is the IETF really the right organization to do this work in? ISO wrote the underlying spec. They presumably thought about it a lot. We are already collaborating with the folks over at CalConnect, to ensure that formats like ISO8601 end up adopting these additions as well, but the IETF RFC would need to be updated as well, and it helps ECMA TC39 refer to the RFC when using this format. I hope these answers help clarify our positions. Feel free to ask me for any further clarifications. Thanks, Ujjwal -- Ujjwal "Ryzokuken" Sharma (he/him) Compilers Hacker, Node.js Core Collaborator and Speaker
- [calsify] New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Steve Allen
- Re: [calsify] New Timestamp Draft Steve Allen
- Re: [calsify] New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Bron Gondwana
- Re: [calsify] New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Bron Gondwana
- Re: [calsify] New Timestamp Draft Steve Allen
- Re: [calsify] New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Eliot Lear
- Re: [calsify] New Timestamp Draft Ned Freed
- Re: [calsify] New Timestamp Draft Ujjwal Sharma
- [calsify] Fwd: New Timestamp Draft Ujjwal Sharma
- Re: [calsify] New Timestamp Draft Shane Carr
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] Fwd: New Timestamp Draft Michael Douglass
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] New Timestamp Draft Bron Gondwana
- Re: [calsify] Fwd: New Timestamp Draft Bron Gondwana
- Re: [calsify] New Timestamp Draft Steve Allen
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] Fwd: New Timestamp Draft Bron Gondwana
- Re: [calsify] New Timestamp Draft Eliot Lear
- Re: [calsify] New Timestamp Draft Bron Gondwana
- Re: [calsify] New Timestamp Draft Eliot Lear
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] Fwd: New Timestamp Draft Bron Gondwana
- Re: [calsify] Fwd: New Timestamp Draft Neil Jenkins
- Re: [calsify] Fwd: New Timestamp Draft Ned Freed
- Re: [calsify] Fwd: New Timestamp Draft Shane Carr
- Re: [calsify] New Timestamp Draft Eliot Lear
- Re: [calsify] New Timestamp Draft Barry Leiba
- Re: [calsify] New Timestamp Draft Shane Carr
- Re: [calsify] New Timestamp Draft Eliot Lear
- Re: [calsify] New Timestamp Draft Shane Carr
- Re: [calsify] New Timestamp Draft Alexey Melnikov