- From: Nidhi Jaju <nidhijaju@chromium.org>
- Date: Mon, 3 Aug 2026 13:20:11 +0900
- To: Dave Thaler <dthaler1968@googlemail.com>
- Cc: Corey Bonnell <dev@cbonnell.com>, ietf-http-wg@w3.org, secdir@ietf.org, last-call@ietf.org, draft-ietf-httpbis-no-vary-search.all@ietf.org, Julian Reschke <julian.reschke@gmx.de>
- Message-ID: <CAMZNYAMLnadQMMz3YPTZzZtJgG0mbM0MSqvZcjtYSvY9Ex40Zg@mail.gmail.com>
Added a reference in
https://github.com/httpwg/http-extensions/pull/3500/changes/2621dfaa74aa2453a88e75adec9e73b1640cb0e0.
Thanks!
Best,
Nidhi
On Fri, Jul 31, 2026 at 4:04 AM Dave Thaler <dthaler1968@googlemail.com>
wrote:
> Consider adding an informative reference to RFC 6943 in the security
> considerations section.
>
>
>
> Dave
>
>
>
> *From:* Nidhi Jaju <nidhijaju@chromium.org>
> *Sent:* Tuesday, July 28, 2026 1:19 AM
> *To:* Corey Bonnell <dev@cbonnell.com>
> *Cc:* ietf-http-wg@w3.org; secdir@ietf.org; last-call@ietf.org;
> draft-ietf-httpbis-no-vary-search.all@ietf.org; Julian Reschke <
> julian.reschke@gmx.de>
> *Subject:* [secdir] Re: draft-ietf-httpbis-no-vary-search-06 ietf last
> call Secdir review
>
>
>
> Hi Corey,
>
> Thank you for the review. I've uploaded a PR to address the comments here:
> https://github.com/httpwg/http-extensions/pull/3500.
> Please let me know if you have any additional feedback.
>
> Best regards,
>
> Nidhi Jaju
>
>
>
> On Thu, Jul 23, 2026 at 6:48 PM Julian Reschke <julian.reschke@gmx.de>
> wrote:
>
> Am 22.07.2026 um 19:51 schrieb Corey Bonnell via Datatracker:
> > ...
> > A few other comments outside the Security Considerations:
> > 1. Since Section 7 of this document replaces text in Section 4 of RFC
> 9111, I
> > would expect that this document updates RFC 9111. 2. Section 5.3 scopes
> the
> > algorithm to ASCII inputs ("To parse a key given an ASCII string
> keyString:"),
> > but the examples in 5.3.1 all contain non-ASCII code points.
> > ...
>
> 1) "Extends" would be less concerning. From this perspective, using an
> actual extension point would be great; but that point would be
> "Cache-Control". There are lots of components that fail for complex
> field values (right?), but maybe this would be a reason for developers
> to actually fix their code.
>
> Also, maybe it would be better if the change would be as self-contained
> as possible, such as just re-defining what "matching" means (that
> wouldn't require to patch the actual algorithm. Maybe a caching expert
> could chime in? Mark? Willy?
>
> 2. On the HTTP layer, this is all ASCII. Non-ASCII comes in only when
> things are passed up to the UA. Maybe this needs some clarification.
>
>
> Thanks for the suggestions, Julian. I've included these in the PR above.
>
>
>
> Best regards, Julian
>
>
Received on Monday, 3 August 2026 04:20:27 UTC