Re: Working Group Last Call: draft-ietf-httpbis-no-vary-search

Am 30.09.2025 um 05:20 schrieb Tommy Pauly:
> Hello HTTP,
> 
> This email starts a Working Group Last Call for draft-ietf-httpbis-no- 
> vary-search-03.
> ...

I found the first part of 
https://www.ietf.org/archive/id/draft-ietf-httpbis-no-vary-search-03.html#name-caching 
a bit hard to understand with respect to what is replaced by what.

See (text version):

> 7.  Caching
> 
>    If a cache [HTTP-CACHING] implements this specification, the
>    presented target URI requirement in Section 4 of [HTTP-CACHING] is
>    replaced with:
> 
>    *  one of the following:
> 
>       -  the presented target URI (Section 7.1 of [HTTP]) and that of
>          the stored response match, or
> 
>       -  the presented target URI and that of the stored response are
>          equivalent modulo search variance (Section 6), given the
>          variance obtained (Section 5.2) from the stored response.


Proposal: make both list items quotes; simplify the replacement text so 
that it does not require more nesting, and do not lose the ", and" at 
the end.

Like that:

> -If a cache {{HTTP-CACHING}} implements this specification, the presented target URI requirement in {{Section 4 of HTTP-CACHING}} is replaced with:
> +If a cache {{HTTP-CACHING}} implements this specification, the presented target URI requirement in  {{Section 4 of HTTP-CACHING}}:
> 
> -* one of the following:
> -  * the presented target URI ({{Section 7.1 of HTTP}}) and that of the stored response match, or
> -  * the presented target URI and that of the stored response are equivalent modulo search variance ({{comparing}}), given the variance obtained ({{obtain-a-url-search-variance}}) from the stored response.
> +> the presented target URI (Section 7.1 of [HTTP]) and that of the stored response match, and
> +{:quote}
> +
> +is replaced with:
> +
> +> the presented target URI (Section 7.1 of [HTTP]) and that of the stored response match or are equivalent modulo search variance, and
> +{:quote}

And yes, the replacement text is likely less precise now, but that could 
be fixed by adding the precise definition somewhere else where it could 
be linked to.

Best regards, Julian

Received on Tuesday, 14 October 2025 14:22:05 UTC