We ran into some interop issues with draft-ietf-anima-constrained-voucher. This document makes use of draft-ietf-core-yang-cbor and draft-ietf-core-yang-sid.
1. I had assumed that less code meant that the voucher request from
Registrar to MASA would be in the same SID-compressed format as from Pledge
to Registrar.
One implementation uses the uncompressed, SID-free, name format from
yang-cbor
for the RVR, even though the contained-within PVR is in SID-format.
In later yang-cbor document versions I thought that mostly we were saying
doing (A:SID) or (B:NAMES), but never mix. This is not really a MIX
situation, but
I guess I am thinking we should pick one or the other.
I think that I can convince my implementation to process both formats.
It might just work as is, but I need to test it.
I am concerned that this is needless liberalism in what we accept, and that
the
https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-07.html#name-ecosystem-effects
would apply.
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.
Section 6, where I might expect to see info about encoding dates:
https://www.ietf.org/archive/id/draft-ietf-core-yang-cbor-20.html#name-representing-yang-data-type
is silent about date and time formats.
https://github.com/core-wg/yang-cbor/issues/144
3. the third interop issue is a fault of mine where I encoded a binary object
as a string. Oops.
--
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
