The CONNECT-UDP HTTP Method
draft-ietf-masque-connect-udp-03
Network Working Group D. Schinazi
Internet-Draft Google LLC
Intended status: Standards Track 5 January 2021
Expires: 9 July 2021
The CONNECT-UDP HTTP Method
draft-ietf-masque-connect-udp-03
Abstract
This document describes the CONNECT-UDP HTTP method. CONNECT-UDP is
similar to the HTTP CONNECT method, but it uses UDP instead of TCP.
Discussion of this work is encouraged to happen on the MASQUE IETF
mailing list masque@ietf.org or on the GitHub repository which
contains the draft: https://github.com/ietf-wg-masque/draft-ietf-
masque-connect-udp.
Discussion Venues
This note is to be removed before publishing as an RFC.
Source for this draft and an issue tracker can be found at
https://github.com/ietf-wg-masque/draft-ietf-masque-connect-udp.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 9 July 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
Schinazi Expires 9 July 2021 [Page 1]
Internet-Draft CONNECT-UDP January 2021
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions and Definitions . . . . . . . . . . . . . . . 2
2. Supported HTTP Versions . . . . . . . . . . . . . . . . . . . 3
3. The CONNECT-UDP Method . . . . . . . . . . . . . . . . . . . 3
4. Datagram Encoding of Proxied UDP Packets . . . . . . . . . . 4
5. Stream Chunks . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Stream Encoding of Proxied UDP Packets . . . . . . . . . . . 6
7. Proxy Handling . . . . . . . . . . . . . . . . . . . . . . . 7
8. HTTP Intermediaries . . . . . . . . . . . . . . . . . . . . . 7
9. Performance Considerations . . . . . . . . . . . . . . . . . 8
10. Security Considerations . . . . . . . . . . . . . . . . . . . 8
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11.1. HTTP Method . . . . . . . . . . . . . . . . . . . . . . 9
11.2. URI Scheme Registration . . . . . . . . . . . . . . . . 9
11.3. Stream Chunk Type Registration . . . . . . . . . . . . . 9
12. Normative References . . . . . . . . . . . . . . . . . . . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
This document describes the CONNECT-UDP HTTP method. CONNECT-UDP is
similar to the HTTP CONNECT method (see section 4.3.6 of [RFC7231]),
but it uses UDP [UDP] instead of TCP [TCP].
Discussion of this work is encouraged to happen on the MASQUE IETF
mailing list masque@ietf.org or on the GitHub repository which
contains the draft: https://github.com/ietf-wg-masque/draft-ietf-
masque-connect-udp.
1.1. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Schinazi Expires 9 July 2021 [Page 2]
Internet-Draft CONNECT-UDP January 2021
In this document, we use the term "proxy" to refer to the HTTP server
that opens the UDP socket and responds to the CONNECT-UDP request.
If there are HTTP intermediaries (as defined in Section 2.3 of
[RFC7230]) between the client and the proxy, those are referred to as
Show full document text