- From: Mike Bishop <mbishop@evequefou.be>
- Date: Wed, 16 Sep 2026 18:32:30 +0000
- To: "draft-ietf-httpbis-connect-tcp@ietf.org" <draft-ietf-httpbis-connect-tcp@ietf.org>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
# AD review of draft-ietf-httpbis-connect-tcp-13 CC @MikeBishop Thanks for your work on modernizing CONNECT! There's nothing blocking here, but I hope you'll consider incorporating these. Let me know when you're ready for Last Call. ## Major ### Section 7.3, paragraph 1 It is unclear to me that this draft could be implemented without a reasonably complete knowledge of how TCP works, yet [TCP] is an Informative reference. Consider making it Normative. ## Minor ### Section 3.3 A cache that sees this exchange would follow the rules in RFC 9110, which mark several 4xx codes as heuristically cacheable unless the method specifies otherwise. While CONNECT is specifically uncacheable, in HTTP/1.1 this is a GET, which is. That's obviously not desired behavior here. Consider a Section 3.3.3 on Caching Headers, suggesting (MAY/SHOULD) `Cache-Control: no-store` on any non-1xx response for HTTP/1.1. ### Section 3.4, paragraph 8 Given that draft-ietf-quic-reliable-stream-reset has been approved, it might make sense to mention it here. This is an excellent use case for it. ### Section 6, paragraph 2 It might also be worth pointing to (or mimicking) the Security Considerations of RFC 9298, particularly around sensitive endpoints and the availability of destination_ip_prohibited in Proxy-Status. ## Nits All comments below are about very minor potential issues that you may choose to address in some way - or ignore - as you see fit. Some were flagged by automated tools (via https://github.com/larseggert/ietf-reviewtool), so there will likely be some false positives. There is no need to let me know what you did with these suggestions. ### Typos #### Section 1.2, paragraph 1 ``` - Classic HTTP CONNECT requests using the proxy do not carry this - ^ + classic HTTP CONNECT requests using the proxy do not carry this + ^ ``` #### Section 6.1, paragraph 1 ``` - A malicious client can achieve cause highly asymmetric resource usage - -------- ``` ### Grammar/style #### Section 3.1, paragraph 18 ``` and Section 4.1.2 of [HTTP/3]). Additionally the "capsule-protocol" header fi ^^^^^^^^^^^^ ``` A comma may be missing after the conjunctive/linking adverb "Additionally". ## Notes This review is in the ["IETF Comments" Markdown format][ICMF]. You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT]. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments [IRT]: https://github.com/larseggert/ietf-reviewtool
Received on Wednesday, 16 September 2026 18:32:42 UTC