The IESG has received a request from the Javascript Object Signing and
Encryption WG (jose) to consider the following document: - 'Use of Hybrid
Public Key Encryption (HPKE) with JSON Web Encryption
   (JWE)'
  <draft-ietf-jose-hpke-encrypt-22.txt> as Proposed Standard

This is a second Last Call for draft-ietf-jose-hpke-encrypt. After the recent 
IESG telechat, with the input of the AD, and based on concerns raised during 
IETF Last Call, it was decided to remove the HPKE-4-KE and HPKE-6-KE algorithms 
(JOSE doesn't have a ChaCha20/Poly1305 content encryption algorithm 
registered). This IETF Last Call is ensure IETF consensus to update these 
registry options.  Section 6, and Section 11.1 have been updated, removing 
these two options.

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[email protected] mailing lists by 2026-08-03. Exceptionally, comments may
be sent to [email protected] instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This specification defines how to use Hybrid Public Key Encryption
   (HPKE) with JSON Web Encryption (JWE).  HPKE enables public key
   encryption of arbitrary-sized plaintexts to a recipient's public key,
   and provides security against adaptive chosen ciphertext attacks.
   This specification chooses a specific subset of the HPKE features to
   use with JWE.

   This specification updates RFC 7516 (JWE) to enable use of Integrated
   Encryption as a Key Management Mode.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-jose-hpke-encrypt/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc8937: Randomness Improvements for Security Protocols (Informational - 
Internet Research Task Force (IRTF) stream)




_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to