Split into two documents - Raised by Martin Thomson

[pmeenan]

Would it be worth considering a split for Use-As-Dictionary? Or do we just need more information? I have far less confidence in that component myself.

If this all stays as experimental, a single document is fine. However, if delta encoding ends up being a slam dunk and we need more information on Use-As-Dictionary, then it might be good to take delta encoding as a proposed standard and leave Use-As-Dictionary as an experiment.

Original listserv response cc @martinthomson

Moved from private ID issue #5

[pmeenan]

It could make sense since setting the dictionary in a response doesn't have to be the only way that client's populate available dictionaries but the dictionary selection is somewhat entangled with the subsequent request.

There's a good chance that fields will need to be added to Use-As-Dictionary (I just added "type", for example, to allow for forward-compatibility with non-raw dictionaries) but some of those changes will also cascade to the content encoding. Zstandard-specific or Brotli-specific dictionary formats, for example, would require new content encodings as well as some explanation for what to send in the Accept-Encoding when using format-specific dictionaries.

listserv response

[pmeenan]

Closing this as we have been evolving the various parts of the draft together and it has been working well to keep it all combined.