- From: Tommy Jensen via Datatracker <noreply@ietf.org>
- Date: Thu, 20 Aug 2026 00:12:19 -0700
- To: "The IESG" <iesg@ietf.org>
- Cc: draft-ietf-httpbis-no-vary-search@ietf.org, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, tpauly@apple.com
Tommy Jensen has entered the following ballot position for
draft-ietf-httpbis-no-vary-search-09: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.
The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-httpbis-no-vary-search/
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
+1 to everyone concerned with external reference stability. Given the extent to
which you rely on WHATWG docs, I think that must be addressed (but I'm not
going to force a DISCUSS because I'm confident that signal has made it through,
pending telechat discussion).
Minor note:
Note that no Unicode normalization is performed during this
comparison. For example, a query string of ?a=%C3%A9 (using the NFC
encoding of é) and ?a=e%CC%81 (using the NFD encoding of é) will not
be treated as equivalent.
Not questioning this decision, but it would a nice gesture to the reader to
explain why, even super briefly ("because it's unnecessary complexity when one
encoding is super uncommon" or "the complexity isn't worth trying to defend
against worst case 2x results" or whatever your rationale is).
Received on Thursday, 20 August 2026 07:12:23 UTC