Re: [dispatch] Proposed charter for extended date format
Bron Gondwana <brong@fastmailteam.com> Wed, 14 April 2021 16:00 UTC
Return-Path: <brong@fastmailteam.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 DEBA83A14DB for <dispatch@ietfa.amsl.com>; Wed, 14 Apr 2021 09:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Level:
X-Spam-Status: No, score=-2.819 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmailteam.com header.b=NqASkRNU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=H3X8YbrX
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 AczzcXT5eG6a for <dispatch@ietfa.amsl.com>; Wed, 14 Apr 2021 09:00:35 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6E0F3A14D9 for <dispatch@ietf.org>; Wed, 14 Apr 2021 09:00:35 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 2F4265C00F9; Wed, 14 Apr 2021 12:00:31 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute2.internal (MEProxy); Wed, 14 Apr 2021 12:00:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm2; bh=L2Gz oBUSNL8FMzsS3oY5mdp2hVMVlw7VS74dYl9rNYQ=; b=NqASkRNUDrj9YTkwjxMr SPT9NkHtyVjAE+bRAqeVVptRGVZom5K98MZYfnDN3Mxyg3pUy+gqcTihrUoobjcv AeGOunk1k47JYdq6Fxd3XQndl5ryVeu5qof2ptTPQ4kNPWT4x/Z6H3bAq9aFkMCA bdeb472XYGnbhoHUHl3EMkCYrOwanxp0tMpYpArnaCYtuFoPCBSlJ0dPZztgvzVA HxEinaqQYLJ43s0WircB/QLduO/Rsfl2djoRtcdmAeFU5F/Fin4Qb7OOELy/PS6g WNqaF5cGN4xmu5+dN46F7jqntgufOJuC8rpEi9Cpg1XaitU3C2JyuCdbsRA841dx 7w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=L2GzoB USNL8FMzsS3oY5mdp2hVMVlw7VS74dYl9rNYQ=; b=H3X8YbrXjJrGi2sa6njtt0 9D5XPTBhvJYnjw4y5moVhoeJWtcpTa9RNOYgCB1NnlGriv2rDBM7AhD4Uv2AjO/5 FXKiFb2coIj8xtjF/BUu7UJYUR7Owj24myNkVisAJbUa/u8hXS4VUIK4aDPuafcN VWWhv9wpx0v3Ta5Z7mFRR5n7flk8s0bbm/zs7ATZl563qWtgCBocuXA95l7laD2b 0eD0xu4C6bKq94/VMR9wDPxzVcfkLpCgEfTMoW76d0Kg41TnSx4IWUbhworyZEGQ L+XTSTuy/qwjlgCciGI9jsaHDTAs4Bb86jy5yOuZf2tlyKxnDIr65Mf6S48CVqkg ==
X-ME-Sender: <xms:nhF3YO7d9p7roL_OXrvg1qs-TmqE-co_o0-ifQ3uvqPEv02ND75wdQ> <xme:nhF3YH5u3r3nBMLPtH-e6QZZnAjubsY6Rj00MNu73glPv7aMmhrayfNJ99eai7rk7 w6TfgULquw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeluddgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnhepffevfeeigfejveetheehleegteelteevgeeutdfhhefg hfdtjefhvdehhfdtkefgnecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhm rghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:nhF3YNeXgsZgQYJyfsHBYVtTgAvC0H3mPpss9aK0Bk-mO5WKzDX2Sg> <xmx:nhF3YLI8HYsijUWaEKmy4jtvIQacFWn0t3h-pMW4P1bj1TwDnqH6BQ> <xmx:nhF3YCKIVgxrmgt3CkIOspHseBylSe1J5AbTP8R7tUGdrUa6HYYgDw> <xmx:nxF3YEhsiIZht_m_dYg6wjHc4lxA88AKjnpEo92S3cVWzHjG9bpmAQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 76798260005F; Wed, 14 Apr 2021 12:00:30 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-378-g5ea5579899-fm-20210412.001-g5ea55798
Mime-Version: 1.0
Message-Id: <9e1bc197-19d5-44d1-867f-6d35108d63ae@dogfood.fastmail.com>
In-Reply-To: <b654b280-00eb-4869-918f-5580347601ef@dogfood.fastmail.com>
References: <b654b280-00eb-4869-918f-5580347601ef@dogfood.fastmail.com>
Date: Thu, 15 Apr 2021 02:00:09 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: dispatch@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Ujjwal Sharma <usharma@igalia.com>, Shane Carr <sffc@google.com>
Content-Type: multipart/alternative; boundary="d18cd176a36a4583b929e67f7c7db54b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/4qgSN8ETNmf_0dPBasEQ4x9tyZw>
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: Wed, 14 Apr 2021 16:00:40 -0000
This was discussed in the DISPATCH meeting at IETF110: https://datatracker.ietf.org/doc/minutes-110-dispatch/ The conclusion of the discussion was: * Kirsty (chair): Sounds like there's general agreement that a working group is what's needed, we will take a final decision on the list and just confirm with Patrick as co-chair before officially dispatching as such. The link to the charter is on list too, please take a look and see if you think a BoF is needed as the next step or a WG can begin right away. So Murray (AD), do you think we have enough to request a working group be charted from the discussion and the proposed charter text quoted below? Thanks, Bron. On Fri, Feb 19, 2021, at 15:20, Bron Gondwana wrote: > I've asked the chairs for space on the next dispatch agenda to talk about dispatch for > > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ > > The authors have taken on board the idea that we should extract the "obsolete RFC3339" and either remove it entirely, or separate it into a document which does nothing but update RFC3339 with support for a wider range of year values. There will be an updated version of this draft soon. > > The dispatch chairs also asked me for some proposed charter text if we were to spin up a working group for this topic. Here's that text. > > Cheers, > > Bron. > > Serialising Extended Data About Times and Events (SEDATE) > ---- > > RFC3339 defines a format that can reliably express an instant in time, either in UTC or in a local time along with the offset against UTC, however datetime data often has additional context, such as the timezone or calendar system that was in use when that instant was recorded. Particularly when using times for interval, recurrence, or offset calculations, it's necessary to know the context in which the timepoint exists. > > It is valuable to have a serialisation format which retains this context and can reliably round-trip the additional context to systems which understand it, via intermediate systems which only need to know about the instant in time. > > The TC39 working group at ECMA have developed a format which is a good basis for this work. > > It is anticipated that this document would be a companion to RFC3339 rather than a replacement, embedding an un-altered RFC3339 instant along with the contextual data. > > It is also within scope for this group to consider a minor update to RFC3339 to allow larger than 4 digit signed years, to enable representing times further into the past and future. > > Once this work is done it is anticipated that this working group will be short-lived, and once the one or two documents are published the working group will close down. > > Milestones: > * April 2021: Adopt draft describing a serialisation format for extended datetimes. > * July 2021: Submit the serialisation document to the IESG. > > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com > > -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com
- [dispatch] Proposed charter for extended date for… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… Carsten Bormann
- Re: [dispatch] Proposed charter for extended date… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… John C Klensin
- Re: [dispatch] Proposed charter for extended date… Eliot Lear
- Re: [dispatch] Proposed charter for extended date… John C Klensin
- Re: [dispatch] Proposed charter for extended date… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… Carsten Bormann
- Re: [dispatch] Proposed charter for extended date… John Levine
- Re: [dispatch] Proposed charter for extended date… Martin J. Dürst
- Re: [dispatch] Proposed charter for extended date… John R Levine
- Re: [dispatch] Proposed charter for extended date… John C Klensin
- Re: [dispatch] Proposed charter for extended date… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… Bron Gondwana
- Re: [dispatch] Proposed charter for extended date… Ujjwal Sharma
- Re: [dispatch] Proposed charter for extended date… Eliot Lear
- Re: [dispatch] Proposed charter for extended date… Eliot Lear
- Re: [dispatch] Proposed charter for extended date… Shane Carr
- Re: [dispatch] Proposed charter for extended date… Francesca Palombini