Skip to content

Add note about implementations that removed support for "zip" #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
selfissued wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add note about implementations that removed support for "zip" #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions draft-ietf-oauth-rfc8725bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -573,10 +573,19 @@ Note that even when used for key encryption, password-based encryption is
## Avoid Compression of Encryption Inputs {#no-compression}


Compression of data SHOULD NOT be used when creating a JWE, because
such compressed data often reveals information about the plaintext.

Compression of data SHOULD NOT be used when creating a JWE, because
such compressed data often reveals information about the plaintext,
as described in {{Kelsey}}.

Note that, in response to the guidance in {{RFC8725}},
some JWE implementations removed support for the "zip" header parameter.
This created an interoperability issue when using these implementations,
as they are incapable of processing a JWE using it.
Such implementations do not conform to {{RFC7516},
since the specification says about "zip":
"This Header Parameter MUST be understood and processed by implementations."
The guidance in {{RFC8725}} was that "zip" SHOULD NOT be used when creating a JWE;
it did not advocate removing support from implementations.


## Use UTF-8 {#use-utf8}
Expand Down Expand Up @@ -854,13 +863,16 @@ This document obsoletes RFC 8725 and provides several significant improvements a

6. Described relationship between explicit typing and kinds of JWTs not already employing it.

7. Added a note about compatibility problems with implementations that removed support for "zip".

# Document History

[[Note to RFC Editor: please remove before publication.]]

## draft-ietf-oauth-rfc8725bis-03

* Described relationship between explicit typing and kinds of JWTs not already employing it.
* Added a note about compatibility problems with implementations that removed support for "zip".

## draft-ietf-oauth-rfc8725bis-02

Expand Down