- From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
- Date: Tue, 12 Oct 2021 12:37:29 -0700
- To: "The IESG" <iesg@ietf.org>
- Cc: draft-ietf-httpbis-proxy-status@ietf.org, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, tpauly@apple.com, tpauly@apple.com
Benjamin Kaduk has entered the following ballot position for draft-ietf-httpbis-proxy-status-07: No Objection 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/blog/handling-iesg-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-httpbis-proxy-status/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the updates in the -07; they look good. Two remarks on the new content in the -07: In Section 2.1.1 the prose accompanying the example that uses a 429 response code mentions "the reverse proxy", but the Proxy-Status list members in the example have been changed to no longer mention "SomeReverseProxy" in favor of an example hostname specific to a given deployment. The template for the proxy error types registry (Section 2.4), as well as the initial registry contents in Sections 2.3.x, use the phrase "Only generated by intermediaries". My apologies if I made this comment already and it was discarded, but that phrasing is easy to misread as saying that the *error* was only generated by intermediaries, when the intent is that the (possibly partial) response content was only generated by intermediaries. So I'd consider adding "response", for "Response only generated by intermediaries" (or similar) to forestall such confusion.
Received on Tuesday, 12 October 2021 19:37:44 UTC