[w3ctag/design-reviews] Zstandard Content-Encoding (Issue #930)

こんにちは TAG-さん!

I'm requesting a TAG review of Zstandard Content-Encoding.

Zstandard, or “zstd”, is a data compression mechanism described in [RFC8878](https://datatracker.ietf.org/doc/html/rfc8878). It is a fast lossless compression algorithm, targeting real-time compression scenarios at zlib-level and better compression ratios. The "zstd" token was added as an IANA-registered Content-Encoding token as per https://datatracker.ietf.org/doc/html/rfc8878#name-content-encoding. 

Adding browser support for "zstd" as a Content-Encoding will help load pages faster, use less bandwidth, and spend less time and CPU/power on compression on servers, resulting in reduced server costs.

  - Explainer¹ (minimally containing user needs and example code): https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/edit?usp=sharing
  - Specification URL: https://datatracker.ietf.org/doc/html/rfc8878
  - Tests: https://github.com/web-platform-tests/wpt/pull/44393
  - User research: https://https://facebook.github.io/zstd/#benchmarks
  - Security and Privacy self-review²: https://docs.google.com/document/d/1IS9g7CcGl44KCCLGS0q75KQFcPgVs56amWszELpo08g/edit?usp=sharing
  - GitHub repo (if you prefer feedback filed there): https://https://github.com/facebook/zstd
  - Primary contacts (and their relationship to the specification):
      - Nidhi Jaju (@nidhijaju), Google, Chromium support implementor
      - Felix Handte (@felixhandte), Meta, Zstd maintainer
      - Yann Collet (@Cyan4973), Meta, RFC Author & Zstd maintainer
  - Organization(s)/project(s) driving the specification: Meta, Google Chrome
  - Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification:
    - Chromium comments: [Chromium Issue](https://issues.chromium.org/issues/40196713), [Intent to Prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/GDsI0Hw-jYk/m/Yc5QZWD-AwAJ), [Intent to Experiment](https://groups.google.com/a/chromium.org/g/blink-dev/c/I6IWfl95gRU)
    - Mozilla comments: https://github.com/mozilla/standards-positions/issues/775
    - WebKit comments: https://github.com/WebKit/standards-positions/issues/168
    - Etc.
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/6186023867908096

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: Chromium is planning to ship support in M123 (branches on Feb 19, 2024).
  - The group where the work on this specification is currently being done: IETF HTTP working group
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): IETF HTTP working group
  - Major unresolved issues with or opposition to this specification: None
  - This work is being funded by: Meta, Google

You should also know that...

N/A

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify [github usernames]

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/930
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/930@github.com>