<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 4.0.7) -->
<?rfc-ext html-pretty-print="prettyprint https://cdn.rawgit.com/google/code-prettify/master/loader/run_prettify.js"?>
<rfc xmlns:x="http://purl.org/net/xml2rfc/ext"
     category="std"
     consensus="true"
     docName="draft-ietf-httpbis-connect-tcp-latest"
     ipr="trust200902"
     sortRefs="true"
     submissionType="IETF"
     symRefs="true"
     tocInclude="true">
   <x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22\&amp;amp;body=%3c{ref}%3e:"/>
   <front>
      <title abbrev="CONNECT-TCP">Template-Driven HTTP CONNECT Proxying for TCP</title>
      <author fullname="Benjamin M. Schwartz" initials="B. M." surname="Schwartz">
         <organization>Meta Platforms, Inc.</organization>
         <address>
            <email>ietf@bemasc.net</email>
         </address>
      </author>
      <date day="14" month="November" year="2026"/>
      <area>wit</area>
      <workgroup>httpbis</workgroup>
      <abstract><?line 45?>
         <t>TCP tunneling using HTTP CONNECT has long been part of the core HTTP specification. However, this tunneling functionality has several important deficiencies due to the lack of a well-defined HTTP origin or path. This specification remedies those deficiencies by defining CONNECT-TCP, an alternative protocol for tunneling TCP in HTTP. A proxy service for this protocol is described by a URI Template, similar to the CONNECT-UDP and CONNECT-IP protocols.</t>
      </abstract>
   </front>
   <middle><?line 49?>
      <section anchor="introduction">
         <name>Introduction</name>
         <section anchor="history">
            <name>History</name>
            <t>HTTP has used the CONNECT method for tunneling TCP connections since HTTP/1.1. When using CONNECT, the request target specifies a host and port number, and the proxy forwards TCP payloads between the client and the target destination (<xref section="9.3.6" sectionFormat="comma" target="RFC9110"/>). Prior to this specification, this was the only mechanism defined for proxying TCP over HTTP. In this specification, this arrangement is referred to as a "classic HTTP CONNECT proxy".</t>
            <t>HTTP/3 <xref target="RFC9114"/> uses a UDP transport, so it cannot be forwarded using the pre-existing CONNECT mechanism. To enable forward proxying of HTTP/3, the MASQUE effort has defined proxy mechanisms that are capable of tunneling UDP datagrams <xref target="CONNECT-UDP"/>, and more generally IP datagrams <xref target="CONNECT-IP"/>. The destination host and port number (if applicable) are encoded into the HTTP resource path, and end-to-end datagrams are wrapped into HTTP Datagrams <xref target="CAPSULE"/> on the client-proxy path.</t>
         </section>
         <section anchor="problems">
            <name>Problems</name>
            <t>HTTP clients can be configured to use proxies by selecting a proxy hostname, a port number, and whether to use a security protocol. However, classic HTTP CONNECT requests using the proxy do not carry this configuration information. Instead, they only indicate the hostname and port of the target. This prevents any HTTP server from hosting multiple distinct proxy services, as the server cannot distinguish them by path (as with distinct resources) or by origin (as in "virtual hosting").</t>
            <t>The absence of an explicit origin for the proxy also rules out the usual defenses against server port misdirection attacks (see <xref section="7.4" sectionFormat="of" target="RFC9110"/>) and creates ambiguity about the use of origin-scoped response header fields (e.g., Alt-Svc <xref target="ALT-SVC"/> or Strict-Transport-Security <xref target="HSTS"/>).</t>
            <t>Classic HTTP CONNECT requests are not extensible to carry in-stream metadata. For example, the WRAP_UP capsule <xref target="I-D.ietf-httpbis-wrap-up"/> cannot be used with classic HTTP CONNECT.</t>
         </section>
         <section anchor="overview">
            <name>Overview</name>
            <t>This specification describes an alternative mechanism for tunneling TCP in HTTP. Like <xref target="CONNECT-UDP"/> and <xref target="CONNECT-IP"/>, the proxy service is identified by a URI Template. Proxy interactions reuse standard HTTP components and semantics, avoiding changes to the core HTTP protocol.</t>
         </section>
      </section>
      <section anchor="conventions-and-definitions">
         <name>Conventions and Definitions</name>
         <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/>
            <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
         <?line -18?>
         <t>In this document, the term "proxy" refers to the HTTP server that acts upon a client's TCP tunneling request. If there are HTTP intermediaries (as defined in Section 3.7 of [HTTP]) between the client and the proxy, those are referred to as "intermediaries" or "gateways" in this document.</t>
         <t>The term "endpoint" describes an implementation of this specification in either client or proxy role.</t>
         <t>The protocol defined in this specification is termed "CONNECT-TCP".</t>
         <t>The term "CONNECT-TCP proxy" refers to a proxy that is identified by a URI Template for CONNECT-TCP.</t>
      </section>
      <section anchor="specification">
         <name>Specification</name>
         <t>A template-driven TCP transport proxy for HTTP is identified by a URI Template <xref target="RFC6570"/> containing variables named "target_host" and "target_port". This URI Template and its variable values <bcp14>MUST</bcp14> meet all the same requirements as for UDP proxying (Sections <xref section="2" sectionFormat="bare" target="CONNECT-UDP"/> and <xref section="3" sectionFormat="bare" target="CONNECT-UDP"/> of <xref target="CONNECT-UDP"/>), and are subject to the same validation rules. Clients <bcp14>MUST</bcp14> substitute the destination host and port number into this template to produce a request URI. The derived URI serves as the destination of a Capsule Protocol connection using the Upgrade Token "connect-tcp" (see registration in <xref target="new-upgrade-token"/>).</t>
         <t>If the request is well-formed and permissible, the proxy <bcp14>MUST</bcp14> attempt to establish the TCP connection before sending a final success or failure response.</t>
         <section anchor="payload-transport">
            <name>Payload Transport</name>
            <t>When using CONNECT-TCP, TCP payload data is sent in the payload of new Capsule Types named DATA and FINAL_DATA (see <xref target="fig-capsules"/> and registrations in <xref target="data-capsule"/>). The ordered concatenation of these capsule payloads, which <bcp14>MAY</bcp14> be empty, represents the TCP payload data. A FINAL_DATA capsule additionally indicates that the sender has closed this stream, semantically equivalent to TCP FIN. After sending a FINAL_DATA capsule, an endpoint <bcp14>MUST NOT</bcp14> send any more DATA or FINAL_DATA capsules on this data stream. See <xref target="closing-connections"/> for related requirements.</t>
            <figure anchor="fig-capsules"
                    title="DATA and FINAL_DATA Capsule Formats, using notation from Section 1.3 of [QUIC]">
               <artwork>
DATA Capsule {
  Type (i) = 0x08,
  Length (i),  # may be zero
  TCP Payload (..),
}

FINAL_DATA Capsule {
  Type (i) = 0x09,
  Length (i),  # may be zero
  TCP Payload (..),
}
</artwork>
            </figure>
            <t>The boundaries between DATA and FINAL_DATA capsules are not significant, and are not expected to match TCP segments, TLS records, HTTP DATA frames, QUIC STREAM frames, etc. Recipients <bcp14>SHOULD</bcp14> begin forwarding payload from a DATA or FINAL_DATA capsule without waiting to receive the entire capsule, especially if the capsule is large.</t>
            <t>An intermediary <bcp14>MAY</bcp14> merge and split successive DATA and FINAL_DATA capsules, subject to the following requirements:</t>
            <t>
               <list style="symbols">
                  <t>There are no intervening capsules of other types.</t>
                  <t>The order of payload content is preserved.</t>
                  <t>The final emitted capsule uses the same capsule type (DATA or FINAL_DATA) as the final input capsule, and all others use the DATA capsule type.</t>
               </list>
            </t>
            <t>For example, an intermediary holding two successive DATA capsules in its transmission buffer could merge them, saving at least 2 bytes of encapsulation overhead when they are forwarded.</t>
            <t>This protocol supports backward-compatible extensions via additional Capsule Types, as described in <xref section="3.2" sectionFormat="of" target="CAPSULE"/>.</t>
         </section>
         <section anchor="in-http11">
            <name>In HTTP/1.1</name>
            <t>In HTTP/1.1 <xref target="RFC9112"/>, the client uses the proxy by issuing a request as follows:</t>
            <t>
               <list style="symbols">
                  <t>The method <bcp14>SHALL</bcp14> be GET.</t>
                  <t>The request's target <bcp14>SHALL</bcp14> correspond to the URI derived from expansion of the proxy's URI Template.</t>
                  <t>The request <bcp14>SHALL</bcp14> include a single Host header field whose value identifies the proxy.</t>
                  <t>The request <bcp14>SHALL</bcp14> include a Connection header field with the value "Upgrade". (Note that this requirement is case-insensitive as per <xref section="7.6.1" sectionFormat="of" target="RFC9110"/>.)</t>
                  <t>The request <bcp14>SHALL</bcp14> include an Upgrade header field with the value "connect-tcp".</t>
                  <t>The request <bcp14>SHOULD</bcp14> include a "Capsule-Protocol: ?1" header field (as recommended in <xref section="3.4" sectionFormat="comma" target="CAPSULE"/>).</t>
               </list>
            </t>
            <t>If the TCP connection is successful, the response <bcp14>SHALL</bcp14> be as follows:</t>
            <t>
               <list style="symbols">
                  <t>The HTTP status code <bcp14>SHALL</bcp14> be 101 (Switching Protocols).</t>
                  <t>The response <bcp14>SHALL</bcp14> include a Connection header field with the value "Upgrade".</t>
                  <t>The response <bcp14>SHALL</bcp14> include a single Upgrade header field with the value "connect-tcp".</t>
                  <t>The response <bcp14>SHOULD</bcp14> include a "Capsule-Protocol: ?1" header field (as above).</t>
               </list>
            </t>
            <t>If a TCP connection was not established, the proxy <bcp14>MUST NOT</bcp14> switch protocols to CONNECT-TCP, and the client <bcp14>MAY</bcp14> reuse this connection for additional HTTP requests.</t>
            <figure title="CONNECT-TCP in HTTP/1.1: Example request for a connection to 192.0.2.1:443 via https://example.com/proxy{?target_host,target_port}">
               <sourcecode type="http-message">
