Re: [TICTOC] [Sedate] [art] [Cbor] Two specifications on timestamps nearing WGLC

Carsten Bormann <cabo@tzi.org> Thu, 20 October 2022 11:47 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA2EC14CF0C; Thu, 20 Oct 2022 04:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVwlc3wp6sys; Thu, 20 Oct 2022 04:47:05 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E2FCC14F6EC; Thu, 20 Oct 2022 04:47:02 -0700 (PDT)
Received: from [192.168.217.124] (p5089abf5.dip0.t-ipconnect.de [80.137.171.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4MtQmy2DDSzDCbl; Thu, 20 Oct 2022 13:46:58 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <958a7cca-95df-6f81-54d3-d3dd6fd9b617@it.aoyama.ac.jp>
Date: Thu, 20 Oct 2022 13:46:57 +0200
Cc: John C Klensin <john-ietf@jck.com>, art@ietf.org, sedate@ietf.org, cbor@ietf.org, ntp@ietf.org, tictoc@ietf.org
X-Mao-Original-Outgoing-Id: 687959217.7626539-2523761ae0a1867d2cae3395f40998f7
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF5F7BC2-6D57-4B9E-9020-8A4724C13D99@tzi.org>
References: <19C0959C-2DFF-4FA6-9691-792CD2AF5E09@tzi.org> <f7a05134-7ec0-411a-fcc5-d0e80c74d6c6@it.aoyama.ac.jp> <2620A4D0-F624-4E31-BDD1-860B40F7A31D@tzi.org> <193653.1665119732@dooku> <CA4866D1-C1E7-4C58-9D85-088A02885FD0@tzi.org> <9621884E0BC501528B6BB591@PSB> <F30D7B75-B3D3-4B99-83B7-809B2EF4B760@tzi.org> <8ED6029F05884D21580EA2AF@PSB> <958a7cca-95df-6f81-54d3-d3dd6fd9b617@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/6xS9xp5dXmKZ6Fsyf5GsaqEYRLU>
Subject: Re: [TICTOC] [Sedate] [art] [Cbor] Two specifications on timestamps nearing WGLC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 11:47:10 -0000

When I need information about a paywalled document, I usually ask my students, who have a supernatural capability to divine information about such documents.

In this case, they were too lazy for actual divination, and I just got back a reference to a document apparently published by NIST: 

https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub4-1-1991.pdf

(This is missing the 1991 corrigendum, but it is a useful resource.
Delete the blank verso pages...)

Interestingly, I cannot find a prohibition of -00:00 (and I cannot find what would actually allow +00:00 either).  So the statement we got about -00:00 not being allowed by ISO 8601 apparently refers to a different revision…  (And I need to apologize to the RFC 3339 contributors who based their work on the 1988 revision, but then the RFC is also referencing ISO8601:2000, and that reference is also in draft-ietf-impp-datetime-04.)

My students also divined that ISO 8601:2000 appears to rule out using a minus sign for non-negative values.  One section that this can be inferred from is Section 5.1.1, but the result of that inference probably can be debated.  More importantly, Section 5.3.4.1 shows a fix that lets one infer +00:00 is actually allowed, while -00:00 is not.

Oh, and Library of Congress has this for us:

https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_iso_wd_8601-1_2016-02-16.pdf

In that draft document (which is likely to reflect published versions up to its date, but may differ from ISO 8601:2019, the relevant sections that support the hypotheses about +00:00 being allowed and -00:00 not being allowed are 3.4.2 and 4.2.5.1.
Same section numbers for ГОСТ Р 7.0.64-2018, which seems to be ИСО 8601:2004 in Russian language.

Grüße, Carsten