ALPS + ACCEPT_CH HTTP/2 and HTTP/3 frames

[miketaylr]

Request for Mozilla Position on an Emerging Web Specification

• Specification Title: Client Hint Reliability
• Specifications:
  • https://tools.ietf.org/html/draft-davidben-http-client-hint-reliability (section 4 in particular)
  • https://tools.ietf.org/html/draft-vvv-httpbis-alps
  • https://tools.ietf.org/html/draft-vvv-tls-alps
  • https://github.com/WICG/client-hints-infrastructure/blob/main/reliability.md#connection-level-settings

Other information

This is complimentary to the Critical-CH request for position (https://github.com/mozilla/standards-positions/issues/479), so it may make sense to close this and consider them together. But, let's at least get it on file in case folks want to do it separately.

The Client Hint Reliability proposal is a set of features aimed at making Client Hints more reliably available and mitigating mis-matches between a site's preferences and the preferences stored in the browser. The ACCEPT_CH HTTP/2 and HTTP/3 frames, combined with the TLS ALPS extension, are a connection-level optimization to deliver the server’s Client Hint preferences in time for the first HTTP request.

[annevk]

If this was required for all cross-origin client hints it could maybe solve WICG/client-hints-infrastructure#100?

[Tanych]

Hi, we've proposed the following updates: https://groups.google.com/a/chromium.org/g/blink-dev/c/yGdMW_gsGS4/m/5Xg_Rv0jBwAJ

Thanks.