Hello COSE list, during some conference discussions questions about AES-OCB's usability in the context of COSE came up, and while I have no personal stakes in pushing it, I'd like to clarify:
What'd the requirements be to have some parametrizations of AES-OCB as an AEAD mechanism in COSE? We do have concrete parametrizations and a suitable description already in RFC 7253, where they are registered into the AEAD parameters registry. Can AEADs that are already in there be easily transferred into COSE Algorithms when needed (and if so, into which range)? If this were aiming at the 1+1-byte range (standards action with specification required), would the existing RFC suffice? Would a document (for >256, not necessarily standards track) that enters it need to say anything more than that IANA is requested to do the actions, and that the AEAD is already sufficiently described in 7253? Best regards Christian
signature.asc
Description: PGP signature
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
