The CONNECT-IP method for proxying IP traffic
draft-kuehlewind-masque-connect-ip-00

Document Type Active Internet-Draft (individual)
Authors Mirja K├╝hlewind  , Magnus Westerlund  , Marcus Ihlar  , Zaheduzzaman Sarker 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
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)
MASQUE                                                     M. Kuehlewind
Internet-Draft                                             M. Westerlund
Intended status: Standards Track                                M. Ihlar
Expires: 6 May 2021                                            Z. Sarker
                                                                Ericsson
                                                         2 November 2020

             The CONNECT-IP method for proxying IP traffic
                 draft-kuehlewind-masque-connect-ip-00

Abstract

   This draft specifies a new HTTP/3 method CONNECT-IP to proxy IP
   traffic.  CONNECT-IP can be used to convert a QUIC stream into a
   tunnel or initialise an HTTP datagram flow to a forwarding proxy.
   Each stream or HTTP datagram flow can be used separately to establish
   forwarding of an IP flow to potentially different remote hosts.  To
   request forwarding, a client connects to a proxy server by initiating
   a HTTP/3 connection and sends a CONNECT-IP indicating the address of
   the target server.  The proxy server then forwards payload received
   on that stream or in an HTTP datagram with a certain flow ID to the
   target server after adding an IP header to each of the frames
   received.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the MASQUE Working Group
   mailing list (masque@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/masque/.

   Source for this draft and an issue tracker can be found at
   https://github.com/mirjak/draft-kuehlewind-masque-connect-ip.

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/.

Kuehlewind, et al.         Expires 6 May 2021                   [Page 1]
Internet-Draft              CONNECT-IP method              November 2020

   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 6 May 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Motivation of IP flow model . . . . . . . . . . . . . . .   5
   2.  The CONNECT-IP method . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Stream-based mode . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Datagram-based mode . . . . . . . . . . . . . . . . . . .   7
     2.3.  IP-Protocol Header for CONNECT-IP . . . . . . . . . . . .   8
     2.4.  Conn-ID Header for CONNECT-IP . . . . . . . . . . . . . .   8
   3.  Client behavior . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  MASQUE server behavior  . . . . . . . . . . . . . . . . . . .   9
     4.1.  Error handling  . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  IP address selection and NAT  . . . . . . . . . . . . . .  10
     4.3.  Constructing the IP header  . . . . . . . . . . . . . . .  10
     4.4.  Receiving an IP packet  . . . . . . . . . . . . . . . . .  11
   5.  MASQUE signalling . . . . . . . . . . . . . . . . . . . . . .  11
     5.1.  Config file . . . . . . . . . . . . . . . . . . . . . . .  11
     5.2.  ECN . . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.3.  ICMP handling . . . . . . . . . . . . . . . . . . . . . .  12
     5.4.  MTU considerations  . . . . . . . . . . . . . . . . . . .  12
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  Security considerations . . . . . . . . . . . . . . . . . . .  12
   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  HTTP Method . . . . . . . . . . . . . . . . . . . . . . .  13
     8.2.  HTTP Header . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text