Dear Ignaz, dear Warren, As chairs of the ANIMA WG, we hereby request your AD approval for early allocation of a code point from IANA according to RFC7120.
Draft: https://tools.ietf.org/html/draft-ietf-anima-constrained-voucher-05 > ## The SMI Security for S/MIME CMS Content Type Registry > > This document registers an OID in the "SMI Security for S/MIME CMS > Content Type" registry (1.2.840.113549.1.9.16.1), with the value: > > Decimal Description References > ------- -------------------------------------- ---------- > TBD1 id-ct-animaCBORVoucher [ThisRFC] Registry: https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#security-smime-1 The ANIMA WG chairs have verified that the required conditions for early allocation from RFC7120, Section 2 are met: a) Standards Action (document is standards track ANIMA WG draft) b) The WG draft adequately describes the desired semantics: https://tools.ietf.org/html/draft-ietf-anima-constrained-voucher-05 c) The WG participants actively working on implementations of the draft have confirmed that the semantic of the code point is stable to the extend that it is clear that the final RFC will need it, but further validation through more interoperability testing is required and only blocked on the availability of an early allocation code point. d) The working group chairs think that it would be highly helpful to receive an early allocation code point now to support further interoperability testing, ensuring that the final RFC has the highest level of practical vetting. The request for early allocation was brought up in the working group and was faced with no disagreement. The working group chairs also understand that there is no risk of depletion of the registry in question. Thank you very much Toerless (for the chairs) _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
