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

Carsten Bormann <cabo@tzi.org> Tue, 28 June 2022 20:51 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABCOCHQqtKw6cZ1o7nzDmQBN0zQP70CgeAAc6nFdRa_kB+-DBQ@mail.gmail.com>
Date: Tue, 28 Jun 2022 22:50:57 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Core <core@ietf.org>, anima@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <09C66776-54C5-4C5D-9DFA-E164A1050170@tzi.org>
References: <DU0P190MB1978F90B0893D32291F6EE7DFDB99@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <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>
To: Andy Bierman <andy@yumaworks.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/iq0fvp6Z6YqPgQmkhBEMy4dU-T8>
Subject: Re: [core] date-and-time and "created-on" field in constrained-voucher
Precedence: list

On 2022-06-28, at 22:22, Andy Bierman <andy@yumaworks.com> wrote:
> 
> During operation, the optimized encoding is used for any objects with the
> data type.  E.g., tag X for date-and-time, tag Y for ipv4-address, tag Z for ipv6-address.
> The receiver is responsible for converting the special encoding to the correct format
> for the YANG data type.  Storage and exposure of the optimized format are possible,
> but (perhaps) not required.

Do I actually know that a yang item “has” that data type (*)?
It actually could “have” multiple of them (and usually has both a base type and at least one typedef).
Just wondering.

The alternative would be to trigger on the data, so any string that looks like 2022-06-28T20:48:15Z would turn into 1(1656449295).  That has some interesting security considerations, though.

Grüße, Carsten

(*) I.e., name equivalence as opposed to structural equivalence.
Many YANG types are defined via a regexp (pattern)…

[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