IETF Logo Mail Archive

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

Henry Story <henry.story@gmail.com> Thu, 15 April 2021 13:29 UTC

Return-Path: <henry.story@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 DF8573A1FD6 for <saag@ietfa.amsl.com>; Thu, 15 Apr 2021 06:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qsrQXu68LVWK for <saag@ietfa.amsl.com>; Thu, 15 Apr 2021 06:29:40 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 024DA3A1FD2 for <saag@ietf.org>; Thu, 15 Apr 2021 06:29:39 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id e14so36826748ejz.11 for <saag@ietf.org>; Thu, 15 Apr 2021 06:29:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=3vndG9J+iiWqTzTwVdMwKjsxHVNF66tBCUzAQueQGLA=; b=WbPIuujRVIyXC3zH6sdCsfqcHgDLf6MfviLtp+KDK6hSz0P/7zzpI5e9WKQfQ6ETyC aX2O135xC0CAtde8rt/+/7/8w2byOff6xBPYzGT3FCQ6eh/0agrZa1aAJJrziaArZDd6 Oliuc//06cDOtfGaMQ3Ys8M/q3dIM1C7scgN2+rXeRf0nGV2sfM0eZ9N9mkUfPTAje3K xdwvgfIqWPGmX6OQmFNQ8KD1tKYbMPZUeonpPiy3nu1JLdm7rNuKrza46/yh5tyCV1+f V9PIo1q0GaDBdJQS4nNai/2Gmx61pjHO6d9qGWdF8KwAhGhh1tuPk/uZ0kVwaChgbHa5 AyoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=3vndG9J+iiWqTzTwVdMwKjsxHVNF66tBCUzAQueQGLA=; b=knDZhw8ZHw+BbKGaOtOUttPkH0Kqj/CWYD/DyaDgrwJCGl5Od0vRaM/qmQjr3DyK+o HIsmu5R37lMfhbvE8WQzJRmxc3eMYz8BwZYnxUTPFCEH6wAD9z7x3EfUD/xYOjreaLzI kjzmrddRSOh2AV5iCxgxEkCkTbfwzj/9ZsXuypANUBOeNnZ8/LV+Xvg8X8cx4xr6oNNM ctL7A9859T3By6XaU3HKB/vqYqwS79RjWkQcQhCFsjUSyWr/nRQswlujz0HobQRgY7sA WqnLRbtayS+XFOFCNeltaBIQedOext9a6CnXs0FAUXpCUi1UUrU4QRx+b+pLPOlxgNqU 6ENw==
X-Gm-Message-State: AOAM532zS7bQFBV2HDtOUUe2vUNxobchoxPqgNO44Pdv4xSF+eKSaOIP xel1TnUiq0593K8x5gGM85kWggC3Gsg=
X-Google-Smtp-Source: ABdhPJyxMYQ1c0RVO6mZZGnPtQHow1UD6Osj5PYL29HTr4lhbztxtXhPB8UI9uC5VGZ6Je2EXgmyug==
X-Received: by 2002:a17:906:1b54:: with SMTP id p20mr3463579ejg.477.1618493377588; Thu, 15 Apr 2021 06:29:37 -0700 (PDT)
Received: from bblfish.fritz.box (p5793ad5d.dip0.t-ipconnect.de. [87.147.173.93]) by smtp.gmail.com with ESMTPSA id a18sm1972571ejr.76.2021.04.15.06.29.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Apr 2021 06:29:36 -0700 (PDT)
From: Henry Story <henry.story@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1F6CA4E8-0480-4BF5-8A14-C1798ACC4815"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Thu, 15 Apr 2021 15:29:34 +0200
References: <CAAyEnSMBdXCA0EvgR79P_1gi15pAPfeyu_HgGqgMjWxRP8sxKg@mail.gmail.com>
To: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, saag@ietf.org
In-Reply-To: <CAAyEnSMBdXCA0EvgR79P_1gi15pAPfeyu_HgGqgMjWxRP8sxKg@mail.gmail.com>
Message-Id: <ADC7ED48-8D36-41C0-9AD5-3154419216C7@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/Z9jRJR1kXGS1m-6hGUrJvBW54Bs>
Subject: Re: [saag] 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: Thu, 15 Apr 2021 13:29:45 -0000

What about unix time: seconds or milliseconds since the Unix Epoch?
That removes all kinds of parsing problems as well as calendaring problems.
And it fits well with RFC8941 Structured Fields SfInteger.
That is used by Signing HTTP Messages draft in their Signature-Input header.

> On 13. Apr 2021, at 20:43, Yakov Shafranovich <yakov@nightwatchcybersecurity.com> 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
> 
> Thanks
> 
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag

v2.8.7 | Report a Bug | By Email