| draft-ietf-httpbis-connect-tcp-06.txt | draft-ietf-httpbis-connect-tcp-latest.txt | |||
|---|---|---|---|---|
| httpbis Working Group B. Schwartz | httpbis Working Group B. Schwartz | |||
| Internet-Draft Meta Platforms, Inc. | Internet-Draft Meta Platforms, Inc. | |||
| Intended status: Standards Track October 21, 2024 | Intended status: Standards Track October 27, 2024 | |||
| Expires: April 24, 2025 | Expires: April 30, 2025 | |||
| Template-Driven HTTP CONNECT Proxying for TCP | Template-Driven HTTP CONNECT Proxying for TCP | |||
| draft-ietf-httpbis-connect-tcp-06 | draft-ietf-httpbis-connect-tcp-latest | |||
| Abstract | Abstract | |||
| TCP proxying using HTTP CONNECT has long been part of the core HTTP | TCP proxying using HTTP CONNECT has long been part of the core HTTP | |||
| specification. However, this proxying functionality has several | specification. However, this proxying functionality has several | |||
| important deficiencies in modern HTTP environments. This | important deficiencies in modern HTTP environments. This | |||
| specification defines an alternative HTTP proxy service configuration | specification defines an alternative HTTP proxy service configuration | |||
| for TCP connections. This configuration is described by a URI | for TCP connections. This configuration is described by a URI | |||
| Template, similar to the CONNECT-UDP and CONNECT-IP protocols. | Template, similar to the CONNECT-UDP and CONNECT-IP protocols. | |||
| skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on April 24, 2025. | This Internet-Draft will expire on April 30, 2025. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2024 IETF Trust and the persons identified as the | Copyright (c) 2024 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 7, line 17 ¶ | skipping to change at page 7, line 17 ¶ | |||
| Section 11.5). For many authentication schemes, this will allow the | Section 11.5). For many authentication schemes, this will allow the | |||
| client to avoid waiting for a "401 (Unauthorized)" response before | client to avoid waiting for a "401 (Unauthorized)" response before | |||
| each new connection through the proxy. | each new connection through the proxy. | |||
| 3.4. Use of the Capsule Protocol | 3.4. Use of the Capsule Protocol | |||
| When using the "connect-tcp" Upgrade Token, templated TCP proxies do | When using the "connect-tcp" Upgrade Token, templated TCP proxies do | |||
| not use the Capsule Protocol [RFC9297]. Clients MAY request use of | not use the Capsule Protocol [RFC9297]. Clients MAY request use of | |||
| the Capsule Protocol by offering the Upgrade Token "connect-tcp- | the Capsule Protocol by offering the Upgrade Token "connect-tcp- | |||
| capsule" instead. When offering or accepting the "connect-tcp- | capsule" instead. When offering or accepting the "connect-tcp- | |||
| capsule" Upgrade Token, clients and servers SHOULD including a | capsule" Upgrade Token, clients and servers SHOULD include a | |||
| "Capsule-Protocol: ?1" header to facilitate processing by | "Capsule-Protocol: ?1" header to facilitate processing by | |||
| intermediaries. | intermediaries. | |||
| Clients of this specification MAY implement "connect-tcp", "connect- | Clients of this specification MAY implement "connect-tcp", "connect- | |||
| tcp-capsule", or both. Accordingly, a templated TCP proxy server | tcp-capsule", or both. Accordingly, a templated TCP proxy server | |||
| MUST implement both Upgrade Tokens unless its use is restricted to a | MUST implement both Upgrade Tokens unless its use is restricted to a | |||
| subset of compatible clients. | subset of compatible clients. | |||
| When using "connect-tcp-capsule", TCP payload data is sent in the | When using "connect-tcp-capsule", TCP payload data is sent in the | |||
| payload of a new Capsule Type named DATA (Section 8.3). The ordered | payload of a new Capsule Type named DATA (Section 8.3). The ordered | |||
| End of changes. 4 change blocks. | ||||
| 5 lines changed or deleted | 5 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||