Use Cases and Requirements for QUIC as a Substrate
draft-kuehlewind-masque-quic-substrate-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Replaces draft-kuehlewind-quic-substrate
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf 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)
Network Working Group                                      M. Kuehlewind
Internet-Draft                                                 Z. Sarker
Intended status: Informational                                  Ericsson
Expires: 10 September 2020                                    T. Fossati
                                                                     Arm
                                                               L. Pardue
                                                              Cloudflare
                                                            9 March 2020

           Use Cases and Requirements for QUIC as a Substrate
               draft-kuehlewind-masque-quic-substrate-00

Abstract

   In situations where direct connectivity is not available or desired,
   proxies in the network are used to forward and potentially translate
   traffic.  TCP is often used as a proxying or tunneling protocol.
   QUIC is a new, emerging transport protocol and there is a similar
   expectation that it too will be used as a substrate once it is widely
   deployed.  Using QUIC instead of TCP in existing scenarios will allow
   proxying and tunneling services to maintain the benefits of QUIC
   natively, without degrading the performance and security
   characteristics.  QUIC also opens up new opportunities for these
   services to have lower latency and better multistreaming support.
   This document summarizes current and future usage scenarios to derive
   requirements for QUIC as a substrate and to provide additional
   considerations for proxy signaling and control protocol as proposed
   by MASQUE.

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 10 September 2020.

Kuehlewind, et al.      Expires 10 September 2020               [Page 1]
Internet-Draft               QUIC Substrate                   March 2020

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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Obfuscation via Tunneling . . . . . . . . . . . . . . . .   3
     2.2.  Advanced Support of User Agents . . . . . . . . . . . . .   5
       2.2.1.  Security and Access Policy Enforcement  . . . . . . .   6
     2.3.  Frontend Support for Load Balancing and Migration/
           Mobility  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  IoT Gateways  . . . . . . . . . . . . . . . . . . . . . .   7
     2.5.  Multi-hop Chaining Usage  . . . . . . . . . . . . . . . .   8
       2.5.1.  Considerations for Multiple Encryption  . . . . . . .   9
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Review of Existing Approaches . . . . . . . . . . . . . . . .  10
   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  11
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   QUIC is a new transport protocol that was developed with a focus on
   optimizing HTTP traffic by supporting multiplexing without head-of-
   line-blocking and integrating security directly into the transport.
   This tight integration of security allows the transport and security
   handshakes to be combined into a single round-trip exchange, after
   which both the transport connection and authenticated encryption keys
   are ready.

   Based on the expectation that QUIC will be widely used for HTTP, it
   follows that there will also be a need to enable the use of QUIC for
Show full document text