Thank you Brian, As DE:
I was (not for the first time either mind you) being reminded that such feedback would not be acceptable from a DE review during IETF Last Call. That being said, I did reach out to the authors off list about the exact point you're making during my review (and I did throw in HPKE-4 and HPKE-6 too on the account of limiting the number of choices), asking how strongly they feel about them. Here are the excerpts from the existing Designated Experts instructions we are asked to follow. The point about general applicability stands out but there isn't anything special about the particular algorithms in question that would make them useful only to a subset of applications. --- Criteria that should be applied by the Designated Experts include determining whether the proposed registration duplicates existing functionality, whether it is likely to be of general applicability or useful only for a single application, and whether the registration description is clear. ... The Designated Experts should perform reasonable due diligence that algorithms being registered either are currently considered cryptographically credible or are being registered as Deprecated or Prohibited. ... Only fully-specified algorithm identifiers may be registered. Polymorphic algorithm identifiers must not be registered. As individual WG member: I do think that, unless someone is anxious to get their hands on ChaCha in JOSE through HPKE right now?, then all of these, alongside "enc":"C20P" and HPKE PQ & PQ/T ones, could be bunched together in a "ChaCha20-Poly1305 for JOSE" document instead. Should've brought it up during WGLC but alas I was so happy we finally got the HPKE Key Management modes in a good shape that I didn't. S pozdravem, *Filip Skokan* On Mon, 18 May 2026 at 14:53, Brian Campbell <[email protected]> wrote: > I've not been designated an expert here but I do dabble in the field. I > disagree with Filip about this being fine. I believe it's irresponsible to > unnecessarily expand the algorithm registry with unneeded and confusing > options. As stated here > https://mailarchive.ietf.org/arch/msg/jose/NUo-HG2WgtQVVKlExn2EbQafdRU/ I > suggest dropping HPKE-4-KE and HPKE-6-KE from the document entirely. > > On Thu, May 14, 2026 at 10:53 AM Filip Skokan <[email protected]> wrote: > >> Hello David, yes this is fine. >> >> S pozdravem, >> *Filip Skokan* >> >> >> On Wed, 13 May 2026 at 23:47, David Dong via RT < >> [email protected]> wrote: >> >>> Dear Sean Turner, Filip Skokan (cc: Mike Jones, jose WG), >>> >>> As the designated experts for the JSON Web Signature and Encryption >>> Algorithms and JSON Web Key Parameters registries, can you review the >>> proposed registrations in draft-ietf-jose-hpke-encrypt-17 for us? Please >>> note that Mike Jones is an author on this document. >>> >>> Please see: >>> >>> https://datatracker.ietf.org/doc/draft-ietf-jose-hpke-encrypt/ >>> >>> The due date is June 3rd. >>> >>> If this is OK, when the IESG approves the document for publication, >>> we'll make the registrations at: >>> >>> https://www.iana.org/assignments/jose/ >>> >>> When the review is complete (or, if you have concerns that need to be >>> addressed, when the initial review is complete), we'll update the >>> Datatracker's "IANA expert review" state and send any comments to the >>> authors. We'll wait one week after the first review we receive to act >>> unless told otherwise. >>> >>> With thanks, >>> >>> David Dong >>> IANA Services Sr. Specialist >>> >> _______________________________________________ >> jose mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > > *CONFIDENTIALITY NOTICE: This email may contain confidential and > privileged material for the sole use of the intended recipient(s). Any > review, use, distribution or disclosure by others is strictly prohibited. > If you have received this communication in error, please notify the sender > immediately by e-mail and delete the message and any file attachments from > your computer. Thank you.*
_______________________________________________ jose mailing list -- [email protected] To unsubscribe send an email to [email protected]
