W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

WGLC: p4 MUSTs

From: Alex Rousskov <rousskov@measurement-factory.com>
Date: Tue, 30 Apr 2013 18:33:14 -0600
Message-ID: <518062CA.6030301@measurement-factory.com>
To: IETF HTTP WG <ietf-http-wg@w3.org>
Hello,

    These comments are based on the "latest" snapshot dated Tue 30 Apr
2013 06:59:03 AM MDT at
https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p4-conditional.html

I hope these comments can be addressed by editors alone.


> The If-Match condition is met if and only if any of the entity-tags
> listed in the If-Match field value match the entity-tag of the
> selected representation using the weak comparison function (as per
> Section 2.3.2), or if "*" is given and any current representation
> exists for the target resource.

The "if and only if ... or if ..." construction looks funny. It is kind
of correct because the first part applies to the non-* condition and the
second part applies to the * condition, but still... Please consider
dropping either "and only if" or the "if" in "or if".

Can a proxy with an empty cache determine whether "any current
representation exists for the target resource" without forwarding the
request to the origin server? In other words, does "exists" mean "exists
in the proxy cache" or "exists on the origin server"? Perhaps you can
add some test to clarify the scope of resource existence here from the
caching proxy point of view.

The same two concerns apply to the If-None-Match section.




Here is a list of requirement-like statements that seem to be missing
MUST/SHOULD/MAY keywords to make them formal requirements and indicate
the level of those requirements:

> Preconditions are ignored if the server determines that an error or
> redirect response applies before they are evaluated.

> The conditional request header fields defined by this specification
> are ignored for request methods that never involve the selection or
> modification of a selected representation

> The general rule of conditional precedence is that exact match
> conditions are ...

> Specifically, the fields defined by this specification are evaluated
> as follows:

Please consider rephrasing the above using RFC 2119 keywords and, where
applicable, giving them explicit actors.


Thank you,

Alex.
Received on Wednesday, 1 May 2013 00:33:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:10 UTC