Re: [Emailcore] WGLC: draft-ietf-emailcore-rfc5322bis-03

Steffen Nurpmeso <steffen@sdaoden.eu> Wed, 03 August 2022 22:32 UTC

Return-Path: <steffen@sdaoden.eu>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498D8C147930 for <emailcore@ietfa.amsl.com>; Wed, 3 Aug 2022 15:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level:
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_ILLEGAL_IP=1.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 fT71HpcHNDFE for <emailcore@ietfa.amsl.com>; Wed, 3 Aug 2022 15:32:27 -0700 (PDT)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C479FC14792A for <emailcore@ietf.org>; Wed, 3 Aug 2022 15:32:26 -0700 (PDT)
Received: from kent.sdaoden.eu (kent.sdaoden.eu [192.0.2.2]) by sdaoden.eu (Postfix) with ESMTPS id C095016059; Thu, 4 Aug 2022 00:32:23 +0200 (CEST)
Received: by kent.sdaoden.eu (Postfix, from userid 1000) id 9D57F92C58; Thu, 4 Aug 2022 00:32:22 +0200 (CEST)
Date: Thu, 04 Aug 2022 00:32:22 +0200
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Jeremy Harris <jgh@wizmail.org>
Cc: emailcore@ietf.org
Message-ID: <20220803223222.OopI_%steffen@sdaoden.eu>
In-Reply-To: <3e5240b4-12ad-0fa1-398a-659a074e46d7@wizmail.org>
References: <20220802031735.E29F746F2656@ary.qy> <305AE7DFC0554733F7C75AAD@PSB> <20220802231408.xOC-e%steffen@sdaoden.eu> <3e5240b4-12ad-0fa1-398a-659a074e46d7@wizmail.org>
Mail-Followup-To: Jeremy Harris <jgh@wizmail.org>, emailcore@ietf.org
User-Agent: s-nail v14.9.24-282-gfb47a7f660
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/3uW3UsMsY8CvkOFEKKhEaor5qiM>
Subject: Re: [Emailcore] WGLC: draft-ietf-emailcore-rfc5322bis-03
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2022 22:32:32 -0000

Jeremy Harris wrote in
 <3e5240b4-12ad-0fa1-398a-659a074e46d7@wizmail.org>:
 |On 03/08/2022 00:14, Steffen Nurpmeso wrote:
 |>    Though "-0000" also indicates Universal Time, it is used to
 |>    indicate that the time was generated on a system that may be
 |>    in a local time zone other than Universal Time and that the
 |>    date-time contains no information about the local time zone.
 |> 
 |> because the widely used MTA exim does not do that (or did not when
 |> the patch was committed in 2020, i did not look at the current
 |> code base).
 |
 |I don't think it's changed in that aspect.
 |
 |My probable reasoning was
 |a) a sub-minute offset (TAI being the case in point)
 |    is not displayable with the existing format
 |b) UTC is calculable, displayable, and well-understood
 |c) there was existing handling for UTC timestamps
 |    as a config option
 |
 |I wasn't aware of the "-0000" indicator
 |and I wouldn't have taken a UTC time as indicating that
 |the writer of it was in the GMT timezone.
 |
 |I probably still wouldn't...  I don't recall *ever*
 |seeing "-0000".

Me neither, consciously.  Nor do i believe that most (practically,
all) people ever will put value on that "-".  There was just
a bell ringing when i saw the changeset.  The important thing to
me was of course your struct tm* pointer switch from localtime(3)
to gmtime(3).  I will do this too.

Ciao,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)