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

Julien ÉLIE <julien@trigofacile.com> Thu, 04 August 2022 13:14 UTC

Return-Path: <julien@trigofacile.com>
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 DF1ECC13C530 for <emailcore@ietfa.amsl.com>; Thu, 4 Aug 2022 06:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 XlM1_Q4xbYZU for <emailcore@ietfa.amsl.com>; Thu, 4 Aug 2022 06:14:34 -0700 (PDT)
Received: from denver.dinauz.org (denver.dinauz.org [37.59.56.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F7DAC13C51C for <emailcore@ietf.org>; Thu, 4 Aug 2022 06:14:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 4155360581 for <emailcore@ietf.org>; Thu, 4 Aug 2022 15:14:29 +0200 (CEST)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id meixA9sVANTX for <emailcore@ietf.org>; Thu, 4 Aug 2022 15:14:29 +0200 (CEST)
Received: from [192.168.1.6] (san13-h02-176-143-2-105.dsl.sta.abo.bbox.fr [176.143.2.105]) by denver.dinauz.org (Postfix) with ESMTPSA id 181E16047E for <emailcore@ietf.org>; Thu, 4 Aug 2022 15:14:29 +0200 (CEST)
Message-ID: <ebe24df9-6335-5626-3826-ed85aa830996@trigofacile.com>
Date: Thu, 04 Aug 2022 15:14:28 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
To: emailcore@ietf.org
References: <20220802031735.E29F746F2656@ary.qy> <305AE7DFC0554733F7C75AAD@PSB> <20220802231408.xOC-e%steffen@sdaoden.eu> <3e5240b4-12ad-0fa1-398a-659a074e46d7@wizmail.org> <20220803223222.OopI_%steffen@sdaoden.eu> <f2e46271-de99-20d4-68ea-a33f560f11d6@trigofacile.com> <8A3BAF234B4580D591240172@PSB>
From: Julien ÉLIE <julien@trigofacile.com>
In-Reply-To: <8A3BAF234B4580D591240172@PSB>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/LNtGFbJGeSNiPGllhAcZ3qSyevc>
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: Thu, 04 Aug 2022 13:14:36 -0000

Hi John,

>> Message-ID: <t9d3rt$29g$2@gal.iecc.com>
>> Date: Mon, 27 Jun 2022 20:27:41 -0000 (UTC)
>> Injection-Date: Mon, 27 Jun 2022 20:27:41 -0000 (UTC)
> 
> So, just to be sure I understand, in the first case "-0000" is
> being used for "unknown for the actual sender/ originator/
> injector" above, with "(UTC)" the time as supplied by the
> Server.  Correct?

Yes, exactly, with "(UTC)" being a comment as CFWS at the end of the 
header field.  This way, it just means that time is given in UTC but the 
local time for the sender/injector is not necessarily the same.
Contrary to "+0000" which would have meant the local time is the same, 
and the sender/injector doesn't mind disclosing that information.

(The INN news server has a parameter, localtime in readers.conf, false 
by default, to configure that behaviour.)



> (2) Should "UT" be taken off the "obs-*" list and added back
> into valid current syntax to allow systems to be clear about
> what is intended, rather than having to guess at the intended
> semantics of "+0000" and "-0000".  I still feel that might be a
> good idea, but I'm not seeing much traction for it.

I was under the impression that the intended semantics was clear in RFC 
5322...  I wouldn't change the list of obsolete time zones.



> (3) Recommendations about what time zones should be chosen for a
> given message, either in the "Date:" header field or in the
> various other fields, notably trace fields, in which time-stamps
> are applied and/or what receiving systems should do about them.
> That seems to be an A/S subject, not a 5322bis/5321bis one.
> Whether we have anything useful to say is another matter.

Maybe a couple of sentences could be added, to recommend either to use 
"-0000" if the real local time zone should not be disclosed, and 
otherwise to use the local time zone including "+0000" which means the 
local time zone matches UTC.  If possible, this behaviour should be 
configurable by the user or administrator.

-- 
Julien ÉLIE

« Ibi etsi uis te non esse sed es ibi. »