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

Andy Bierman <andy@yumaworks.com> Tue, 28 June 2022 03:16 UTC

MIME-Version: 1.0
References: <DU0P190MB1978F90B0893D32291F6EE7DFDB99@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <24048.1656352364@localhost> <25937.1656365067@localhost> <CABCOCHS6=F0tfESkVmOk1AFKvsu4tRfKu9A_Sgz5swVXv-eXCQ@mail.gmail.com> <26870.1656383550@localhost>
In-Reply-To: <26870.1656383550@localhost>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 27 Jun 2022 20:16:13 -0700
Message-ID: <CABCOCHSkh95PEEM5E3YKe_yc5VmsY90XxT1D-z3AiJwwcG-HhA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Core <core@ietf.org>, anima@ietf.org
Content-Type: multipart/alternative; boundary="00000000000019641705e27976b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/gNXuZK_FnYSTLOVx9BU_BcVbkdE>
Subject: Re: [core] date-and-time and "created-on" field in constrained-voucher
Precedence: list

On Mon, Jun 27, 2022 at 7:32 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> 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?
>
>
not that I know about



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

I am not in favor of the YANG-CBOR draft defining special encodings for
1 derived type (like date-and-time).  Implementations may not store the
named YANG typedefs defined in various YANG modules.
The current draft (properly) addresses only the base types, not derived
types.



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

Andy


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

[core] date-and-time and "created-on" field in co… Michael Richardson
Re: [core] date-and-time and "created-on" field i… Michael Richardson
Re: [core] date-and-time and "created-on" field i… Andy Bierman
Re: [core] date-and-time and "created-on" field i… Michael Richardson
Re: [core] date-and-time and "created-on" field i… Michael Richardson
Re: [core] date-and-time and "created-on" field i… Andy Bierman
Re: [core] date-and-time and "created-on" field i… Michael Richardson
Re: [core] date-and-time and "created-on" field i… Carsten Bormann
Re: [core] date-and-time and "created-on" field i… Andy Bierman
Re: [core] date-and-time and "created-on" field i… Carsten Bormann
Re: [core] date-and-time and "created-on" field i… Andy Bierman
Re: [core] date-and-time and "created-on" field i… Jürgen Schönwälder
Re: [core] date-and-time and "created-on" field i… Andy Bierman
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] [Anima] date-and-time and "created-on"… Jürgen Schönwälder
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] date-and-time and "created-on" field i… Michael Richardson
Re: [core] [Anima] date-and-time and "created-on"… Andy Bierman
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] [Anima] date-and-time and "created-on"… Andy Bierman
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] [Anima] date-and-time and "created-on"… Andy Bierman
Re: [core] [Anima] date-and-time and "created-on"… Carsten Bormann
Re: [core] [Anima] date-and-time and "created-on"… Andy Bierman