GET /proxy?target_host=192.0.2.1&amp;target_port=443 HTTP/1.1
Host: example.com
Connection: Upgrade
Upgrade: connect-tcp
Capsule-Protocol: ?1
</sourcecode>
            </figure>
            <figure title="CONNECT-TCP in HTTP/1.1: Initial response">
               <sourcecode type="http-message">
HTTP/1.1 100 Continue
</sourcecode>
            </figure>
            <figure title="CONNECT-TCP in HTTP/1.1: Final success response">
               <sourcecode type="http-message">
HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Upgrade: connect-tcp
Capsule-Protocol: ?1
Proxy-Status: example.com
</sourcecode>
            </figure>
         </section>
         <section anchor="in-http2-and-http3">
            <name>In HTTP/2 and HTTP/3</name>
            <t>In HTTP/2 and HTTP/3, the proxy <bcp14>MUST</bcp14> include SETTINGS_ENABLE_CONNECT_PROTOCOL in its SETTINGS frame <xref target="RFC8441"/>
               <xref target="RFC9220"/>. The client uses the proxy by issuing an "extended CONNECT" request as follows:</t>
            <t>
               <list style="symbols">
                  <t>The :method pseudo-header field <bcp14>SHALL</bcp14> be CONNECT.</t>
                  <t>The :protocol pseudo-header field <bcp14>SHALL</bcp14> be "connect-tcp".</t>
                  <t>The :authority pseudo-header field <bcp14>SHALL</bcp14> contain the authority of the proxy.</t>
                  <t>The :path and :scheme pseudo-header fields <bcp14>SHALL</bcp14> contain the path and scheme of the request URI derived from the proxy's URI Template.</t>
               </list>
            </t>
            <t>A CONNECT-TCP request that does not conform to all of these requirements represents a client error (see <xref section="15.5" sectionFormat="comma" target="RFC9110"/>) and may be malformed (see <xref section="8.1.1" sectionFormat="of" target="RFC9113"/> and <xref section="4.1.2" sectionFormat="of" target="RFC9114"/>).</t>
            <t>Additionally, the Capsule-Protocol header field <bcp14>SHOULD</bcp14> be present with a value of "?1" (as recommended in <xref section="3.4" sectionFormat="comma" target="CAPSULE"/>).</t>
            <figure title="CONNECT-TCP in HTTP/2: Example request to [2001:db8::1]:443">
               <artwork>
HEADERS
:method = CONNECT
:scheme = https
:authority = example.com
:path = /proxy?target_host=2001%3Adb8%3A%3A1&amp;target_port=443
:protocol = connect-tcp
capsule-protocol = ?1
...
</artwork>
            </figure>
         </section>
         <section anchor="use-of-other-relevant-headers">
            <name>Use of Other Relevant Headers</name>
            <section anchor="origin-scoped-headers">
               <name>Origin-scoped Headers</name>
               <t>Ordinary HTTP headers apply only to the single resource identified in the request or response. An origin-scoped HTTP header is a special response header that is intended to change the client's behavior for subsequent requests to any resource on this origin.</t>
               <t>Unlike classic HTTP CONNECT proxies, a CONNECT-TCP proxy has an unambiguous origin of its own. Origin-scoped headers apply to this origin when they are associated with a CONNECT-TCP response. Here are some origin-scoped headers that could potentially be sent by a CONNECT-TCP proxy:</t>
               <t>
                  <list style="symbols">
                     <t>Alt-Svc <xref target="ALT-SVC"/>
                     </t>
                     <t>Strict-Transport-Security <xref target="HSTS"/>
                     </t>
                     <t>Accept-CH <xref target="RFC8942"/>
                     </t>
                     <t>Set-Cookie <xref target="RFC6265"/>, which has configurable scope.</t>
                     <t>Clear-Site-Data <xref target="CLEAR-SITE-DATA"/>
                     </t>
                  </list>
               </t>
            </section>
            <section anchor="authentication-headers">
               <name>Authentication Headers</name>
               <t>Authentication to a CONNECT-TCP proxy normally uses ordinary HTTP authentication via the 401 (Unauthorized) response code, the WWW-Authenticate response header field, and the Authorization request header field (<xref section="11.6" sectionFormat="comma" target="RFC9110"/>). A CONNECT-TCP proxy does not use the 407 (Proxy Authentication Required) status code and related header fields (<xref section="11.7" sectionFormat="comma" target="RFC9110"/>) because they do not traverse HTTP gateways (see <xref target="gateway-compatibility"/>).</t>
               <t>Clients <bcp14>SHOULD</bcp14> assume that all proxy resources generated by a single template share a protection space (i.e., a realm) (<xref section="11.5" sectionFormat="comma" target="RFC9110"/>). For many authentication schemes, this will allow the client to avoid waiting for a 401 (Unauthorized) response before each new connection through the proxy.</t>
               <t>TLS Client Certificate authentication can also be used (see <xref target="gateway-compatibility"/>).</t>
            </section>
            <section anchor="caching-headers">
               <name>Caching Headers</name>
               <t>In HTTP/2 and HTTP/3, this specification uses the CONNECT method, which is not subject to caching (<xref section="9.3.6" sectionFormat="comma" target="RFC9110"/>). However, in HTTP/1.1, the method is GET, which in other usages can be cacheable. To minimize discrepancies between HTTP versions, the following requirements apply when using HTTP/1.1:</t>
               <t>
                  <list style="symbols">
                     <t>If the response has a heuristically cacheable status code (<xref section="15.1" sectionFormat="comma" target="RFC9110"/>), it <bcp14>SHOULD</bcp14> also carry a "Cache-Control: no-store" header field (<xref section="5.2" sectionFormat="comma" target="HTTP-CACHING"/>). <list style="symbols">
                           <t>This can occur if the request is rejected or the connection fails.</t>
                        </list>
                     </t>
                     <t>The proxy <bcp14>SHOULD NOT</bcp14> attach any other caching-related header fields to the response.</t>
                  </list>
               </t>
            </section>
         </section>
         <section anchor="closing-connections">
            <name>Closing Connections</name>
            <t>Connection termination is essentially symmetrical for proxies and their clients, which we refer to here as the "endpoints" of a request.</t>
            <t>When closing connections, endpoints are subject to the following requirements:</t>
            <t>
               <list style="symbols">
                  <t>When an endpoint receives a valid TCP FIN, it <bcp14>MUST</bcp14> send a FINAL_DATA capsule.</t>
                  <t>When an endpoint receives a valid FINAL_DATA capsule, it <bcp14>MUST</bcp14> send a TCP FIN.</t>
                  <t>When a TCP connection reaches the TIME-WAIT or CLOSED state, the associated endpoint <bcp14>MUST</bcp14> close its send stream. <list style="symbols">
                        <t>If the connection closed gracefully, the endpoint <bcp14>MUST</bcp14> close the send stream gracefully.</t>
                        <t>Otherwise, the endpoint <bcp14>SHOULD</bcp14> close the send stream abruptly, using a mechanism appropriate to the HTTP version: <list style="symbols">
                              <t>HTTP/3: reset the stream with H3_CONNECT_ERROR; see <xref section="19.4" sectionFormat="comma" target="QUIC"/> and <xref section="8.1" sectionFormat="comma" target="RFC9114"/>.</t>
                              <t>HTTP/2: reset the stream with CONNECT_ERROR; see <xref target="RFC9113"/>, Sections <xref target="RFC9113" x:fmt="number" x:sec="6.4"/> and <xref target="RFC9113" x:fmt="number" x:sec="7"/>.</t>
                              <t>HTTP/1.1 over TLS: TCP shutdown without a TLS closure alert; see <xref section="6.1" sectionFormat="comma" target="TLS"/>.</t>
                              <t>HTTP/1.1 without TLS: TCP RST.</t>
                           </list>
                        </t>
                     </list>
                  </t>
                  <t>When the receive stream is closed abruptly or without a FINAL_DATA capsule received, the endpoint <bcp14>SHOULD</bcp14> send a TCP RST if the TCP subsystem permits it.</t>
               </list>
            </t>
            <t>Any locally imposed timeout (<xref target="timeouts"/>) <bcp14>MUST</bcp14> be treated as an abrupt closure of the affected stream or connection.</t>
            <t>The mandatory behaviors above enable endpoints to detect any truncation of incoming TCP data. The recommended behaviors propagate any TCP errors through the tunnel.</t>
            <t>In HTTP/3, endpoints <bcp14>MAY</bcp14> negotiate and use the RESET_STREAM_AT frame in order to reduce data loss during an abrupt closure <xref target="I-D.ietf-quic-reliable-stream-reset"/>. However, RESET_STREAM_AT may not be very effective in this case, as TCP implementations will typically discard pending data when a RST is received.</t>
            <figure title="Simple graceful termination example (HTTP/3)">
               <artset>
                  <artwork type="svg">
                     <svg xmlns="http://www.w3.org/2000/svg"
                          class="diagram"
                          font-family="monospace"
                          font-size="13px"
                          height="176"
                          stroke-linecap="round"
                          text-anchor="middle"
                          version="1.1"
                          viewBox="0 0 480 176"
                          width="480">
                        <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
                        <path d="M 24,64 L 24,160" fill="none" stroke="black"/>
                        <path d="M 72,32 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,32 L 112,64" fill="none" stroke="black"/>
                        <path d="M 128,64 L 128,160" fill="none" stroke="black"/>
                        <path d="M 216,32 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,32 L 264,64" fill="none" stroke="black"/>
                        <path d="M 352,64 L 352,160" fill="none" stroke="black"/>
                        <path d="M 368,32 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,32 L 408,64" fill="none" stroke="black"/>
                        <path d="M 456,64 L 456,160" fill="none" stroke="black"/>
                        <path d="M 472,32 L 472,64" fill="none" stroke="black"/>
                        <path d="M 8,32 L 72,32" fill="none" stroke="black"/>
                        <path d="M 112,32 L 216,32" fill="none" stroke="black"/>
                        <path d="M 264,32 L 368,32" fill="none" stroke="black"/>
                        <path d="M 408,32 L 472,32" fill="none" stroke="black"/>
                        <path d="M 8,64 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,64 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,64 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,64 L 472,64" fill="none" stroke="black"/>
                        <path d="M 24,80 L 48,80" fill="none" stroke="black"/>
                        <path d="M 96,80 L 192,80" fill="none" stroke="black"/>
                        <path d="M 288,80 L 376,80" fill="none" stroke="black"/>
                        <path d="M 424,80 L 448,80" fill="none" stroke="black"/>
                        <path d="M 24,96 L 56,96" fill="none" stroke="black"/>
                        <path d="M 88,96 L 176,96" fill="none" stroke="black"/>
                        <path d="M 296,96 L 384,96" fill="none" stroke="black"/>
                        <path d="M 416,96 L 448,96" fill="none" stroke="black"/>
                        <path d="M 32,112 L 56,112" fill="none" stroke="black"/>
                        <path d="M 88,112 L 176,112" fill="none" stroke="black"/>
                        <path d="M 296,112 L 384,112" fill="none" stroke="black"/>
                        <path d="M 416,112 L 456,112" fill="none" stroke="black"/>
                        <path d="M 136,128 L 168,128" fill="none" stroke="black"/>
                        <path d="M 304,128 L 352,128" fill="none" stroke="black"/>
                        <path d="M 24,144 L 48,144" fill="none" stroke="black"/>
                        <path d="M 104,144 L 168,144" fill="none" stroke="black"/>
                        <path d="M 304,144 L 344,144" fill="none" stroke="black"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,96 444,90.4 444,101.6"
                                 transform="rotate(0,448,96)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,80 444,74.4 444,85.6"
                                 transform="rotate(0,448,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="368,112 356,106.4 356,117.6"
                                 transform="rotate(180,360,112)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,144 340,138.4 340,149.6"
                                 transform="rotate(0,344,144)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,96 340,90.4 340,101.6"
                                 transform="rotate(0,344,96)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,80 340,74.4 340,85.6"
                                 transform="rotate(0,344,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="144,128 132,122.4 132,133.6"
                                 transform="rotate(180,136,128)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="144,112 132,106.4 132,117.6"
                                 transform="rotate(180,136,112)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,144 116,138.4 116,149.6"
                                 transform="rotate(0,120,144)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,96 116,90.4 116,101.6"
                                 transform="rotate(0,120,96)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,80 116,74.4 116,85.6"
                                 transform="rotate(0,120,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="40,112 28,106.4 28,117.6"
                                 transform="rotate(180,32,112)"/>
                        <g class="text">
                           <text x="32" y="52">TCP</text>
                           <text x="56" y="52">A</text>
                           <text x="156" y="52">Endpoint</text>
                           <text x="200" y="52">A</text>
                           <text x="308" y="52">Endpoint</text>
                           <text x="352" y="52">B</text>
                           <text x="432" y="52">TCP</text>
                           <text x="456" y="52">B</text>
                           <text x="72" y="84">"abc"</text>
                           <text x="240" y="84">DATA{"abc"}</text>
                           <text x="400" y="84">"abc"</text>
                           <text x="72" y="100">FIN</text>
                           <text x="236" y="100">FINAL_DATA{""}</text>
                           <text x="400" y="100">FIN</text>
                           <text x="72" y="116">FIN</text>
                           <text x="236" y="116">FINAL_DATA{""}</text>
                           <text x="400" y="116">FIN</text>
                           <text x="236" y="132">QUIC.STREAM{FIN}</text>
                           <text x="76" y="148">FINACK</text>
                           <text x="236" y="148">QUIC.STREAM{FIN}</text>
                        </g>
                     </svg>
                  </artwork>
                  <artwork type="ascii-art">
