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

Carsten Bormann <cabo@tzi.org> Wed, 29 June 2022 23:12 UTC

Return-Path: <cabo@tzi.org>
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 EECA2C14F744; Wed, 29 Jun 2022 16:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 yjcjg8wFt63b; Wed, 29 Jun 2022 16:12:46 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 5440EC14F733; Wed, 29 Jun 2022 16:12:46 -0700 (PDT)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4LYHLN52z8zDCc1; Thu, 30 Jun 2022 01:12:44 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABCOCHRNveBNYm0boZRoWhX2+SerB0=9bx+T2D89UNMQkAv_Xw@mail.gmail.com>
Date: Thu, 30 Jun 2022 01:12:44 +0200
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, anima@ietf.org, Core <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <396DBABC-7F5C-48B7-ADBB-39401624DD94@tzi.org>
References: <24048.1656352364@localhost> <25937.1656365067@localhost> <CABCOCHS6=F0tfESkVmOk1AFKvsu4tRfKu9A_Sgz5swVXv-eXCQ@mail.gmail.com> <26870.1656383550@localhost> <CABCOCHSkh95PEEM5E3YKe_yc5VmsY90XxT1D-z3AiJwwcG-HhA@mail.gmail.com> <7669.1656440710@localhost> <6DCC06F4-3799-4CC0-8780-21E6B12A4022@tzi.org> <CABCOCHQqtKw6cZ1o7nzDmQBN0zQP70CgeAAc6nFdRa_kB+-DBQ@mail.gmail.com> <09C66776-54C5-4C5D-9DFA-E164A1050170@tzi.org> <E51C95DD-0AC5-40E4-8609-E0B444E77786@tzi.org> <20220629015429.vfps46mvcb7io67o@anna> <04EC3D51-6242-4547-BF7F-397859E8D18E@tzi.org> <CABCOCHSEyGakhuukHkLU-bWUV26QAzc3vkOuLEMRf8-YZbFtqQ@mail.gmail.com> <27FD2DA5-AF36-4E57-ADC8-2D6F8DE62919@tzi.org> <CABCOCHSk2moVv_X90SAjHX8RyTE4XJcSGEvU4ufZnGN_eYWY=A@mail.gmail.com> <D27B5BB0-D545-46BF-B878-69C583345E73@tzi.org> <CABCOCHRNveBNYm0boZRoWhX2+SerB0=9bx+T2D89UNMQkAv_Xw@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/EeuNVavDPJV5FsbaoyyC5XGYtts>
Subject: Re: [core] [Anima] 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: Wed, 29 Jun 2022 23:12:52 -0000

> 
> Yes.  E.g, the constrained-voucher spec could define a new media type, ZANG-data+CBOR, which is defined to be almost identical to YANG-data+CBOR, except that in a few places (small matter of defining this properly, e.g., based on SIDs) the encoding deviates.
> 
> 
> There will be more optimizations that will be added over time.
> Would it be possible to use a media-type parameter to identify each of the almost-identical variants?

There could be a version number (zang-data+cbor; v=3), with increasing sets of optimizations being factored in at each version.

> I new media type for each variant seems like too much cut-and-paste.

A bit field (enumerating the powerset) would be another way, but would also be an interop testing nightmare.

Grüße, Carsten