Re: [dispatch] Proposed charter for extended date format

Ujjwal Sharma <ryzokuken@igalia.com> Fri, 16 April 2021 09:38 UTC

Return-Path: <ryzokuken@igalia.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAA63A1E51 for <dispatch@ietfa.amsl.com>; Fri, 16 Apr 2021 02:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 bVNBH-D-NbGM for <dispatch@ietfa.amsl.com>; Fri, 16 Apr 2021 02:38:12 -0700 (PDT)
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 352C83A1E50 for <dispatch@ietf.org>; Fri, 16 Apr 2021 02:38:11 -0700 (PDT)
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:To:Subject; bh=lGpGn3eo7bLT7mFyPeSKLTiBWXgaaIkhMNay/ypkNXs=; b=GQZV5mj0MGiCVPURme9NEH/amKy4Lk5IdEISOy2MzzKJTeHmDj+Llovi5ttGzYRxLZA2BgKysl+3Myl0Mcifct3mnPjzUjXbWnem95ikDFU41let9NRWNwjHmsKGzF2KPig+lXpv0KLGx8rTUlixtDZbx0+qbgQCB/2NhQSykrmp8zPL9G6oVVPHoBtk94enkAAbLshc3Icrx8CHOLfgYI6f2kIEXRW836wTXgFixMWLUhNC1+rGgXIXa5CcS5do+DD2eUwItRyiSAvFYh+wEC3xXip2nDYTzIN6T5HCCTo3grMB9cbozU6xnHZ+p/epkLY7VHdyGyP7716FewPpWw==;
Received: from [183.83.213.40] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1lXKvO-0004GF-LE for <dispatch@ietf.org>; Fri, 16 Apr 2021 11:38:07 +0200
To: dispatch@ietf.org
References: <b654b280-00eb-4869-918f-5580347601ef@dogfood.fastmail.com> <9e1bc197-19d5-44d1-867f-6d35108d63ae@dogfood.fastmail.com> <A6E0CEE4-DFFD-42D2-A514-17E6C7CED24F@cisco.com> <ef575aff-3ab8-40bc-88f4-2f0a5242e1fb@dogfood.fastmail.com> <BE9EF760B2999ECF91D650AB@PSB>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <fcbcbadb-14e9-894f-8bc1-cb40e1c66849@igalia.com>
Date: Fri, 16 Apr 2021 15:07:53 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <BE9EF760B2999ECF91D650AB@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/NJSKUV_9aGI0YT3VoaFS2B2Rvh4>
Subject: Re: [dispatch] Proposed charter for extended date format
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Apr 2021 09:38:19 -0000

Hi John!

On 15/04/2021 06.55, John C Klensin wrote:
> But, since we don't live in that universe (or at least I hope we
> don't), why not work out a collaboration with ECMA TC39 [1] and,
> ideally, a three-way one that includes ISO 154, and sort this
> out together, vastly reducing both the chance of one body
> standardizing something different from the rest of that world
> and, even more important, of messing it up?  Another advantage
> of such an approach is that it tends to drop any bars to
> accessibility to each other's work in progress and other
> documents, thereby addressing the issue John Levine has raised.

I'm afraid I don't quite understand what you mean here? This *is* a
collaboration with ECMA TC39. We are TC39 delegates and the champions of
the Temporal proposal
(https://github.com/tc39/proposal-temporal/#champions) that deals with
the improvements around date-time handling in ECMAScript.

There is consensus among the TC39 delegates that this work should end up
in a standards body like the IETF before we proceed with it, as would be
evident from the discussions during plenary (notes at
https://github.com/tc39/notes/blob/master/meetings/2021-03/mar-9.md#temporal-for-stage-3,
search for "IETF" or my initials, "USA"), so this effort is already a
collaborative one between TC39 and IETF.

Regarding ISO, we have brought this to the notice of the folks working
on ISO8601 and CalConnect who seem to be happy with this generally, but
perhaps we could work to get them more in the loop if needed?

Cheers,
Ujjwal

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

Compilers Hacker, TC39 Delegate, Node.js Core Collaborator and Speaker