+-------+    +------------+     +------------+    +-------+
| TCP A |    | Endpoint A |     | Endpoint B |    | TCP B |
+-+-----+    +-+----------+     +----------+-+    +-----+-+
  +---"abc"---&gt;+--------DATA{"abc"}-------&gt;+---"abc"---&gt;|
  +----FIN----&gt;+------FINAL_DATA{""}------&gt;+----FIN----&gt;|
  |&lt;---FIN-----+&lt;-----FINAL_DATA{""}-------+&lt;---FIN-----+
  |            |&lt;----QUIC.STREAM{FIN}------+            |
  +---FINACK--&gt;+-----QUIC.STREAM{FIN}-----&gt;|            |
  |            |                           |            |
</artwork>
               </artset>
            </figure>
            <figure title="Simple TCP RST termination example (HTTP/2)">
               <artset>
                  <artwork type="svg">
                     <svg xmlns="http://www.w3.org/2000/svg"
                          class="diagram"
                          font-family="monospace"
                          font-size="13px"
                          height="112"
                          stroke-linecap="round"
                          text-anchor="middle"
                          version="1.1"
                          viewBox="0 0 480 112"
                          width="480">
                        <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
                        <path d="M 24,64 L 24,96" fill="none" stroke="black"/>
                        <path d="M 72,32 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,32 L 112,64" fill="none" stroke="black"/>
                        <path d="M 128,64 L 128,96" fill="none" stroke="black"/>
                        <path d="M 216,32 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,32 L 264,64" fill="none" stroke="black"/>
                        <path d="M 352,64 L 352,96" fill="none" stroke="black"/>
                        <path d="M 368,32 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,32 L 408,64" fill="none" stroke="black"/>
                        <path d="M 456,64 L 456,96" fill="none" stroke="black"/>
                        <path d="M 472,32 L 472,64" fill="none" stroke="black"/>
                        <path d="M 8,32 L 72,32" fill="none" stroke="black"/>
                        <path d="M 112,32 L 216,32" fill="none" stroke="black"/>
                        <path d="M 264,32 L 368,32" fill="none" stroke="black"/>
                        <path d="M 408,32 L 472,32" fill="none" stroke="black"/>
                        <path d="M 8,64 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,64 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,64 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,64 L 472,64" fill="none" stroke="black"/>
                        <path d="M 24,80 L 56,80" fill="none" stroke="black"/>
                        <path d="M 88,80 L 160,80" fill="none" stroke="black"/>
                        <path d="M 320,80 L 384,80" fill="none" stroke="black"/>
                        <path d="M 416,80 L 448,80" fill="none" stroke="black"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,80 444,74.4 444,85.6"
                                 transform="rotate(0,448,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,80 340,74.4 340,85.6"
                                 transform="rotate(0,344,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,80 116,74.4 116,85.6"
                                 transform="rotate(0,120,80)"/>
                        <g class="text">
                           <text x="32" y="52">TCP</text>
                           <text x="56" y="52">A</text>
                           <text x="156" y="52">Endpoint</text>
                           <text x="200" y="52">A</text>
                           <text x="308" y="52">Endpoint</text>
                           <text x="352" y="52">B</text>
                           <text x="432" y="52">TCP</text>
                           <text x="456" y="52">B</text>
                           <text x="72" y="84">RST</text>
                           <text x="240" y="84">RST_STREAM{CON_ERR}</text>
                           <text x="400" y="84">RST</text>
                        </g>
                     </svg>
                  </artwork>
                  <artwork type="ascii-art">
+-------+    +------------+     +------------+    +-------+
| TCP A |    | Endpoint A |     | Endpoint B |    | TCP B |
+-+-----+    +-+----------+     +----------+-+    +-----+-+
  +----RST----&gt;+----RST_STREAM{CON_ERR}---&gt;+----RST----&gt;|
  |            |                           |            |
