Visual RFC.
ALL RFCs / RFC 7516
Read the RFC ↗
RFC 7516 / MECHANISMS

Content keys and recipient keys

02

A content-encryption key protects the payload; a selected key-management mode establishes that key.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.1 ↗
RFC 7516 · § 5.1EXAMPLE
3 / 3
Content keys and recipient keysA content-encryption key protects the payload; a selected key-management mode establishes that key. Current state: Encrypt content.Content keys and recipient keysCEKrecipient keywrap CEKencrypted keycontent → ciphertextWrapped CEK example; direct and key-agreement modes differ.
03
Encrypt content

Use the CEK with the content-encryption algorithm.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

alg describes key management; enc describes content encryption.

  • alg describes key management; enc describes content encryption.
  • Key management may wrap, encrypt, agree on, or directly use a key according to the algorithm.
  • The illustration uses a wrapped CEK; not every JWE mode has an encrypted-key value.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Five compact parts
  2. Content keys and recipient keys
  3. Associated data is checked too
  4. Several recipients, one ciphertext
  5. Decryption must authenticate
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