CfC to move Fetch Metadata to CR < 2025-07-16

[simoneonofri]

This is a Call for Consensus (CfC) to move Fetch Metadata as a Candidate Recommendation (CR).

This document defines a set of Fetch metadata request headers that aim to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used.

We discussed this briefly in our most recent WG meeting, with no objections raised.

To ensure everyone has an opportunity to weigh in, this issue will serve as a record of the group's decision, one way or another.

I've pre-populated this issue with reactions to make it trivial to collect a signal from folks out there in the world:

• React with👍 if you agree with the publication.
• React with 😕 if you disagree, but it's fine if we decide to proceed.
• React with 👎 if you strongly disagree with the publication.

If you register discontent with the publication, please add a comment as well so we know what we can address to remove the concern (and if you really disapprove, Formal Objections are accepted through the usual venues).

You can find the most recent editor's draft at https://www.w3.org/TR/fetch-metadata/.

Thanks!

Please respond by 2025-07-16, at which point I'll close this CfC and open an issue to coordinate the preparation.

[cc'ing @mikewest ]

[simoneonofri]

Having received no objections, I proceed

[mikewest]

cc @simon-friedberger, who asked about this in #686 (comment). Do you have what you need to push this forward, @simoneonofri, or do we need to provide you with more information? (The same question applies to CSP3, SRI2, and WebCrypto2 :) ).

[simoneonofri]

hi @mikewest, thank you for the patience, follow-up here #692