Re: [saag] [art] Date formats: RFC3339 vs. RFC 5322

Claudio Allocchio <Claudio.Allocchio@garr.it> Tue, 13 April 2021 20:58 UTC

Return-Path: <Claudio.Allocchio@garr.it>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF2C53A0CF8; Tue, 13 Apr 2021 13:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=garr.it
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 0byQHOtXRfk9; Tue, 13 Apr 2021 13:58:50 -0700 (PDT)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [193.206.158.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D93E93A0CF6; Tue, 13 Apr 2021 13:58:49 -0700 (PDT)
Received: from mac-allocchio3.garrtest.units.it (unknown [10.2.2.13]) by smtp-1.dir.garr.it (Postfix) with ESMTPSA id EA6E09FB6A; Tue, 13 Apr 2021 22:58:44 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=garr.it; s=202004; t=1618347525; bh=SM0rYB/O19MjT9r6urAjn+xHK7y7cXNgfgO3Z5jLrhc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=HNzdLy5PS3sROGXnhUvtT1nIngohYgb/rlmXHz6lKG1h0SGBxg1rR08BlUqCUCR6w FaKjVfVnuzCAxHqMm/2j/lDQCMDRu9zaz6mpTdohrnfMXGqEoUrB8V+PDl04t7i/CV n2AKPhjo3kSUn7K780oB3fgXgmCHb/oSpzdwijlCKAm9PAUXwGC6rCj04n2Es7ZZFL vqUSHwGTp4r7Tl1GB+ZHOLpoTmnnNEpPne+4xZUivnAvr83YybGBudvwS7u9aLSmK9 vYSHgeP6C6AYdOqWjxSmCYm1Z3Y1mnjHazBeU7hchTjGBFBmywXBbhrD8YmGnfBU11 4n/m8ZBvJFGWA==
Date: Tue, 13 Apr 2021 22:58:44 +0200
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.local
To: John C Klensin <john-ietf@jck.com>
cc: "Eliot Lear (elear)" <elear=40cisco.com@dmarc.ietf.org>, Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, art@ietf.org, saag@ietf.org
In-Reply-To: <B3D690C21848AF07EC92577F@PSB>
Message-ID: <alpine.OSX.2.20.2104132217310.1318@mac-allocchio3.local>
References: <CAAyEnSMBdXCA0EvgR79P_1gi15pAPfeyu_HgGqgMjWxRP8sxKg@mail.gmail.com> <C7B5DB45-F0A1-491C-AD4E-91F67C8C182E@cisco.com> <B3D690C21848AF07EC92577F@PSB>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-890075638-1618347432=:1318"
Content-ID: <alpine.OSX.2.20.2104132257220.1318@mac-allocchio3.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/jg87FpE7bmAuZ04RuXyUeryMCEw>
Subject: Re: [saag] [art] Date formats: RFC3339 vs. RFC 5322
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 20:58:56 -0000

let me do a wider diversion:

human reading of time and date, was and still is a cause of problems: the 
human readable version, with all its flavours, variants, causes 
headaches... every time we schedule a meeting we need to ensure all do 
understand when it is... 04/07/2021  at 2.30PM  is it the 4th day of July 
2021, or th e 7th date of April? 2.30PM which time zone? DST or not?

So to go back to the point, +1 to John: ISO 8601 is better, also for 
humans!

(the date/time paring code for email gateways I wrote 30+ years ago was 
a set of nested "if" "then" "else" "and" "or" and tables... no thank you.)


On Tue, 13 Apr 2021, John C Klensin wrote:

>
>
> --On Tuesday, April 13, 2021 19:00 +0000 "Eliot Lear (elear)"
> <elear=40cisco.com@dmarc.ietf.org> wrote:
>
>> The question is whether you need something that is easy to
>> parse or something that is human readable and can be
>> localized.  It SEEMs that this draft is intended to be human
>> readable, and so 5322 doesn't seem out of bounds.
>
> I suggest that even for reading by humans in 2021 --as distinct
> from 1982 (RFC 822) or 1977 (RFC 733, which used day-month-year
> ordering)-- the 5322 dates are not easy to understand and use...
> at least unless one is an English speaker on this side of the
> pond.  It was quite wise at the time to spell out the month
> name, thereby eliminating the ambiguity associated with, e.g.,
> 5/10/1977, but still bad news for someone who might think the
> fourth month in the Gregorian calendar is, e.g., апреля,
> أبريل , or 四月.
>
> So I would argue that, for new protocols or data structures in
> this increasingly global/ international Internet, and even for
> elements visible to humans, sticking as close to ISO 8601 as
> possible (with minimal profiling) is the Right Thing to Do.
> Much too late now to change the 822/5322 format, turning
> supplemental protocols for email into a gray area, but, for new
> work, ISO 8601 formats are not just easier to parse but easier
> to understand globally and in an unambiguous way.
>
> Just my opinion, of course.
>
>
>    john
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

      PGP Key: https://www.cert.garr.it/servizi/informazioni-su-pgp-keys