QUIC-Aware Proxying Using CONNECT-UDP
draft-pauly-masque-quic-proxy-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Tommy Pauly
,
David Schinazi
|
|
Last updated |
|
2020-11-13
(latest revision 2020-10-18)
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
html
xml
pdf
htmlized (tools)
htmlized
bibtex
|
|
Additional Resources |
|
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group T. Pauly
Internet-Draft Apple Inc.
Intended status: Experimental D. Schinazi
Expires: 21 April 2021 Google LLC
18 October 2020
QUIC-Aware Proxying Using CONNECT-UDP
draft-pauly-masque-quic-proxy-00
Abstract
This document defines an extension to the CONNECT-UDP HTTP method
that adds specific optimizations for QUIC connections that are
proxied. This extension allows a proxy to reuse UDP 4-tuples for
multiple connections. It also defines a mode of proxying in which
QUIC short header packets can be forwarded through the proxy rather
than being re-encapsulated and re-encrypted.
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/tfpauly/quic-proxy (https://github.com/tfpauly/
quic-proxy).
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 21 April 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Pauly & Schinazi Expires 21 April 2021 [Page 1]
Internet-Draft QUIC Proxy October 2020
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 . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Required Proxy State . . . . . . . . . . . . . . . . . . . . 5
2.1. Datagram Flow ID Mapping . . . . . . . . . . . . . . . . 5
2.2. Server Connection ID Mapping . . . . . . . . . . . . . . 6
2.3. Client Connection ID Mappings . . . . . . . . . . . . . . 6
2.4. Detecting Connection ID Conflicts . . . . . . . . . . . . 6
3. Connection ID Headers for CONNECT-UDP . . . . . . . . . . . . 7
4. Client Request Behavior . . . . . . . . . . . . . . . . . . . 8
4.1. New Proxied Connection Setup . . . . . . . . . . . . . . 8
4.2. Adding New Client Connection IDs . . . . . . . . . . . . 9
4.3. Sending With Forwarded Mode . . . . . . . . . . . . . . . 9
4.4. Receiving With Forwarded Mode . . . . . . . . . . . . . . 10
4.5. Opting Out of Forwarded Mode . . . . . . . . . . . . . . 10
5. Proxy Response Behavior . . . . . . . . . . . . . . . . . . . 10
5.1. Removing Mapping State . . . . . . . . . . . . . . . . . 12
6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Interactions with Load Balancers . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9.1. HTTP Headers . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
The CONNECT-UDP HTTP method [CONNECT-UDP] defines a way to send
datagrams through an HTTP proxy, where UDP is used to communicate
between the proxy and a target server. This can be used to proxy
QUIC connections [QUIC], since QUIC runs over UDP datagrams.
Pauly & Schinazi Expires 21 April 2021 [Page 2]
Show full document text