Wide Review of 9 July WD of IFT

[svgeesus]

This meta-issue tracks the wide review of the 9 July Working Draft of IFT

The new draft addresses review feedback from the earlier proposals. There is no longer a Range Request vs Patch Subset choice, and there is no longer any special protocol required. Compared to the earlier proposals, the risks of fingerprinting have been reduced and there should no longer be an impact on CDN caching.

Because this is a substantial rewrite, we have an Explainer. For the same reason, the FPWD review of Patch Subset is now closed.

• [ ] Accessibility (see FAST checklist)
• [ ] Security (see self review answers)
• [ ] Privacy (see self review answers)
• [x] I18n (see I18n checklist) completed
• [ ] W3C Web Perf WG
• [ ] IETF HTTP WG
• [ ] TAG (after the above are completed)

[svgeesus]

A11y review requested 10 July 2024

[svgeesus]

Security review requested 10 July 2024

[svgeesus]

Privacy review requested 24 July 2024

[svgeesus]

I18n review requested 24 July 2024

[svgeesus]

Web Perf WG review requested 24 July 2024

[svgeesus]

IETF HTTP WG review requested 24 July 2024

[svgeesus]

Issue raised by IETF HTTP WG:

• https://github.com/w3c/IFT/issues/196

  Response to our request for review:

• https://lists.w3.org/Archives/Public/ietf-http-wg/2024JulSep/0076.html

[svgeesus]

Response from Yoav Weiss, WebPerf WG

[svgeesus]

I18n review completed, no issues