The "Use of Hybrid Public-Key Encryption (HPKE) with JSON Object Signing and Encryption (JOSE)<https://www.ietf.org/archive/id/draft-ietf-jose-hpke-encrypt-08.html>" specification has updated to incorporate feedback from IETF 122 in Bangkok<https://datatracker.ietf.org/meeting/122/proceedings>.
Per the History entries, the changes were: * Use "enc":"int" for integrated encryption. * Described the reasons for excluding authenticated HPKE. * Stated that mutually known private information MAY be used as the HPKE info value. At this point, the authors have closed all the issues and PRs<https://github.com/ietf-wg-jose/draft-ietf-jose-hpke-encrypt> that we believe there's consensus to address. I would normally suggest that we're ready for working group last call at this point, but I'd like us to take the extra step to verify that the spec is aligned with the COSE HPKE<https://datatracker.ietf.org/doc/draft-ietf-cose-hpke/> spec first. Both as an author of the JOSE HPKE spec and as a COSE chair interested in the COSE HPKE spec, I'd request that members of both working groups review the specs together and send their feedback. -- Mike P.S. I also posted about this at https://self-issued.info/?p=2657 and made supporting posts at https://x.com/selfissued/status/1915925844645843325 and https://www.linkedin.com/posts/selfissued_hybrid-public-key-encryption-hpke-for-jose-activity-7321693628085559297-9D54/.
_______________________________________________ jose mailing list -- [email protected] To unsubscribe send an email to [email protected]
