Session mode for multiple QUIC Tunnels
draft-piraux-intarea-quic-tunnel-session-00

Document Type Active Internet-Draft (individual)
Authors Maxime Piraux  , Olivier Bonaventure  , Adi Masputra 
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)
Internet Area Working Group                                    M. Piraux
Internet-Draft                                            O. Bonaventure
Intended status: Experimental                                  UCLouvain
Expires: 6 May 2021                                          A. Masputra
                                                              Apple Inc.
                                                         2 November 2020

                 Session mode for multiple QUIC Tunnels
              draft-piraux-intarea-quic-tunnel-session-00

Abstract

   This document specifies methods for grouping QUIC tunnel connections
   in a single session enabling the exchange of packets of Internet
   protocols over several QUIC connections.

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

Piraux, et al.             Expires 6 May 2021                   [Page 1]
Internet-Draft             QUIC Tunnel Session             November 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Reference environment . . . . . . . . . . . . . . . . . . . .   3
   4.  The tunnel session mode . . . . . . . . . . . . . . . . . . .   4
     4.1.  Joining a tunneling session . . . . . . . . . . . . . . .   6
       4.1.1.  Coordinate use of the Packet Tag  . . . . . . . . . .   7
   5.  Connection establishment  . . . . . . . . . . . . . . . . . .   7
   6.  Messages format . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  QUIC tunnel control TLVs  . . . . . . . . . . . . . . . .   8
       6.1.1.  New Session TLV . . . . . . . . . . . . . . . . . . .   8
       6.1.2.  Session ID TLV  . . . . . . . . . . . . . . . . . . .   9
       6.1.3.  Join Session TLV  . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Registration of QUIC tunnel Identification String . . . .  10
     8.2.  QUIC tunnel control TLVs  . . . . . . . . . . . . . . . .  10
       8.2.1.  QUIC tunnel control TLVs Types  . . . . . . . . . . .  10
     8.3.  QUIC tunnel control Error Codes . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  12
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Mobile devices such as laptops, smartphones or tablets have different
   requirements than the traditional fixed devices.  These mobile
   devices often change their network attachment.  They are often
   attached to trusted networks, but sometimes they need to be connected
   to untrusted networks where their communications can be eavesdropped,
   filtered or modified.  In these situations, the classical approach is
   to rely on VPN protocols such as DTLS or IPSec.  These VPN protocols
   provide the encryption and authentication functions to protect those
   mobile clients from malicious behaviors in untrusted networks.

Piraux, et al.             Expires 6 May 2021                   [Page 2]
Internet-Draft             QUIC Tunnel Session             November 2020

   Today's mobile devices are often multihomed and many expect to be
   able to perform seamless handovers from one access network to another
Show full document text