Michael Richardson <[email protected]> wrote: > 2. The other thing we ran into was that the CBOR implementation I'm using, when given a > DateTime object naturally produces a RFC 8949 Section 3.4.2 compliant "tag 1" marked Epoch-Based > Date/Time. And demarshalls this. So I don't really notice.
> But, draft-ietf-core-yang-cbor doesn't say much about
"yang:date-and-time".
> The only reference seems to be at:
>
https://www.ietf.org/archive/id/draft-ietf-core-yang-cbor-20.html#name-the-container-and-other-nod
> where date-and-time is shown as part of a container object.
> The Content is defined to be string date pattern.
"created-on"=>"2022-06-17T09:21:32.299Z"
We don't need this much precision either, so I wonder if we can forbid it.
--
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] https://www.ietf.org/mailman/listinfo/anima
