oauth2.dev

DEF

IESG

Registry Context

DEF is the JWE compression value for the DEFLATE compression algorithm.

Technical Summary

The JWE `zip` header parameter uses the case-sensitive value `DEF` to indicate that the plaintext is compressed with DEFLATE before encryption. RFC 7518 initially registered `DEF` in the JSON Web Encryption Compression Algorithms registry.

When Used

Used in a JWE Protected Header when the plaintext is compressed with DEFLATE before encryption.

Normative Requirements

Unspecified actor

MAY
1

  1. RFC 7516 - Section 4.1.3

    Use compression algorithm values other than `DEF`..

    Condition: For the JWE `zip` header parameter.

    Other values MAY be used.

JWE implementations

MUST
1

  1. RFC 7516 - Section 4.1.3

    Understand and process the `zip` header parameter..

    Condition: When processing a JWE containing the `zip` header parameter.

    This Header Parameter MUST be understood and processed by implementations.

JWE producers

MUST
1

  1. RFC 7516 - Section 4.1.3

    Integrity protect the `zip` header parameter and place it only within the JWE Protected Header..

    Condition: When using the `zip` header parameter.

    this Header Parameter MUST be integrity protected; therefore, it MUST occur only within the JWE Protected Header

OPTIONAL
1

  1. RFC 7516 - Section 4.1.3

    Include the `zip` header parameter..

    Condition: When creating a JWE.

    Use of this Header Parameter is OPTIONAL.

Registration applicants

RECOMMENDED
1

  1. RFC 7518 - Section 7.3.1

    Keep the requested compression algorithm name short, not exceeding 8 characters without a compelling reason..

    Condition: When requesting registration of a JWE compression algorithm value.

    it is RECOMMENDED that the name be short -- not to exceed 8 characters without a compelling reason to do so

Validation Guidance

warning

Warn when a requested compression algorithm name exceeds 8 characters and no compelling reason is documented.

error

Reject a JWE whose `zip` header parameter is not integrity protected or occurs outside the JWE Protected Header.

error

Verify that an implementation recognizes and processes `zip` when the parameter is present.

info

Do not require a `zip` header parameter; when it is absent, treat the plaintext as uncompressed before encryption.

Security Notes

RFC 7516 - Section 4.1.3

When present, `zip` must be integrity protected and occur only within the JWE Protected Header.

Reference

RFC7516

Details

Entry Id
DEF
Compression Algorithm Value
DEF
Compression Algorithm Description
DEFLATE
Change Controller
IESG
Reference
RFC7516