IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 28 June 2022 02:32 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 F1460C1595E6; Mon, 27 Jun 2022 19:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.709
X-Spam-Level:
X-Spam-Status: No, score=-1.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 3mromO7k5acL; Mon, 27 Jun 2022 19:32:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 F2B84C14F74E; Mon, 27 Jun 2022 19:32:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7A28D38B2D; Mon, 27 Jun 2022 22:49:03 -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 8x8vealonNLJ; Mon, 27 Jun 2022 22:49:02 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 157A338B2C; Mon, 27 Jun 2022 22:49:02 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1656384542; bh=0213ntAY4sgtYsZs8MuHoAKjK7IV6VENukFUGT88FzY=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=uCMPVOK1zX/tzh5ZmDDeHxQGfSbz4vPwVROaK35ts1+SngJXmtPdYEu3C7n8oLvUR baefSPiILSZVZggtRig/fuMiQspaxXhk7x9JFs2h7NNup5GZ8M59N/XHLsIKWw/cXI 5J/0vn9FxJ6HSfU43a8V+GoDzSwPxGeJx0bzJM0EF2ZT5Hi2Sd3hPAkzFTtjWYoDwX qKsUA5pmBHEijVwtjTKOvWD8c0UMplHPv2byuYe1n38C8lECRqtvj+yoZPGZIXYUdP m6Xk3z3npf/RKUd6Gpl908KCLXR+4SBq61KbbKtrZ7ltipoysui7Mmr8tCLBEx8hxq yQMuQvsIzrB6g==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8A20630; Mon, 27 Jun 2022 22:32:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andy Bierman <andy@yumaworks.com>
cc: Core <core@ietf.org>, anima@ietf.org
In-Reply-To: <CABCOCHS6=F0tfESkVmOk1AFKvsu4tRfKu9A_Sgz5swVXv-eXCQ@mail.gmail.com>
References: <DU0P190MB1978F90B0893D32291F6EE7DFDB99@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <24048.1656352364@localhost> <25937.1656365067@localhost> <CABCOCHS6=F0tfESkVmOk1AFKvsu4tRfKu9A_Sgz5swVXv-eXCQ@mail.gmail.com>
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 22:32:30 -0400
Message-ID: <26870.1656383550@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/PtAEn4eFByRDqWrDS85Iy8WTyEU>
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: Tue, 28 Jun 2022 02:32:44 -0000

Andy Bierman <andy@yumaworks.com> wrote:
    > This change is not backward-compatible and not allowed per RFC 7950, sec 11.
    > A new typedef with a different name is needed to allow the uint64 encoding.

Since RFC8366 uses yang:date-and-time, and our document derives from it,
short of revising RFC8366, is there something we can do to allow use to use
tag 1 when we encode in draft-ietf-anima-constrained-voucher?

It sure seems like a major omission in yang-cbor, which is yes, approved, but is just
AUTH48 today...

(Noting that revising RFC8366 *is* on our agenda, just order of operations,
we didn't think we'd have to do that first)

--
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