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

Ben Campbell's Yes on draft-ietf-httpbis-replay-03: (with COMMENT)

From: Ben Campbell <ben@nostrum.com>
Date: Wed, 06 Jun 2018 12:23:31 -0700
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-httpbis-replay@ietf.org, Patrick McManus <mcmanus@ducksong.com>, httpbis-chairs@ietf.org, mcmanus@ducksong.com, ietf-http-wg@w3.org
Message-ID: <152831301132.6390.14342116884555533700.idtracker@ietfa.amsl.com>
Ben Campbell has entered the following ballot position for
draft-ietf-httpbis-replay-03: Yes

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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-httpbis-replay/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Just some minor (mostly editorial) comments:

Substantive:

§3, item 2:  It seems odd to find "reject early data" in a list of mitigation
strategies for servers that enable early data.

Editorial and Nits:

§3, latter part: There's a tendency to use language that gives anthropomorphic
agency to inanimate objects or concepts. I find that a bit jarring. (e.g., "if
resources do elect" and "server instances need to consider"

§5.1: "An intermediary MUST use the "Early-Data" header field if it might have
forwarded the request prior to handshake completion (see Section 6.2 for
details)." - inconsistent tense. (after forwarding seems a bit late to add the
header field.)

§5.2: "425 (Too Early): Are there degrees of earliness?

§6.1: " A gateway that forwards requests that were received in early data
   MUST only do so if it knows that the origin server that receives
   those requests understands"
Consider "MUST NOT unless...". "MUST ONLY" can be ambiguous whether it means
don't do it unless the condition occurs, you are only required to do it when
the condition occurs, or you must do that and nothing else when the condition
occurs.
Received on Wednesday, 6 June 2018 19:23:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC