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

Ned Freed <ned.freed@mrochek.com> Tue, 13 April 2021 22:26 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95273A12EF; Tue, 13 Apr 2021 15:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
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 OShrCEmTseUf; Tue, 13 Apr 2021 15:25:57 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D77A3A12E4; Tue, 13 Apr 2021 15:25:56 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RXTS9CKTSW00HE4N@mauve.mrochek.com>; Tue, 13 Apr 2021 15:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1618352452; bh=VyPYKdRldGKqG/AjXCbPNj06MVVXTcRLbfTXjBuCOyo=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=EwlvaTO55Z4sus+8wU/r81nZsgu6zoTfrDFYioKmkPugHrkOXSfNBU2kl0SEJf2Vj BeL4T0tlKfrSg+HtzU/mpR2jUiQkBfZsxA4YOx0DfpM5tiCCp/pYGEa3k2UMUbuCKe jX5679aPOIb4cUwtVKVmZPxv7zQ1RxE6dGMMZWjM=
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="utf-8"; Format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RXTM8LE0RK0085YQ@mauve.mrochek.com>; Tue, 13 Apr 2021 15:20:49 -0700 (PDT)
Cc: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, art@ietf.org, saag@ietf.org
Message-id: <01RXTS9APXIU0085YQ@mauve.mrochek.com>
Date: Tue, 13 Apr 2021 15:17:45 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 13 Apr 2021 12:30:21 -0700" <901F4345-91B6-42CA-9F68-27DB4C539F3D@vpnc.org>
References: <CAAyEnSMBdXCA0EvgR79P_1gi15pAPfeyu_HgGqgMjWxRP8sxKg@mail.gmail.com> <901F4345-91B6-42CA-9F68-27DB4C539F3D@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/zsI8PjAxyqVvd3IXwvdMeyQT24A>
Subject: Re: [art] [saag] Date formats: RFC3339 vs. RFC 5322
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 22:26:02 -0000

> On 13 Apr 2021, at 11:43, Yakov Shafranovich wrote:

> > Is there a preference for Internet drafts/RFCs regarding the specific
> > data/time format to be used?
> >
> > Right now we are referencing RFC 5322, but there has been feedback
> > from multiple people that the ISO 8601 format is easier to parse. This
> > is in regards to the section 3.5.5 of "draft-foudil-securitytxt-11"
> > that I am working on:
> > https://tools.ietf.org/html/draft-foudil-securitytxt-11#section-3.5.4
> >
> > The options I am asking about are the following:
> > - RFC 3339 (a profile of ISO 8601)
> > Example: 2021-04-13T06:50:53-07:00
> >
> > - RFC 5322, section 3.3
> > Example: Tue, 13 Apr 2021 06:50:53 -0700

> Given that the date in that section of that draft is meant to be machine
> parsed, choosing RFC 5322 (neé 822) date formats is a particularly bad
> idea, given the existence of RFC 3339.

Whenever machine parsing enters the picture the other syntax that should be
considered is integer milliseconds since epoch. (This syntax is increasingly
popular in the schemata I encounter.) However, I think there's also a need for
this to be readable. RFC 3339 seems like the right balance to me.

				Ned