Adding COSE list to say... These labels will show up in the COSE registry as well, but their length will not be an issue, since the assigned integer will be used instead.
I'm supportive of shorter registered names if we can land them. >From RFC7518 - https://datatracker.ietf.org/doc/html/rfc7518#section-1 "Names defined by this specification are short because a core goal is for the resulting representations to be compact." Later in, in the registration template: https://datatracker.ietf.org/doc/html/rfc7518#section-7.3.1 "Because a core goal of this specification is for the resulting representations to be compact, it is RECOMMENDED that the name be short -- not to exceed 8 characters without a compelling reason to do so." OS On Fri, Dec 6, 2024 at 2:15 AM Neil Madden <[email protected]> wrote: > On 5 Dec 2024, at 20:15, Michael Jones <[email protected]> > wrote: > > > > Please see the discussion in the issue > https://github.com/ietf-wg-jose/draft-ietf-jose-hpke-encrypt/issues/8 > (*Algorithm > identifiers like HPKE-P256-SHA256-A128GCM are overly verbose*) and add > your thoughts there. > > > > > Given that one of the primary motivators of HPKE is use of post-quantum > KEMs, I’d have thought the length of the algorithm identifiers was the > least of the size issues. Even the smallest ML-KEM ciphertexts are over 1KB > when base64-encoded. A few bytes for an algorithm identifier seems neither > here nor there. > > — Neil > _______________________________________________ > jose mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
