Re: [Cbor] draft-ietf-cbor-date-tag-02 - handling of time zone offsets

Carsten Bormann <cabo@tzi.org> Thu, 09 July 2020 07:37 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA4F3A086E; Thu, 9 Jul 2020 00:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RiN_SdPz3fLu; Thu, 9 Jul 2020 00:37:54 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90A133A086C; Thu, 9 Jul 2020 00:37:54 -0700 (PDT)
Received: from [192.168.217.116] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4B2Sgv2rBjz17p1; Thu, 9 Jul 2020 09:37:46 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <014101d655a5$fcf4ba30$f6de2e90$@augustcellars.com>
Date: Thu, 09 Jul 2020 09:37:35 +0200
Cc: Mike Jones <Michael.Jones@microsoft.com>, draft-ietf-cbor-date-tag@ietf.org, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 615973055.2951061-8584596602d9aee061858a21744d97f2
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD58CC30-2E41-451D-AF9C-241CF1302CBA@tzi.org>
References: <MN2PR00MB06889C828D2E5900D1795D70F5670@MN2PR00MB0688.namprd00.prod.outlook.com> <014101d655a5$fcf4ba30$f6de2e90$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/2OfU07RbTgUIwPyruGygP-EatUs>
Subject: Re: [Cbor] draft-ietf-cbor-date-tag-02 - handling of time zone offsets
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 07:37:57 -0000


> On 2020-07-09, at 06:04, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> I agree that I don't want to deal with differences in calendars.  

Tag 100 is calendar agnostic, as long as the calendar has an equivalent to what is 1970-01-01 in the Gregorian calendar, and can count earth days back/forward from that.

Tag 1004 has the Gregorian calendar baked in, with leap years etc.  That also means that 1582-10-04 (100(-141428)) is immediately followed by 1582-10-15 (100(-141427)), and even more caution is needed before this date (proleptic Gregorian calendar).  But we don’t have to explain all that, just point out that there is some complexity with the proleptic Gregorian calendar.

Tag 100 dates inherit some of that complexity if combined with/converted to/from Gregorian dates, more so if the conversion actually is to/from a date-time anchored to a time zone (civil time).  That is also pretty much all we need to say about that.

> It might have been easier to go with the Jewish calendar but that would not be at all well known.  The conversions on dates should assume that the calendars are the same (and reasonable).

I’d go with the French revolutionary calendar — ten-day weeks (properly split into five workdays and five-day weekends, of course) would be so much more natural.  But I digress…

Grüße, Carsten