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

Phillip Hallam-Baker <ietf@hallambaker.com> Wed, 14 April 2021 19:37 UTC

Return-Path: <hallam@gmail.com>
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 23BAB3A1CF6; Wed, 14 Apr 2021 12:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 sqtgs27Fkp8f; Wed, 14 Apr 2021 12:37:04 -0700 (PDT)
Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 741213A1CF1; Wed, 14 Apr 2021 12:37:04 -0700 (PDT)
Received: by mail-yb1-f170.google.com with SMTP id o10so23418045ybb.10; Wed, 14 Apr 2021 12:37:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=w9ai63aRpL2q0ywtr3rhR4Cit7nJMxm+RarrPA+po8E=; b=A5bFtVI1rLokr0lFdkRxg3qyH4nUoWTYQp+fHunFfI/uPPFNttxWlGrPQddCKZNN9b Cy/EhbJLRQeQ9ecsUvjLxI8PRg3/CNnXEWq0z1dDB7TGJishoqX0BsqRk5LCxzl25Uc8 W7LMAQADLTymKzl+NqoLCjTRcCGe+tEb//M6x7TcSqkJnCFPavY3bIjfyJbPSNwgiynL D1HiehA/iPpytAXzlYpmPcOYtDWVrhMxLzkRD3TjpPd8dhmgNtHFc8s+wBEZWuFI8J8u 58vtHaog3SNSbxB+p6KuUq30gmyOgQiKZ22gZf5aCdHuW0/lWldrQXFIPll4y0qXCXJp eu1Q==
X-Gm-Message-State: AOAM530Zpc5K9nKFCOPl3dCU0WfS55VqkDlvfjlNq/NTYKJJAYcbgp8w QqsmxncTb0g9KdYfuhMRn/lQihwYsUnwRHhw8WQbYpbt
X-Google-Smtp-Source: ABdhPJxlmrtQD/ZeYxzgMPrTOd7oTpDUn7QiR4aFeS8JBqTTccnVGG+tMbBDcm1QjUPHVyMYqkltDvbdWW/zn0aPKgA=
X-Received: by 2002:a25:4c7:: with SMTP id 190mr11178534ybe.480.1618429023451; Wed, 14 Apr 2021 12:37:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAAyEnSMBdXCA0EvgR79P_1gi15pAPfeyu_HgGqgMjWxRP8sxKg@mail.gmail.com> <C7B5DB45-F0A1-491C-AD4E-91F67C8C182E@cisco.com> <B3D690C21848AF07EC92577F@PSB>
In-Reply-To: <B3D690C21848AF07EC92577F@PSB>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Wed, 14 Apr 2021 15:36:50 -0400
Message-ID: <CAMm+LwiNGDMF9muA0p3uYALSiPFNEpZ5vrkyXRnUzqdBL02Jjw@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: "Eliot Lear (elear)" <elear=40cisco.com@dmarc.ietf.org>, Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, "General Area Review Team (gen-art@ietf.org)" <art@ietf.org>, IETF SAAG <saag@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000097e0f05bff3df7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/wgcYEMI2ADYyQ2Dl_-BdY1Aw8SY>
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: Wed, 14 Apr 2021 19:37:09 -0000

I am also going to strongly +1 John here.

At this point, the only question I would consider in a protocol is the
choice of UTC or TAI.

Unfortunately, the method of platform handling of UTC means that all date
time values recorded in electronic documents are inherently ambiguous, a
state of affairs that will persist until the cretinous notion of leap
seconds is done away with.





On Tue, Apr 13, 2021 at 4:06 PM John C Klensin <john-ietf@jck.com> 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
>