Skip to content
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.

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

Remove paragraph about decoders being able to support a different limit #3

Merged
merged 1 commit into from
Mar 14, 2024
Merged
Changes from all commits
Commits
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
4 changes: 0 additions & 4 deletions draft-jaju-httpbis-zstd-window-size.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,10 +108,6 @@ MUST support window sizes of up to and including 8 MB and encoders MUST NOT
generate frames requiring a window size of larger than 8 MB, when using the
"zstd" Content Encoding token (see {{zstd-iana-token}}).

Decoders are free to support higher or lower limits, depending on local
limitations, if negotiated out-of-band. Many deployments of Zstandard operate in controlled, private environments and can directly communicate with their encoder
and decoder to negotiate a higher or lower limit.

# Security Considerations

This document introduces no new security considerations beyond those discussed
Expand Down
Loading