Andy Bierman <[email protected]> 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? It sure seems like a major omission in yang-cbor, which is yes, approved, but is just AUTH48 today... (Noting that revising RFC8366 *is* on our agenda, just order of operations, we didn't think we'd have to do that first) -- 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
