QUIC Multiplexing
draft-aboba-avtcore-quic-multiplexing-04

Document Type Active Internet-Draft (individual)
Last updated 2020-01-28
Stream (None)
Intended RFC status (None)
Formats plain text 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)
AVTCORE Working Group                                           B. Aboba
INTERNET-DRAFT                                     Microsoft Corporation
Category: Informational                                      P. Thatcher
Expires: July 28, 2020                                            Google
                                                              C. Perkins
                                                   University of Glasgow
                                                         28 January 2020

                           QUIC Multiplexing
              draft-aboba-avtcore-quic-multiplexing-04.txt

Abstract

   If QUIC is to be used for peer-to-peer data transport with NAT
   traversal, then it is necessary to be able to demultiplex QUIC and
   other protocols used in WebRTC on a single UDP port. This memo
   discusses a proposed scheme for demultiplexing.

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 http://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 28 July 2020.

Aboba, et. al                 Informational                     [Page 1]
INTERNET-DRAFT              QUIC Multiplexing            28 January 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
   (http://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.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Solution . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.1. Informative references  . . . . . . . . . . . . . . . . . .  5
   Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1.  Introduction

   QUIC [I-D.ietf-quic-transport] is a new network transport protocol.
   While it is initially intended as a replacement for TCP in order to
   better support HTTP/2 [RFC7540], with the introduction of datagram
   support [I-D.pauly-quic-datagram] it will also support unreliable as
   well as reliable transport.  HTTP is an asymmetric client-server
   protocol, but other uses of QUIC support peer-to-peer operation and
   so will need effective NAT traversal using ICE [RFC5245], which which
   makes use of STUN [RFC5389] and TURN [RFC5766] to discover NAT
   bindings.  Therefore for QUIC to be utilized for peer-to-peer data
   transport, QUIC and STUN must be able to multiplex on the same port.

   In a WebRTC scenario where RTP is used to transport audio and video
   and QUIC is used for data exchange, SRTP [RFC3711] is keyed using
   DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP [RFC3550], STUN, TURN,
   DTLS [RFC6347] and QUIC will need to be multiplexed on the same port.

   Within the W3C, a Javascript API for the use of QUIC for peer-to-peer
   data exchange [WEBRTC-QUIC] is under development within the ORTC
   Community Group, and an Origin Trial [WEBRTC-QUIC-TRIAL] implementing

Aboba, et. al                 Informational                     [Page 2]
INTERNET-DRAFT              QUIC Multiplexing            28 January 2020

   an early version of this API shipped in the Chrome and Edge browsers.
   Due to lack of demultiplexing support, the Origin Trial could only
   support peer-to-peer use of QUIC over a standalone ICE transport, as
   defined in [WEBRTC-ICE].

   As noted in [RFC7983] Figure 3, protocol demultiplexing currently
   relies upon differentiation based on the first octet, as follows:

                +----------------+
                |        [0..3] -+--> forward to STUN
                |                |
Show full document text