Esko Dijk <[email protected]> wrote: > We had some past 2022 discussions on using a simple CBOR uint timestamp > value (in seconds) in the constrained Voucher. The conclusion of this > discussion was that such timestamp needed to be in a new field, not in > "created-on", because that field is already defined by YANG/YANG-cbor > as a date-time string. Most of the discussion was then about how it > could be modeled in YANG such that consistent translations between > string format and uint/float format can be done. But, that's complex as > it turns out.
> Sorry to bring this topic up again!
Sorry to bring out a 12 month-old email.
Trying to empty inbox.
We could change the YANG from:
leaf created-on {
type yang:date-and-time;
to:
type union {
type uint64; // when serialized to CBOR
type yang:date-and-time; // when serialized to JSON
}
If there is a YANG data type which is seconds-since-unix-epoch, I'm unaware
of it. We are in WGLC, so is this something you want to make a blocking
comment?
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
