Carl Wallace <[email protected]> wrote: > How does “eContentType of 40” work given the first two elements of an > OID are encoded in one byte?
Yeah, so the text in RFC8366 ad RFC8366bis:
An eContentType of 40 indicates that the content is a JSON-encoded voucher.
is way too concise, and yeah, confusing. Later on, in IANA Considerations,
it gives the entire OID:
## The SMI Security for S/MIME CMS Content Type Registry
IANA has registered the OID 1.2.840.113549.1.9.16.1.40,
id-ct-animaJSONVoucher.
This registration should be updated to point to this document.
How does:
An OID for JSON-encoded voucher is allocated in {{iana-contenttype}}, and
it is to be placed in the eContentType.
work for you?
--
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]
