I'm requesting a TAG review of Compression Dictionary Transport.

This proposal adds support for using designated previous responses as an external dictionary for HTTP responses for compression schemes that support external dictionaries (e.g. Brotli and Zstandard).

• Explainer: https://github.com/WICG/compression-dictionary-transport/blob/main/README.md
• Security and Privacy self-review: https://github.com/WICG/compression-dictionary-transport/blob/main/security-questionnaire.md
• GitHub repo (if you prefer feedback filed there): https://github.com/WICG/compression-dictionary-transport
• Primary contacts (and their relationship to the specification):
  • [Patrick Meenan] (pmeenan), [Google]
  • [Yoav Weiss] (yoavweiss), [Google]
• Organization(s)/project(s) driving the specification: Google Chrome
• External status/issue trackers for this specification: https://chromestatus.com/feature/5124977788977152

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the work on this specification is currently being done: Web Performance working group, 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): Web Performance working group, IETF HTTP working group
• Major unresolved issues with or opposition to this specification: None
• This work is being funded by: Google

You should also know that...

We are taking the lower-level HTTP pieces (headers, content encoding, negotiation) through the IETF HTTP working group to create a RFC. The browser-specific parts will be layered on top of that and be integrated into the HTML and Fetch specs.

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]