IETF Logo Mail Archive

Re: [core] date-and-time and "created-on" field in constrained-voucher

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 27 June 2022 20:24 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD63C147930; Mon, 27 Jun 2022 13:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
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 Gj22wNRkMhmY; Mon, 27 Jun 2022 13:24:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAB69C15AD32; Mon, 27 Jun 2022 13:24:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9797B38B61; Mon, 27 Jun 2022 16:40:50 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kJPpwcGyUTuM; Mon, 27 Jun 2022 16:40:49 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 31CE938B48; Mon, 27 Jun 2022 16:40:49 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1656362449; bh=0gKfAQW99OZtj3O3wMFlLTfkuZeT/p0F5ryIogKu8kQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=PgvQZJGBZXC8Mc8FrtTUmI+idFnvVKtPT7CZCK/3AbgHmnySDisTavK0KnwTsTMuC PTQFrnqwwTPCxVJtNOlKnuaPnh9tvBRvkFWKVxWbnDM8rZT6+4zSlI1FhYjmAmA553 ZdLRplNYAjyYcHjrkSt4m48+HvhGh9xuq5TOl2e2hPOZ/LyGOFQbFAlIxv6Ii0oFdI 7tdKHDreHe0GcXEWbIQ1l61dSTT7nrZzdD9XotQY30M4lfOTE1QbwhFjQilOSUTi0h 9gK6DDm1PvvEDWWQ7ptkho/wIcsDoel681LiwE+3Mj680pBHhEL51U4KUigZePnN6X 27VTan+pyW/sw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 967BC661; Mon, 27 Jun 2022 16:24:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: core@ietf.org, anima@ietf.org
In-Reply-To: <24048.1656352364@localhost>
References: <DU0P190MB1978F90B0893D32291F6EE7DFDB99@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <24048.1656352364@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 27 Jun 2022 16:24:18 -0400
Message-ID: <6941.1656361458@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/wybZuH0_jaq3_PvoXgGCIRbUSqo>
Subject: Re: [core] date-and-time and "created-on" field in constrained-voucher
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2022 20:24:31 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > 2.  The other thing we ran into was that the CBOR implementation I'm using, when given a
    > DateTime object naturally produces a RFC 8949 Section 3.4.2 compliant "tag 1" marked Epoch-Based
    > Date/Time.  And demarshalls this.  So I don't really notice.

    > But, draft-ietf-core-yang-cbor doesn't say much about "yang:date-and-time".
    > The only reference seems to be at:
    > https://www.ietf.org/archive/id/draft-ietf-core-yang-cbor-20.html#name-the-container-and-other-nod

    > where date-and-time is shown as part of a container object.
    > The Content is defined to be string date pattern.

"created-on"=>"2022-06-17T09:21:32.299Z"

We don't need this much precision either, so I wonder if we can forbid it.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email