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

Andy Bierman <andy@yumaworks.com> Wed, 29 June 2022 23:30 UTC

Return-Path: <andy@yumaworks.com>
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 7F2ABC14F746 for <core@ietfa.amsl.com>; Wed, 29 Jun 2022 16:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks.com
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 jqLw5Qry0Uwh for <core@ietfa.amsl.com>; Wed, 29 Jun 2022 16:30:17 -0700 (PDT)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 8CA0BC14792A for <core@ietf.org>; Wed, 29 Jun 2022 16:30:17 -0700 (PDT)
Received: by mail-yb1-xb2c.google.com with SMTP id d5so30731873yba.5 for <core@ietf.org>; Wed, 29 Jun 2022 16:30:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qjB0TiZM4eusBGjsjJX6xeUv/kNjn0BHMzndlmwrJQ8=; b=ljhEKPbmrqNp51zNKqYKeB5sCD93m99mxbH1CdtHgEor8nDWsW/EXuhhNsd78TcbU+ LuSnNWuOsQwlJf16MjRBtR2YGglbREFNIdMwnemLcuTT3WBGvnCK31HGqJSLUAx6rwzp KgOrRaXu10TU/1G6qJrE3KTRI/F2vd0VED2L/UbRC2IwAGxoJMp6Ufb3SYTdgSUtmYFn 4mrMxXMHDAgH1ENZ46JbMefX5QVd8dW5T09Ju0gnt3jM8gPlUcYEpHrmMU7vQOT5Ds6z sGuOf20i0gfpn5uvcKIEbaTSRap8qfGbFDVwkZ7rDhPf3M1sx71UYAZ+mTu60R2ikJlj fdOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qjB0TiZM4eusBGjsjJX6xeUv/kNjn0BHMzndlmwrJQ8=; b=iMPFqA7YcB+kb9985aThsEPHRnrsHuDQLJhX2msyoczEJKHrRjCxXgUf1/RnOYJjkx 6MXyhAdCYG2dP6ldhTNyypNOchDy8vgdihJCBjdrrCaM4YvtDuZgu4Cayi7HlG7qoUCl DqXVsoMDQ1orcSIEDeVWsxB7kNndcH6neXMPDekoiEL6oohOaasbWzqFuaEHv754ejh+ GEb87swrZAHI/KLswDMJH/uADk/2FxN5SbY8RQGuBPZN1slayByLcHDw08e8R0obnrR1 rRuY0qpzWZYC6SMwbiIgtDHS8u4soKj4UMiU2LHW64sRB0vJ7CFI2r1+2L/JC5XXtKaH XXkA==
X-Gm-Message-State: AJIora/jIWaTJIQlcF3QGrLgmYRpYiPpiEiNOqB1QKbk06Tb/T7mYTao 8o+80Mxj4xX8Dwmru5mpEnFlR/FTBs7YHizoDAbigg==
X-Google-Smtp-Source: AGRyM1s14Qq4EwTfaYexmEqlKZXLBbcsRj5BzZPICFDU3hdWSWMTBj6vvGhygnJrBhgL9lyqretsxFgN8nGZQx9lZ6k=
X-Received: by 2002:a25:df15:0:b0:66c:8c2d:7897 with SMTP id w21-20020a25df15000000b0066c8c2d7897mr6033272ybg.445.1656545416047; Wed, 29 Jun 2022 16:30:16 -0700 (PDT)
MIME-Version: 1.0
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> <396DBABC-7F5C-48B7-ADBB-39401624DD94@tzi.org>
In-Reply-To: <396DBABC-7F5C-48B7-ADBB-39401624DD94@tzi.org>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 29 Jun 2022 16:30:05 -0700
Message-ID: <CABCOCHR_uLuGDpyEvQbwLcvBTTueJDsBNyJPhRFXUFSaoDaB1g@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, anima@ietf.org, Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001409a705e29e89a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Xq_QQw-OGiht6IYGQmJqo_ZK1wA>
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:30:21 -0000

On Wed, Jun 29, 2022 at 4:12 PM Carsten Bormann <cabo@tzi.org> wrote:

> >
> > 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.
>
>
A version or variant also requires both peers to agree on the supported
subset (if any).
Maybe better to forget any parameter.



> Grüße, Carsten
>
>
>
Andy