[secdir] draft-ietf-httpbis-no-vary-search-06 ietf last call Secdir review

Corey Bonnell via Datatracker <noreply@ietf.org> Wed, 22 July 2026 17:51 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@mail2.ietf.org
Received: from [10.244.21.25] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 7EE2E11C998D7; Wed, 22 Jul 2026 10:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784742716; bh=vIDBr0F9UTvuvqwWNknmwlsP4AmxGbVNRecDqhfQvkU=; h=From:To:Cc:Subject:Reply-To:Date; b=ecHv+7xfwcuQ6Fm/vCdwHuBJeNd8+1O0G3MQ1Kn7ASrRYA+m/uZcMlLql2CVYC1Qz xMu5u0R+eO1DqldHzxp8pp8q0FjvdQHMafYyrN9e6tZeO2/CGuQMtKYp9jkP3eMAZ3 MCzXDwOoupizZYjQvCoyD67N7zcjMI2LnAJlyLv4=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Corey Bonnell via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178474271640.543100.12196993780439829682@dt-datatracker-d4d6ff9d9-fsx7d>
Date: Wed, 22 Jul 2026 10:51:56 -0700
Message-ID-Hash: CL4IPBU32H4U3XE2FCTZDIBUYXWDV4SY
X-Message-ID-Hash: CL4IPBU32H4U3XE2FCTZDIBUYXWDV4SY
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-httpbis-no-vary-search.all@ietf.org, ietf-http-wg@w3.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Corey Bonnell <dev@cbonnell.com>
Subject: [secdir] draft-ietf-httpbis-no-vary-search-06 ietf last call Secdir review
List-Id: Security Area Directorate <secdir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/TiltnNo2zz5tw4_Gy-eJfsLPX5I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Owner: <mailto:secdir-owner@ietf.org>
List-Post: <mailto:secdir@ietf.org>
List-Subscribe: <mailto:secdir-join@ietf.org>
List-Unsubscribe: <mailto:secdir-leave@ietf.org>

Document: draft-ietf-httpbis-no-vary-search
Title: The No-Vary-Search HTTP Caching Extension
Reviewer: Corey Bonnell
Review result: Has Issues

The Security Considerations say "The main risk to be aware of is the impact of
mismatched URLs", but nowhere in this document (or in any of the normative
references) is a "mismatched URL" defined. I think this section needs to
elaborate on what this is so the guidance can be understood.

However, the most significant issue is that the Security Considerations is
seemingly written from the standpoint of a web browser. Given that non-browser
technologies also may implement this specification, I would expect this section
to contain guidance for other types of caches, especially shared caches.

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.