WGLC Review: Connect-TCP

Yes, I know the WGLC was a while ago, but I don't see that we've submitted it yet, so here we go.

1) The direction in 3.1 to use a TLS alert from the proxy to signal TCP RSTs from the server surprises me. Is the logic here to ensure that the error is reliably delivered to the client? Maybe I missed some discussion, but it might be worth mentioning the rationale in the doc.

2) Looks like we're missing normative references to Extended CONNECT in 3.2. That's an easy fix. (Filed an issue for this one.)

3) The permission for optimistic data in 4.1 for HTTP/2 and HTTP/3 is "not permitted" for HTTP/1.1 for good reason; is there a reason the draft stops short of a MUST NOT?

I think the document is in good shape, and I appreciate the work everyone has put into it until now.

Thanks,
Mike Bishop