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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 01 July 2020 07:21 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 8A9C23A093E; Wed, 1 Jul 2020 00:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ztoKwsjsSL_Z; Wed, 1 Jul 2020 00:21:28 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB69B3A093D; Wed, 1 Jul 2020 00:21:27 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 15480670; Wed, 1 Jul 2020 09:21:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.198]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id 4HoMv7Ul-CuT; Wed, 1 Jul 2020 09:21:24 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Wed, 1 Jul 2020 09:21:24 +0200 (CEST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id B783D20154; Wed, 1 Jul 2020 09:21:24 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id Z6T71eHYsSZq; Wed, 1 Jul 2020 09:21:24 +0200 (CEST)
Received: from localhost (anna.jacobs.jacobs-university.de [10.50.218.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by hermes.jacobs-university.de (Postfix) with ESMTPS id 87B10200E4; Wed, 1 Jul 2020 09:21:24 +0200 (CEST)
Date: Wed, 01 Jul 2020 09:21:23 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: draft-ietf-cbor-date-tag@ietf.org
Cc: cbor@ietf.org
Message-ID: <20200701072123.hnyhzemagtotnuyl@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/7Qp7uH5CrnabcXiAks0prfe0QHM>
Subject: [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: Wed, 01 Jul 2020 07:21:31 -0000

Hi,

I just saw your CBOR date type and it seems it does not include a
timezone offset. This means a date value does not represent a 24 hour
time interval but something larger. XML schema's date type allows the
optional inclusion of a timezone offset. The date definition in
draft-ietf-netmod-rfc6991-bis-03.txt (still under discussion) includes
a mandatory timezone offset (since it was already mandatory for
date-and-time). I do not know whether we should have a common approach
for this.

Note that your 'number of days since the epoch 1970-01-01 does not
really say 1970-01-01T00:00:00 and also leaves it open whether this is
calculated in UTC or not (on Unix-like systems, time is usually
counted in UTC).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>