</artwork>
               </artset>
            </figure>
            <figure title="Timeout example (HTTP/1.1)">
               <artset>
                  <artwork type="svg">
                     <svg xmlns="http://www.w3.org/2000/svg"
                          class="diagram"
                          font-family="monospace"
                          font-size="13px"
                          height="144"
                          stroke-linecap="round"
                          text-anchor="middle"
                          version="1.1"
                          viewBox="0 0 480 144"
                          width="480">
                        <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
                        <path d="M 24,64 L 24,128" fill="none" stroke="black"/>
                        <path d="M 72,32 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,32 L 112,64" fill="none" stroke="black"/>
                        <path d="M 128,64 L 128,128" fill="none" stroke="black"/>
                        <path d="M 216,32 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,32 L 264,64" fill="none" stroke="black"/>
                        <path d="M 352,64 L 352,128" fill="none" stroke="black"/>
                        <path d="M 368,32 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,32 L 408,64" fill="none" stroke="black"/>
                        <path d="M 456,64 L 456,128" fill="none" stroke="black"/>
                        <path d="M 472,32 L 472,64" fill="none" stroke="black"/>
                        <path d="M 8,32 L 72,32" fill="none" stroke="black"/>
                        <path d="M 112,32 L 216,32" fill="none" stroke="black"/>
                        <path d="M 264,32 L 368,32" fill="none" stroke="black"/>
                        <path d="M 408,32 L 472,32" fill="none" stroke="black"/>
                        <path d="M 8,64 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,64 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,64 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,64 L 472,64" fill="none" stroke="black"/>
                        <path d="M 24,80 L 48,80" fill="none" stroke="black"/>
                        <path d="M 96,80 L 192,80" fill="none" stroke="black"/>
                        <path d="M 288,80 L 376,80" fill="none" stroke="black"/>
                        <path d="M 424,80 L 448,80" fill="none" stroke="black"/>
                        <path d="M 128,112 L 144,112" fill="none" stroke="black"/>
                        <path d="M 328,112 L 384,112" fill="none" stroke="black"/>
                        <path d="M 416,112 L 448,112" fill="none" stroke="black"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,112 444,106.4 444,117.6"
                                 transform="rotate(0,448,112)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,80 444,74.4 444,85.6"
                                 transform="rotate(0,448,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,112 340,106.4 340,117.6"
                                 transform="rotate(0,344,112)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,80 340,74.4 340,85.6"
                                 transform="rotate(0,344,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,80 116,74.4 116,85.6"
                                 transform="rotate(0,120,80)"/>
                        <g class="text">
                           <text x="32" y="52">TCP</text>
                           <text x="56" y="52">A</text>
                           <text x="156" y="52">Endpoint</text>
                           <text x="200" y="52">A</text>
                           <text x="308" y="52">Endpoint</text>
                           <text x="352" y="52">B</text>
                           <text x="432" y="52">TCP</text>
                           <text x="456" y="52">B</text>
                           <text x="72" y="84">"abc"</text>
                           <text x="240" y="84">DATA{"abc"}</text>
                           <text x="400" y="84">"abc"</text>
                           <text x="172" y="100">(...</text>
                           <text x="224" y="100">timeout</text>
                           <text x="264" y="100">@</text>
                           <text x="280" y="100">A</text>
                           <text x="308" y="100">...)</text>
                           <text x="160" y="116">FIN</text>
                           <text x="192" y="116">(no</text>
                           <text x="264" y="116">close_notify)</text>
                           <text x="400" y="116">RST</text>
                        </g>
                     </svg>
                  </artwork>
                  <artwork type="ascii-art">
+-------+    +------------+     +------------+    +-------+
| TCP A |    | Endpoint A |     | Endpoint B |    | TCP B |
+-+-----+    +-+----------+     +----------+-+    +-----+-+
  +---"abc"---&gt;+--------DATA{"abc"}-------&gt;+---"abc"---&gt;|
  |            |   (... timeout @ A ...)   |            |
  |            +--FIN (no close_notify) --&gt;+----RST----&gt;|
  |            |                           |            |
</artwork>
               </artset>
            </figure>
            <figure title="RST after FIN example (HTTP/3)">
               <artset>
                  <artwork type="svg">
                     <svg xmlns="http://www.w3.org/2000/svg"
                          class="diagram"
                          font-family="monospace"
                          font-size="13px"
                          height="192"
                          stroke-linecap="round"
                          text-anchor="middle"
                          version="1.1"
                          viewBox="0 0 480 192"
                          width="480">
                        <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
                        <path d="M 24,64 L 24,176" fill="none" stroke="black"/>
                        <path d="M 72,32 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,32 L 112,64" fill="none" stroke="black"/>
                        <path d="M 128,64 L 128,176" fill="none" stroke="black"/>
                        <path d="M 216,32 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,32 L 264,64" fill="none" stroke="black"/>
                        <path d="M 352,64 L 352,176" fill="none" stroke="black"/>
                        <path d="M 368,32 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,32 L 408,64" fill="none" stroke="black"/>
                        <path d="M 456,64 L 456,176" fill="none" stroke="black"/>
                        <path d="M 472,32 L 472,64" fill="none" stroke="black"/>
                        <path d="M 8,32 L 72,32" fill="none" stroke="black"/>
                        <path d="M 112,32 L 216,32" fill="none" stroke="black"/>
                        <path d="M 264,32 L 368,32" fill="none" stroke="black"/>
                        <path d="M 408,32 L 472,32" fill="none" stroke="black"/>
                        <path d="M 8,64 L 72,64" fill="none" stroke="black"/>
                        <path d="M 112,64 L 216,64" fill="none" stroke="black"/>
                        <path d="M 264,64 L 368,64" fill="none" stroke="black"/>
                        <path d="M 408,64 L 472,64" fill="none" stroke="black"/>
                        <path d="M 24,80 L 64,80" fill="none" stroke="black"/>
                        <path d="M 96,80 L 184,80" fill="none" stroke="black"/>
                        <path d="M 304,80 L 392,80" fill="none" stroke="black"/>
                        <path d="M 424,80 L 448,80" fill="none" stroke="black"/>
                        <path d="M 32,128 L 56,128" fill="none" stroke="black"/>
                        <path d="M 104,128 L 168,128" fill="none" stroke="black"/>
                        <path d="M 312,128 L 384,128" fill="none" stroke="black"/>
                        <path d="M 432,128 L 456,128" fill="none" stroke="black"/>
                        <path d="M 136,144 L 168,144" fill="none" stroke="black"/>
                        <path d="M 304,144 L 352,144" fill="none" stroke="black"/>
                        <path d="M 24,160 L 64,160" fill="none" stroke="black"/>
                        <path d="M 96,160 L 168,160" fill="none" stroke="black"/>
                        <path d="M 304,160 L 392,160" fill="none" stroke="black"/>
                        <path d="M 424,160 L 448,160" fill="none" stroke="black"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,160 444,154.4 444,165.6"
                                 transform="rotate(0,448,160)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="456,80 444,74.4 444,85.6"
                                 transform="rotate(0,448,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="368,128 356,122.4 356,133.6"
                                 transform="rotate(180,360,128)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,160 340,154.4 340,165.6"
                                 transform="rotate(0,344,160)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="352,80 340,74.4 340,85.6"
                                 transform="rotate(0,344,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="144,144 132,138.4 132,149.6"
                                 transform="rotate(180,136,144)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="144,128 132,122.4 132,133.6"
                                 transform="rotate(180,136,128)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,160 116,154.4 116,165.6"
                                 transform="rotate(0,120,160)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="128,80 116,74.4 116,85.6"
                                 transform="rotate(0,120,80)"/>
                        <polygon class="arrowhead"
                                 fill="black"
                                 points="40,128 28,122.4 28,133.6"
                                 transform="rotate(180,32,128)"/>
                        <g class="text">
                           <text x="32" y="52">TCP</text>
                           <text x="56" y="52">A</text>
                           <text x="156" y="52">Endpoint</text>
                           <text x="200" y="52">A</text>
                           <text x="308" y="52">Endpoint</text>
                           <text x="352" y="52">B</text>
                           <text x="432" y="52">TCP</text>
                           <text x="456" y="52">B</text>
                           <text x="80" y="84">FIN</text>
                           <text x="244" y="84">FINAL_DATA{""}</text>
                           <text x="408" y="84">FIN</text>
                           <text x="80" y="116">(FIN)</text>
                           <text x="408" y="116">(FIN)</text>
                           <text x="80" y="132">"abc"</text>
                           <text x="240" y="132">FINAL_DATA{"abc"}</text>
                           <text x="408" y="132">"abc"</text>
                           <text x="236" y="148">QUIC.STREAM{FIN}</text>
                           <text x="80" y="164">RST</text>
                           <text x="236" y="164">H3_CONNECT_ERROR</text>
                           <text x="408" y="164">RST</text>
                        </g>
                     </svg>
                  </artwork>
                  <artwork type="ascii-art">
+-------+    +------------+     +------------+    +-------+
| TCP A |    | Endpoint A |     | Endpoint B |    | TCP B |
+-+-----+    +-+----------+     +----------+-+    +-----+-+
  +-----FIN---&gt;+-------FINAL_DATA{""}-----&gt;+-----FIN---&gt;|
  |            |                           |            |
  |    (FIN)   |                           |    (FIN)   |
  |&lt;---"abc"---+&lt;----FINAL_DATA{"abc"}-----+&lt;---"abc"---+
  |            |&lt;----QUIC.STREAM{FIN}------+            |
  +-----RST---&gt;+-----H3_CONNECT_ERROR-----&gt;+-----RST---&gt;|
  |            |                           |            |
