JWE and Argon2id
| Field | Value |
|---|---|
| Status | Adopt |
| Version pinned | RFC 7516 (May 2015); RFC 9106 (September 2021) |
| Source | https://www.rfc-editor.org/rfc/rfc7516 |
| What is taken | Passphrase-encrypted export |
| Why | Standard envelope encryption for the portable export, with a maintained memory-hard key derivation |
| What is extended or replaced | None |
| Specification home | A11.2 |
Version pinned
- RFC 7516, JSON Web Encryption, May 2015, Proposed Standard.
- RFC 9106, Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications, September 2021, Informational (IRTF CFRG).
What is taken
The optional encrypted export (A11.2): compact JWE with alg:dir and enc:A256GCM, and a 32-byte key derived with Argon2id version 19, memory 65,536 KiB, three iterations, four lanes and a fresh 16-byte salt, carried in the authenticated critical header autonym_kdf.
Why
A person moving a record needs it encrypted at rest with a passphrase, using primitives with maintained implementations.
What is extended
Nothing beyond the autonym_kdf critical header, which carries the single permitted parameter set. Argon2id is not a JOSE alg.
What is replaced or not used
No other key-management algorithm or KDF is accepted.
Deviations
None.
Conformance checks
PORT-01, and ENCRYPT-01 for the optional encrypted-export feature, in the conformance manifest, with runtime evidence pending.
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.