- From: Robert Wilton via Datatracker <noreply@ietf.org>
- Date: Tue, 24 Oct 2023 05:49:28 -0700
- To: "The IESG" <iesg@ietf.org>
- Cc: draft-ietf-httpbis-alias-proxy-status@ietf.org, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, mnot@mnot.net, mnot@mnot.net
Robert Wilton has entered the following ballot position for draft-ietf-httpbis-alias-proxy-status-05: 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/about/groups/iesg/statements/handling-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-alias-proxy-status/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this document. From an RFC series perspective, I wonder whether this wouldn't have been better to put into a bis of RFC 9209 rather than a standalone RFC ... but I'm not suggesting that you change this now. One minor comment: (1) p 4, sec 2.1. Encoding special characters Upon parsing this name, "dot%5C.label" MUST be treated as a single label. Similarly the "\" character in a label MUST be escaped as "\\". I think that this is probably obvious, but possibly could state 'escaped as "\\" and then percent-encoded'. Regards, Rob
Received on Tuesday, 24 October 2023 12:49:34 UTC