</artwork>
               </artset>
            </figure>
            <section anchor="handling-invalid-data">
               <name>Handling Invalid Data</name>
               <t>An endpoint that receives invalid data from its peer is subject to the same requirements as when receiving an abrupt closure of the receive stream (see <xref target="closing-connections"/>). Some examples of invalid data include:</t>
               <t>
                  <list style="symbols">
                     <t>A second FINAL_DATA capsule.</t>
                     <t>A DATA capsule after FINAL_DATA.</t>
                     <t>Data that results in a parsing error under the Capsule Protocol.</t>
                     <t>A capsule that is truncated by the end of the stream.</t>
                     <t>A capsule that would require unreasonable effort to process.</t>
                  </list>
               </t>
               <t>Note that very large DATA and FINAL_DATA capsules are still valid, as they can be forwarded incrementally using a bounded memory buffer.</t>
            </section>
         </section>
      </section>
      <section anchor="additional-connection-setup-behaviors">
         <name>Additional Connection Setup Behaviors</name>
         <t>This section discusses some behaviors that are permitted or recommended in order to enhance the performance or functionality of connection setup.</t>
         <section anchor="latency-optimizations">
            <name>Latency Optimizations</name>
            <t>When using this specification in HTTP/2 or HTTP/3, clients <bcp14>MAY</bcp14> start sending TCP stream content optimistically, subject to flow control limits (<xref section="5.2" sectionFormat="of" target="RFC9113"/> or <xref section="4.1" sectionFormat="of" target="QUIC"/>). Proxies <bcp14>MUST</bcp14> buffer this "optimistic" content until the TCP stream becomes writable, and discard it if the TCP connection fails.</t>
            <t>Clients <bcp14>MUST NOT</bcp14> use "optimistic" behavior in HTTP/1.1, as this would interfere with reuse of the connection after an error response such as 401 (Unauthorized).</t>
            <t>Servers that host a proxy under this specification <bcp14>MAY</bcp14> offer support for TLS early data in accordance with <xref target="RFC8470"/>. Clients <bcp14>MAY</bcp14> send CONNECT-TCP requests in early data, and <bcp14>MAY</bcp14> include "optimistic" TCP content in early data (in HTTP/2 and HTTP/3). At the TLS layer, proxies <bcp14>MAY</bcp14> ignore, reject, or accept the <spanx style="verb">early_data</spanx> extension (<xref section="4.3.10" sectionFormat="comma" target="TLS"/>). At the HTTP layer, proxies <bcp14>MAY</bcp14> process the request immediately, return a 425 (Too Early) response (<xref section="5.2" sectionFormat="comma" target="RFC8470"/>), or delay some or all processing of the request until the handshake completes. For example, a proxy with limited anti-replay defenses might choose to perform DNS resolution of <spanx style="verb">target_host</spanx> when a request arrives in early data, but delay the TCP connection until the TLS handshake completes.</t>
            <t>When DNS resolution of <spanx style="verb">target_host</spanx> produces IP addresses from multiple address families, proxies <bcp14>SHOULD</bcp14> use a racing procedure such as Happy Eyeballs <xref target="HEv2"/> to accelerate connection establishment. Proxies that race multiple connection attempts <bcp14>MUST</bcp14> buffer any optimistic content until a connection is selected and <bcp14>MUST NOT</bcp14> transmit any payload data on the other connections.</t>
         </section>
         <section anchor="indicating-failure">
            <name>Indicating Failure</name>
            <t>Failure to initiate a tunnel is indicated by the HTTP status code.</t>
            <t>A 4xx status code indicates that the request is malformed or impermissible. For example, if the proxy performs DNS resolution of <spanx style="verb">target_host</spanx> and receives an IP address that is disallowed by the proxy's policy, it might return 403 (Forbidden).</t>
            <t>A 5xx status code indicates a failure in the attempt, such as when a TCP connection was attempted but did not succeed. The 502 (Bad Gateway) and 504 (Gateway Timeout) status codes are commonly used.</t>
            <t>The 429 (Too Many Requests) and 503 (Service Unavailable) status codes indicate a temporary failure, and can carry a Retry-After response header field (<xref section="10.2.3" sectionFormat="comma" target="RFC9110"/>). If included, this field applies to all requests using this URI Template.</t>
         </section>
         <section anchor="conveying-metadata">
            <name>Conveying Metadata</name>
            <t>This specification supports the 100 (Continue) status code (<xref section="15.2.1" sectionFormat="comma" target="RFC9110"/>) in any HTTP version. Proxies <bcp14>SHOULD</bcp14> send this status code whenever they accept a request, without waiting for the proxy-destination TCP handshake to succeed or fail. This allows for a few useful improvements:</t>
            <t>
               <list style="symbols">
                  <t>Clients can provide a clearer status indication while waiting for the destination host to respond. (TCP handshakes can hang for several minutes before failing.)</t>
                  <t>Clients can apply separate timeouts to the tunneling request and connection establishment.</t>
                  <t>In HTTP/2 and HTTP/3, clients have the option to delay some or all of the optimistic payload data until after confirming that the request is permissible. This strategy reduces wasted effort when the request is rejected.</t>
               </list>
            </t>
            <t>Note that a client in this specification cannot send an "Expect: 100-continue" request header field, because the request does not include any "content" (<xref section="10.1.1" sectionFormat="comma" target="RFC9110"/>).</t>
            <t>Proxies implementing this specification <bcp14>SHOULD</bcp14> include a Proxy-Status response header field <xref target="PROXY-STATUS"/> in any success or failure response (i.e., status codes 101, 2xx, 4xx, or 5xx) to support advanced client behaviors and diagnostics. Clients and proxies <bcp14>MUST NOT</bcp14> send trailer fields on CONNECT-TCP streams.</t>
         </section>
      </section>
      <section anchor="applicability">
         <name>Applicability</name>
         <section anchor="servers">
            <name>Servers</name>
            <t>For server operators, CONNECT-TCP proxies are particularly valuable in situations where virtual-hosting is needed, or where multiple proxies must share an origin. For example, the proxy might benefit from sharing an HTTP gateway that provides DDoS defense, performs request sanitization, or enforces user authorization (<xref target="gateway-compatibility"/>).</t>
            <t>CONNECT-TCP proxies can also be made invisible to probes from unauthorized clients:</t>
            <t>
               <list style="symbols">
                  <t>The URI template can include a high-entropy path, similar to Capability URLs <xref target="CAPABILITY"/>.</t>
                  <t>The proxy can require HTTP Concealed Authentication (<xref section="6.4" sectionFormat="comma" target="CONCEALED"/>).</t>
               </list>
            </t>
         </section>
         <section anchor="clients">
            <name>Clients</name>
            <t>This specification does not require any specific type of configuration input. Suitable configuration input types include:</t>
            <t>
               <list style="symbols">
                  <t>A URI Template string, as described in <xref target="specification"/>.</t>
                  <t>An IP address or hostname, with optional or required port and scheme (as often used to describe classic HTTP CONNECT proxies). A corresponding CONNECT-TCP proxy might be found in two ways: <list style="symbols">
                        <t>At the default template for "connect-tcp" (<xref target="fig-default"/>).</t>
                        <t>In the "proxies" array of a provisioning domain resource retrieved from the corresponding ".well-known" URI (Sections <xref section="2"
                                 sectionFormat="bare"
                                 target="I-D.ietf-intarea-proxy-config"/> and <xref section="3"
                                 sectionFormat="bare"
                                 target="I-D.ietf-intarea-proxy-config"/> of <xref target="I-D.ietf-intarea-proxy-config"/>).</t>
                     </list>
                  </t>
                  <t>A provisioning domain resource, configured directly or identified by a local or remote URI (e.g., using "file://" or "https://").</t>
               </list>
            </t>
            <figure anchor="fig-default" title="Registered default template">
               <artwork>
https://$PROXY_HOST:$PROXY_PORT/.well-known/masque
                 /tcp/{target_host}/{target_port}/
