AD Review: No-Vary-Search

# AD review of draft-ietf-httpbis-no-vary-search-05

CC @MikeBishop

Overall, a very precise and well-written spec. Thanks for the work on this so far.
Only a few things I'd like to see cleaned up, and then it will be ready for Last Call.

## High-Level Points

### Query Parameters

This spec depends heavily on "query parameters," but fails to define it
or point to a definition. It looks like you're referencing the
application/x-www-form-urlencoded parser [WHATWG-URL] definition for parsing, so
you're most of the way there; you just need to associate the term with that
encoding.

### W3C/WHATWG to IETF Translation

Not surprisingly, given the history, this reads like a W3C spec.
Consider softening the reliance on FETCH/URL/HTML where you don't actually need
something that departs from RFCs 9110/3986/6454.

## Comments

### Section 3, paragraph 8

I'm not sure all IETF reviewers will be familiar with the term
"authoring conformance requirements," nor will "as always" land so well.
Consider "It has the following constraints:" and "A parsing algorithm is defined
in Section 5.2."

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Typos

#### Section 1, paragraph 4
```
-    If the specific query parameters (e.g., ones indicating something for
-      ----
```