</artwork>
            </figure>
            <t>All of these input types <bcp14>MAY</bcp14> share a single input string, as they can be disambiguated reliably by parsing and probing. However, it may be preferable to indicate the configuration input type explicitly, to reduce probing delays while supporting clients with differing capabilities.</t>
            <t>Clients <bcp14>SHOULD</bcp14> treat certain errors during classic HTTP CONNECT as indications that the proxy might only support CONNECT-TCP:</t>
            <t>
               <list style="symbols">
                  <t>In HTTP/1.1: the response's status code is 426 (Upgrade Required), with an "Upgrade: connect-tcp" response header.</t>
                  <t>In any HTTP version: the response's status code is 501 (Not Implemented). <list style="symbols">
                        <t>Requires SETTINGS_ENABLE_CONNECT_PROTOCOL to have been negotiated in HTTP/2 or HTTP/3.</t>
                     </list>
                  </t>
               </list>
            </t>
            <t>If the client infers that classic HTTP CONNECT is not supported, it <bcp14>SHOULD</bcp14> retry the request using the registered default template for "connect-tcp" (<xref target="fig-default"/>). If this request succeeds, the client <bcp14>SHOULD</bcp14> record a preference for CONNECT-TCP to avoid further retry delays.</t>
         </section>
         <section anchor="gateway-compatibility">
            <name>Gateways</name>
            <t>CONNECT-TCP requests can traverse standard HTTP gateways to ease implementation and allow use of shared infrastructure. However, current gateways might need modifications to support TCP proxy services. To be compatible, a gateway <bcp14>MUST</bcp14>:</t>
            <t>
               <list style="symbols">
                  <t>support Extended CONNECT (if acting as an HTTP/2 or HTTP/3 server).</t>
                  <t>support HTTP/1.1 Upgrade to "connect-tcp" (if acting as an HTTP/1.1 server). <list style="symbols">
                        <t>only after forwarding the upgrade request to the origin and observing a success response.</t>
                     </list>
                  </t>
                  <t>forward the "connect-tcp" protocol to the origin.</t>
                  <t>convert CONNECT-TCP requests between all supported HTTP server and client versions.</t>
                  <t>allow any Proxy-Status headers to traverse the gateway.</t>
               </list>
            </t>
            <t>If the proxy relies on TLS Client Certificates for client authentication, the gateway <bcp14>MUST</bcp14> perform this authentication itself or pass the relevant information to the origin (e.g., using a Client-Cert request header field <xref target="RFC9440"/>).</t>
         </section>
      </section>
      <section anchor="security-considerations">
         <name>Security Considerations</name>
         <t>CONNECT-TCP is largely subject to the same security risks as classic HTTP CONNECT. For example, any restrictions on authorized use of the proxy (see <xref section="9.3.6" sectionFormat="comma" target="RFC9110"/>) apply equally to both. The "destination_ip_prohibited" Proxy Error Type from <xref section="2.3.5" sectionFormat="of" target="PROXY-STATUS"/> can be useful when rejecting unauthorized requests.</t>
         <t>A small additional risk is posed by the use of a URI Template parser on the client side. The template input string could be crafted to exploit any vulnerabilities in the parser implementation. Client implementers should apply their usual precautions for code that processes untrusted inputs.</t>
         <t>See <xref section="7" sectionFormat="of" target="CONNECT-UDP"/> for a comparison of the risks of operating a TCP or UDP proxy.</t>
         <section anchor="resource-exhaustion">
            <name>Resource Exhaustion attacks</name>
            <t>A malicious client can cause highly asymmetric resource usage at the proxy by colluding with a destination server and violating the ordinary rules of TCP or HTTP. Some example attacks, and mitigations that proxies can apply:</t>
            <t>
               <list style="symbols">
                  <t>
                     <strong>Connection Pileup</strong>: A malicious client can attempt to open a large number of connections to exhaust the proxy's memory, port, or file descriptor limits. When using HTTP/2 or HTTP/3, each incremental TCP connection imposes a much higher cost on the proxy than on the attacker. <list style="symbols">
                        <t>Mitigation: Limit the number of concurrent connections per client.</t>
                     </list>
                  </t>
                  <t>
                     <strong>Window Bloat</strong>: An attacker can grow the receive window size by simulating a "long, fat network" (<xref section="1.1" sectionFormat="comma" target="RFC7323"/>), then fill the window (from the sender) and stop acknowledging it (at the receiver). This leaves the proxy buffering up to 1 GiB of TCP data until some timeout, while the attacker does not have to retain a large buffer. <list style="symbols">
                        <t>Mitigation: Limit the maximum receive window for TCP and HTTP connections, and the size of userspace buffers used for forwarding data. Alternatively, monitor the connections' send queues and limit the total buffered data per client.</t>
                     </list>
                  </t>
                  <t>
                     <strong>WAIT Abuse</strong>: An attacker can force the proxy into a TIME-WAIT, CLOSE-WAIT, or FIN-WAIT state until the timer expires, tying up a proxy-to-destination 4-tuple for up to four minutes after the client's connection is closed. <list style="symbols">
                        <t>Mitigations: <list style="symbols">
                              <t>Enable the PAWS optimization (<xref section="5" sectionFormat="comma" target="RFC7323"/>) across successive connections (e.g., Linux's <spanx style="verb">tcp_tw_reuse=1</spanx>
                                 <xref target="SYSCTL"/>). This makes TIME-WAIT 4-tuples rapidly reusable if the destination enables TCP Timestamps, which most do.</t>
                              <t>Allocate a large range of IP addresses for TCP connections (especially in IPv6).</t>
                              <t>Limit the number of connections for each client to each destination, even if those connections are in a waiting state and the corresponding CONNECT stream is closed.</t>
                              <t>If necessary, perform an abrupt TCP closure that destroys the Transmission Control Block. Note that reusing a 4-tuple in this way can increase the risk of interference between successive connections.</t>
                           </list>
                        </t>
                     </list>
                  </t>
               </list>
            </t>
         </section>
         <section anchor="client-authentication">
            <name>Client Authentication</name>
            <t>A proxy server operating without access controls on the open internet (an "open proxy") is likely to be discovered and misused quickly by attackers. HTTP client authentication is the most common way to avoid this misuse.</t>
            <t>
               <xref target="authentication-headers"/> describes how to use HTTP client authentication with this specification. Each HTTP client authentication scheme offers distinct security properties, so care should be taken to select an appropriate scheme for each deployment. See <xref section="17.16" sectionFormat="comma" target="RFC9110"/> for additional guidance related to HTTP authentication.</t>
         </section>
         <section anchor="tls-early-data">
            <name>TLS Early Data</name>
            <t>This specification supports sending both proxying requests and optimistic payload data in TLS early data (<xref target="latency-optimizations"/>). TLS 1.3 recommends, but does not require, replay protection for this data (<xref section="8" sectionFormat="comma" target="TLS"/>), so a replay attack could cause the proxy service to establish multiple connections to the target, and to deliver any optimistic payload data on each of these connections. When such a replay attack would cause harm (e.g., when the optimistic data represents a non-idempotent application command), clients <bcp14>MUST NOT</bcp14> use TLS early data.</t>
            <t>See <xref section="6" sectionFormat="of" target="RFC8470"/> for additional relevant security considerations.</t>
         </section>
      </section>
      <section anchor="operational-considerations">
         <name>Operational Considerations</name>
         <section anchor="avoiding-http11">
            <name>Avoiding HTTP/1.1</name>
            <t>While this specification is fully functional under HTTP/1.1, performance-sensitive deployments <bcp14>SHOULD</bcp14> use HTTP/2 or HTTP/3 instead. When using HTTP/1.1:</t>
            <t>
               <list style="symbols">
                  <t>Each CONNECT request requires a new TCP and TLS connection, imposing a higher cost in setup latency, congestion control convergence, CPU time, and data transfer.</t>
                  <t>The graceful and abrupt closure signals (<xref target="closing-connections"/>) are more likely to be missing or corrupted: <list style="symbols">
                        <t>Some implementations may be unable to emit the recommended abrupt closure signals, due to limitations in their TCP and TLS subsystems.</t>
                        <t>Faulty implementations may fail to send a TLS closure alert during graceful shutdown, or fail to report an error when the expected closure alert is not received. These misbehaviors are not compliant with <xref target="TLS"/>, but they are common nonetheless among HTTP/1.1 implementations today.</t>
                     </list>
                  </t>
                  <t>The number of active connections through each client may be limited by the number of available TCP client ports, especially if: <list style="symbols">
                        <t>The client only has one IP address that can be used to reach the proxy.</t>
                        <t>The client is shared between many parties, such as when acting as a gateway or concentrator.</t>
                        <t>The tunneled connections are often closed by the destination. This causes the client to initiate closure of the client-to-proxy connection, leaving the client in a TIME-WAIT state for up to four minutes.</t>
                     </list>
                  </t>
               </list>
            </t>
         </section>
         <section anchor="timeouts">
            <name>Timeouts</name>
            <t>Except when actively sending or receiving data, an endpoint is always waiting for an event from its peer or its TCP connection. HTTP and TCP are designed to ensure that such an event always arrives, so the connection is never permanently stuck in any state until it is fully closed. However, for efficient operation, it may be necessary to adjust the settings for TCP keep-alives (<xref section="3.8.4" sectionFormat="comma" target="TCP"/>), QUIC idle timeouts (<xref section="10.1" sectionFormat="comma" target="QUIC"/>), HTTP/2 PING frames (<xref section="6.7" sectionFormat="comma" target="RFC9113"/>), and other transport options.</t>
            <t>Endpoints <bcp14>MAY</bcp14> impose additional timeouts, especially as a defense against certain resource exhaustion attacks (<xref target="resource-exhaustion"/>). However, operators should apply timeouts cautiously to minimize the impact on connections that are functioning but slow. See <xref target="closing-connections"/> for related requirements.</t>
            <t>For example, enabling PING frames on idle HTTP/2 connections allows the operator to prevent some kinds of failures and detect failed connections faster, but it uses more bandwidth, CPU time, and radio power, and increases the risk of false-positive connection failures. Optimal transport settings will depend on the network environment (e.g., mobile vs. fixed), characteristics of the tunneled application, and many other considerations.</t>
         </section>
         <section anchor="scope-of-packet-level-metadata">
            <name>Scope of Packet-Level Metadata</name>
            <t>This specification does not provide a way to pass packet-level metadata such as IPv6 Extension Headers <xref section="4" sectionFormat="comma" target="RFC2460"/>, DiffServ Codepoints (DSCP) <xref target="RFC2474"/>, or Explicit Congestion Notification (ECN) marks <xref target="RFC3168"/> through the tunnel. TCP options and non-fatal ICMP messages (e.g., Packet Too Big) are similarly not relayed. Instead, these signals are processed by the relevant endpoint of this specification, which is also the TCP endpoint and only relays payload data through the tunnel.</t>
            <t>Consumption and generation of these signals on each connection is controlled by the endpoint, and is independent from any behaviors of the other endpoint and any similar signals on the tunnel's HTTP connection. If the operator has requirements related to these behaviors, it must configure the relevant endpoint (typically the proxy) accordingly.</t>
         </section>
         <section anchor="ip-address-sharing">
            <name>IP address sharing</name>
            <t>A TCP proxy typically uses the same IP address to establish connections on behalf of multiple clients, especially in IPv4. <xref target="RFC6269"/> provides guidance regarding difficulties that can arise from IP address sharing, including in this arrangement.</t>
         </section>
         <section anchor="diagnostics-and-monitoring">
            <name>Diagnostics and Monitoring</name>
            <t>A proxy in this protocol reports success or failure in each response via the HTTP status code and the Proxy-Status response header field. Monitoring those error codes is a sensible way to assess the functioning of a proxy server. Other relevant performance indicators may include:</t>
            <t>
               <list style="symbols">
                  <t>Abrupt closure rates</t>
                  <t>Number of active tunnels per user</t>
                  <t>Total throughput in each direction</t>
                  <t>Number of bytes buffered</t>
                  <t>Connection duration</t>
                  <t>Time spent establishing or closing connections</t>
                  <t>Number of half-closed or WAIT-state connections</t>
                  <t>DNS resolution delay</t>
               </list>
            </t>
            <t>An increase in any of these measures could indicate an operational problem or a resource exhaustion attack (<xref target="resource-exhaustion"/>). See <xref target="resource-exhaustion"/> for guidance on relevant defenses and limits.</t>
         </section>
      </section>
      <section anchor="iana-considerations">
         <name>IANA Considerations</name>
         <section anchor="new-upgrade-token">
            <name>New Upgrade Token</name>
            <t>IANA is requested to add the following entry to the "HTTP Upgrade Tokens" registry under "Hypertext Transfer Protocol (HTTP) Upgrade Token Registry" registry group:</t>
            <texttable>
               <ttcol align="left">Value</ttcol>
               <ttcol align="left">Description</ttcol>
               <ttcol align="left">Expected Version Tokens</ttcol>
               <ttcol align="left">Reference</ttcol>
               <c>"connect-tcp"</c>
               <c>Proxying of TCP payloads</c>
               <c>(None)</c>
               <c>(This document)</c>
            </texttable>
            <section anchor="interop-testing" removeInRFC="true">
               <name>Interop testing</name>
               <t>For interoperability testing of this draft version, implementations <bcp14>SHALL</bcp14> use the value "connect-tcp-12".</t>
            </section>
         </section>
         <section anchor="iana-template">
            <name>New MASQUE Default Template</name>
            <t>IANA is requested to add the following entry to the "MASQUE URI Suffixes" registry under "Multiplexed Application Substrate over QUIC Encryption (MASQUE)" registry group:</t>
            <texttable>
               <ttcol align="left">Path Segment</ttcol>
               <ttcol align="left">Description</ttcol>
               <ttcol align="left">Reference</ttcol>
               <c>tcp</c>
               <c>TCP Proxying</c>
               <c>(This document)</c>
            </texttable>
         </section>
         <section anchor="data-capsule">
            <name>New Capsule Type</name>
            <t>IANA is requested to add the following entry to the "HTTP Capsule Types" registry under "Multiplexed Application Substrate over QUIC Encryption (MASQUE)" registry group:</t>
            <texttable>
               <ttcol align="left">Value</ttcol>
               <ttcol align="left">Capsule Type</ttcol>
               <ttcol align="left">Status</ttcol>
               <ttcol align="left">Reference</ttcol>
               <ttcol align="left">Change Controller</ttcol>
               <ttcol align="left">Contact</ttcol>
               <c>0x08</c>
               <c>DATA</c>
               <c>permanent</c>
               <c>(This document), <xref target="specification"/>
               </c>
               <c>IETF</c>
               <c>HTTPBIS</c>
               <c>0x09</c>
               <c>FINAL_DATA</c>
               <c>permanent</c>
               <c>(This document), <xref target="specification"/>
               </c>
               <c>IETF</c>
               <c>HTTPBIS</c>
            </texttable>
         </section>
      </section>
   </middle>
   <back>
      <displayreference target="RFC9110" to="HTTP"/>
      <displayreference target="RFC9112" to="HTTP/1.1"/>
      <displayreference target="RFC9113" to="HTTP/2"/>
      <displayreference target="RFC9114" to="HTTP/3"/>
      <references anchor="sec-combined-references" title="References">
         <references anchor="sec-normative-references" title="Normative References">
            <reference anchor="RFC9110">
               <front>
                  <title>HTTP Semantics</title>
                  <author fullname="R. Fielding"
                          initials="R."
                          role="editor"
                          surname="Fielding"/>
                  <author fullname="M. Nottingham"
                          initials="M."
                          role="editor"
                          surname="Nottingham"/>
                  <author fullname="J. Reschke"
                          initials="J."
                          role="editor"
                          surname="Reschke"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="STD" value="97"/>
               <seriesInfo name="RFC" value="9110"/>
               <seriesInfo name="DOI" value="10.17487/RFC9110"/>
            </reference>
            <reference anchor="RFC9112">
               <front>
                  <title>HTTP/1.1</title>
                  <author fullname="R. Fielding"
                          initials="R."
                          role="editor"
                          surname="Fielding"/>
                  <author fullname="M. Nottingham"
                          initials="M."
                          role="editor"
                          surname="Nottingham"/>
                  <author fullname="J. Reschke"
                          initials="J."
                          role="editor"
                          surname="Reschke"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="STD" value="99"/>
               <seriesInfo name="RFC" value="9112"/>
               <seriesInfo name="DOI" value="10.17487/RFC9112"/>
            </reference>
            <reference anchor="RFC9113">
               <front>
                  <title>HTTP/2</title>
                  <author fullname="M. Thomson"
                          initials="M."
                          role="editor"
                          surname="Thomson"/>
                  <author fullname="C. Benfield"
                          initials="C."
                          role="editor"
                          surname="Benfield"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9113"/>
               <seriesInfo name="DOI" value="10.17487/RFC9113"/>
            </reference>
            <reference anchor="RFC9114">
               <front>
                  <title>HTTP/3</title>
                  <author fullname="M. Bishop"
                          initials="M."
                          role="editor"
                          surname="Bishop"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9114"/>
               <seriesInfo name="DOI" value="10.17487/RFC9114"/>
            </reference>
            <reference anchor="CONNECT-UDP">
               <front>
                  <title>Proxying UDP in HTTP</title>
                  <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
                  <date month="August" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9298"/>
               <seriesInfo name="DOI" value="10.17487/RFC9298"/>
            </reference>
            <reference anchor="RFC2119">
               <front>
                  <title>Key words for use in RFCs to Indicate Requirement Levels</title>
                  <author fullname="S. Bradner" initials="S." surname="Bradner"/>
                  <date month="March" year="1997"/>
               </front>
               <seriesInfo name="BCP" value="14"/>
               <seriesInfo name="RFC" value="2119"/>
               <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            </reference>
            <reference anchor="RFC8174">
               <front>
                  <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
                  <author fullname="B. Leiba" initials="B." surname="Leiba"/>
                  <date month="May" year="2017"/>
               </front>
               <seriesInfo name="BCP" value="14"/>
               <seriesInfo name="RFC" value="8174"/>
               <seriesInfo name="DOI" value="10.17487/RFC8174"/>
            </reference>
            <reference anchor="RFC6570">
               <front>
                  <title>URI Template</title>
                  <author fullname="J. Gregorio" initials="J." surname="Gregorio"/>
                  <author fullname="R. Fielding" initials="R." surname="Fielding"/>
                  <author fullname="M. Hadley" initials="M." surname="Hadley"/>
                  <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
                  <author fullname="D. Orchard" initials="D." surname="Orchard"/>
                  <date month="March" year="2012"/>
               </front>
               <seriesInfo name="RFC" value="6570"/>
               <seriesInfo name="DOI" value="10.17487/RFC6570"/>
            </reference>
            <reference anchor="CAPSULE">
               <front>
                  <title>HTTP Datagrams and the Capsule Protocol</title>
                  <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
                  <author fullname="L. Pardue" initials="L." surname="Pardue"/>
                  <date month="August" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9297"/>
               <seriesInfo name="DOI" value="10.17487/RFC9297"/>
            </reference>
            <reference anchor="RFC8441">
               <front>
                  <title>Bootstrapping WebSockets with HTTP/2</title>
                  <author fullname="P. McManus" initials="P." surname="McManus"/>
                  <date month="September" year="2018"/>
               </front>
               <seriesInfo name="RFC" value="8441"/>
               <seriesInfo name="DOI" value="10.17487/RFC8441"/>
            </reference>
            <reference anchor="RFC9220">
               <front>
                  <title>Bootstrapping WebSockets with HTTP/3</title>
                  <author fullname="R. Hamilton" initials="R." surname="Hamilton"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9220"/>
               <seriesInfo name="DOI" value="10.17487/RFC9220"/>
            </reference>
            <reference anchor="QUIC">
               <front>
                  <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
                  <author fullname="J. Iyengar"
                          initials="J."
                          role="editor"
                          surname="Iyengar"/>
                  <author fullname="M. Thomson"
                          initials="M."
                          role="editor"
                          surname="Thomson"/>
                  <date month="May" year="2021"/>
               </front>
               <seriesInfo name="RFC" value="9000"/>
               <seriesInfo name="DOI" value="10.17487/RFC9000"/>
            </reference>
            <reference anchor="TLS">
               <front>
                  <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
                  <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
                  <date month="July" year="2026"/>
               </front>
               <seriesInfo name="RFC" value="9846"/>
               <seriesInfo name="DOI" value="10.17487/RFC9846"/>
            </reference>
            <reference anchor="RFC8470">
               <front>
                  <title>Using Early Data in HTTP</title>
                  <author fullname="M. Thomson" initials="M." surname="Thomson"/>
                  <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
                  <author fullname="W. Tarreau" initials="W." surname="Tarreau"/>
                  <date month="September" year="2018"/>
               </front>
               <seriesInfo name="RFC" value="8470"/>
               <seriesInfo name="DOI" value="10.17487/RFC8470"/>
            </reference>
            <reference anchor="PROXY-STATUS">
               <front>
                  <title>The Proxy-Status HTTP Response Header Field</title>
                  <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
                  <author fullname="P. Sikora" initials="P." surname="Sikora"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="RFC" value="9209"/>
               <seriesInfo name="DOI" value="10.17487/RFC9209"/>
            </reference>
            <reference anchor="TCP">
               <front>
                  <title>Transmission Control Protocol (TCP)</title>
                  <author fullname="W. Eddy" initials="W." role="editor" surname="Eddy"/>
                  <date month="August" year="2022"/>
               </front>
               <seriesInfo name="STD" value="7"/>
               <seriesInfo name="RFC" value="9293"/>
               <seriesInfo name="DOI" value="10.17487/RFC9293"/>
            </reference>
         </references>
         <references anchor="sec-informative-references" title="Informative References">
            <reference anchor="CAPABILITY" target="https://www.w3.org/TR/capability-urls/">
               <front>
                  <title>Good Practices for Capability URLs</title>
                  <author/>
                  <date month="February" year="2014"/>
               </front>
            </reference>
            <reference anchor="CLEAR-SITE-DATA"
                       target="https://www.w3.org/TR/clear-site-data/">
               <front>
                  <title>Clear Site Data</title>
                  <author/>
                  <date month="November" year="2017"/>
               </front>
            </reference>
            <reference anchor="SYSCTL"
                       target="https://www.kernel.org/doc/html/v7.1/networking/ip-sysctl.html">
               <front>
                  <title>IP Sysctl -- The Linux Kernel documentation</title>
                  <author/>
                  <date month="June" year="2026"/>
               </front>
            </reference>
            <reference anchor="CONNECT-IP">
               <front>
                  <title>Proxying IP in HTTP</title>
                  <author fullname="T. Pauly" initials="T." role="editor" surname="Pauly"/>
                  <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
                  <author fullname="A. Chernyakhovsky" initials="A." surname="Chernyakhovsky"/>
                  <author fullname="M. Kühlewind" initials="M." surname="Kühlewind"/>
                  <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
                  <date month="October" year="2023"/>
               </front>
               <seriesInfo name="RFC" value="9484"/>
               <seriesInfo name="DOI" value="10.17487/RFC9484"/>
            </reference>
            <reference anchor="ALT-SVC">
               <front>
                  <title>HTTP Alternative Services</title>
                  <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
                  <author fullname="P. McManus" initials="P." surname="McManus"/>
                  <author fullname="J. Reschke" initials="J." surname="Reschke"/>
                  <date month="April" year="2016"/>
               </front>
               <seriesInfo name="RFC" value="7838"/>
               <seriesInfo name="DOI" value="10.17487/RFC7838"/>
            </reference>
            <reference anchor="HSTS">
               <front>
                  <title>HTTP Strict Transport Security (HSTS)</title>
                  <author fullname="J. Hodges" initials="J." surname="Hodges"/>
                  <author fullname="C. Jackson" initials="C." surname="Jackson"/>
                  <author fullname="A. Barth" initials="A." surname="Barth"/>
                  <date month="November" year="2012"/>
               </front>
               <seriesInfo name="RFC" value="6797"/>
               <seriesInfo name="DOI" value="10.17487/RFC6797"/>
            </reference>
            <reference anchor="I-D.ietf-httpbis-wrap-up">
               <front>
                  <title>The HTTP Wrap Up Capsule</title>
                  <author fullname="David Schinazi" initials="D." surname="Schinazi">
                     <organization>Google LLC</organization>
                  </author>
                  <author fullname="Lucas Pardue" initials="L." surname="Pardue">
                     <organization>Cloudflare</organization>
                  </author>
                  <date day="7" month="July" year="2025"/>
               </front>
               <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-wrap-up-01"/>
            </reference>
            <reference anchor="RFC8942">
               <front>
                  <title>HTTP Client Hints</title>
                  <author fullname="I. Grigorik" initials="I." surname="Grigorik"/>
                  <author fullname="Y. Weiss" initials="Y." surname="Weiss"/>
                  <date month="February" year="2021"/>
               </front>
               <seriesInfo name="RFC" value="8942"/>
               <seriesInfo name="DOI" value="10.17487/RFC8942"/>
            </reference>
            <reference anchor="RFC6265">
               <front>
                  <title>HTTP State Management Mechanism</title>
                  <author fullname="A. Barth" initials="A." surname="Barth"/>
                  <date month="April" year="2011"/>
               </front>
               <seriesInfo name="RFC" value="6265"/>
               <seriesInfo name="DOI" value="10.17487/RFC6265"/>
            </reference>
            <reference anchor="HTTP-CACHING">
               <front>
                  <title>HTTP Caching</title>
                  <author fullname="R. Fielding"
                          initials="R."
                          role="editor"
                          surname="Fielding"/>
                  <author fullname="M. Nottingham"
                          initials="M."
                          role="editor"
                          surname="Nottingham"/>
                  <author fullname="J. Reschke"
                          initials="J."
                          role="editor"
                          surname="Reschke"/>
                  <date month="June" year="2022"/>
               </front>
               <seriesInfo name="STD" value="98"/>
               <seriesInfo name="RFC" value="9111"/>
               <seriesInfo name="DOI" value="10.17487/RFC9111"/>
            </reference>
            <reference anchor="I-D.ietf-quic-reliable-stream-reset">
               <front>
                  <title>QUIC Stream Resets with Partial Delivery</title>
                  <author fullname="Marten Seemann" initials="M." surname="Seemann"/>
                  <author fullname="Kazuho Oku" initials="K." surname="Oku">
                     <organization>Fastly</organization>
                  </author>
                  <date day="6" month="September" year="2026"/>
               </front>
               <seriesInfo name="Internet-Draft" value="draft-ietf-quic-reliable-stream-reset-11"/>
            </reference>
            <reference anchor="HEv2">
               <front>
                  <title>Happy Eyeballs Version 2: Better Connectivity Using Concurrency</title>
                  <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
                  <author fullname="T. Pauly" initials="T." surname="Pauly"/>
                  <date month="December" year="2017"/>
               </front>
               <seriesInfo name="RFC" value="8305"/>
               <seriesInfo name="DOI" value="10.17487/RFC8305"/>
            </reference>
            <reference anchor="CONCEALED">
               <front>
                  <title>The Concealed HTTP Authentication Scheme</title>
                  <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
                  <author fullname="D. Oliver" initials="D." surname="Oliver"/>
                  <author fullname="J. Hoyland" initials="J." surname="Hoyland"/>
                  <date month="February" year="2025"/>
               </front>
               <seriesInfo name="RFC" value="9729"/>
               <seriesInfo name="DOI" value="10.17487/RFC9729"/>
            </reference>
            <reference anchor="I-D.ietf-intarea-proxy-config">
               <front>
                  <title>Communicating Proxy Configurations in Provisioning Domains</title>
                  <author fullname="Tommy Pauly" initials="T." surname="Pauly">
                     <organization>Apple, Inc.</organization>
                  </author>
                  <author fullname="Dragana Damjanovic" initials="D." surname="Damjanovic">
                     <organization>Microsoft</organization>
                  </author>
                  <author fullname="Yaroslav Rosomakho" initials="Y." surname="Rosomakho">
                     <organization>Zscaler</organization>
                  </author>
                  <date day="19" month="May" year="2026"/>
               </front>
               <seriesInfo name="Internet-Draft" value="draft-ietf-intarea-proxy-config-14"/>
            </reference>
            <reference anchor="RFC9440">
               <front>
                  <title>Client-Cert HTTP Header Field</title>
                  <author fullname="B. Campbell" initials="B." surname="Campbell"/>
                  <author fullname="M. Bishop" initials="M." surname="Bishop"/>
                  <date month="July" year="2023"/>
               </front>
               <seriesInfo name="RFC" value="9440"/>
               <seriesInfo name="DOI" value="10.17487/RFC9440"/>
            </reference>
            <reference anchor="RFC7323">
               <front>
                  <title>TCP Extensions for High Performance</title>
                  <author fullname="D. Borman" initials="D." surname="Borman"/>
                  <author fullname="B. Braden" initials="B." surname="Braden"/>
                  <author fullname="V. Jacobson" initials="V." surname="Jacobson"/>
                  <author fullname="R. Scheffenegger"
                          initials="R."
                          role="editor"
                          surname="Scheffenegger"/>
                  <date month="September" year="2014"/>
               </front>
               <seriesInfo name="RFC" value="7323"/>
               <seriesInfo name="DOI" value="10.17487/RFC7323"/>
            </reference>
            <reference anchor="RFC2460">
               <front>
                  <title>Internet Protocol, Version 6 (IPv6) Specification</title>
                  <author fullname="S. Deering" initials="S." surname="Deering"/>
                  <author fullname="R. Hinden" initials="R." surname="Hinden"/>
                  <date month="December" year="1998"/>
               </front>
               <seriesInfo name="RFC" value="2460"/>
               <seriesInfo name="DOI" value="10.17487/RFC2460"/>
            </reference>
            <reference anchor="RFC2474">
               <front>
                  <title>Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers</title>
                  <author fullname="K. Nichols" initials="K." surname="Nichols"/>
                  <author fullname="S. Blake" initials="S." surname="Blake"/>
                  <author fullname="F. Baker" initials="F." surname="Baker"/>
                  <author fullname="D. Black" initials="D." surname="Black"/>
                  <date month="December" year="1998"/>
               </front>
               <seriesInfo name="RFC" value="2474"/>
               <seriesInfo name="DOI" value="10.17487/RFC2474"/>
            </reference>
            <reference anchor="RFC3168">
               <front>
                  <title>The Addition of Explicit Congestion Notification (ECN) to IP</title>
                  <author fullname="K. Ramakrishnan" initials="K." surname="Ramakrishnan"/>
                  <author fullname="S. Floyd" initials="S." surname="Floyd"/>
                  <author fullname="D. Black" initials="D." surname="Black"/>
                  <date month="September" year="2001"/>
               </front>
               <seriesInfo name="RFC" value="3168"/>
               <seriesInfo name="DOI" value="10.17487/RFC3168"/>
            </reference>
            <reference anchor="RFC6269">
               <front>
                  <title>Issues with IP Address Sharing</title>
                  <author fullname="M. Ford" initials="M." role="editor" surname="Ford"/>
                  <author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
                  <author fullname="A. Durand" initials="A." surname="Durand"/>
                  <author fullname="P. Levis" initials="P." surname="Levis"/>
                  <author fullname="P. Roberts" initials="P." surname="Roberts"/>
                  <date month="June" year="2011"/>
               </front>
               <seriesInfo name="RFC" value="6269"/>
               <seriesInfo name="DOI" value="10.17487/RFC6269"/>
            </reference>
         </references>
      </references>
      <?line 519?>
      <section anchor="acknowledgments" numbered="false">
         <name>Acknowledgments</name>
         <t>This document benefited from close review and suggested changes by:</t>
         <t>
            <list style="symbols">
               <t>Mohamed Boucadair</t>
               <t>Deb Cooley</t>
               <t>Gorry Fairhurst</t>
               <t>Thomas Fossati</t>
               <t>Amos Jeffries</t>
               <t>Mahesh Jethanandani</t>
               <t>Antun Jurkovic</t>
               <t>Eric Kinnear</t>
               <t>Kyle Nekritz</t>
               <t>Kazuho Oku</t>
               <t>Tommy Pauly</t>
               <t>Yaroslav Romakho</t>
               <t>David Schinazi</t>
               <t>Ketan Talaulikar</t>
               <t>Willy Tarreau</t>
            </list>
         </t>
      </section>
   </back>
</rfc>
