Network Enhancements for QUIC
draft-abilash-quic-network-00

Document Type Active Internet-Draft (individual)
Last updated 2017-01-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
QUIC                                                            A. Menon
Internet-Draft                                              R. Mukherjee
Intended status: Standards Track                          128 Technology
Expires: July 8, 2017                                    January 4, 2017

                     Network Enhancements for QUIC
                     draft-abilash-quic-network-00

Abstract

   QUIC aims to improve performance by multiplexing streams and various
   other enhancements [I-D.ietf-quic-transport].  QUIC performs better
   than existing transport protocols in most cases.  However, its
   performance suffers compared to HTTP under very high bandwidth when
   large amounts of data needs to be downloaded [MEG2016].  This is
   because QUIC is an end to end protocol and provides no means for the
   intermediate network elements to contribute to QUIC improvements.
   This draft proposes a change to the QUIC protocol header that will
   allow session aware routers and other middleboxes to prioritize
   streams in QUIC packets, divert high priority streams to low loss
   paths, and adjust packet pacing on a per stream basis.  This opens
   the door to many possible future in-network enhancements.

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 July 8, 2017.

Copyright Notice

   Copyright (c) 2017 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

Menon & Mukherjee         Expires July 8, 2017                  [Page 1]
Internet-Draft                QUIC Network                  January 2017

   (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
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  QUIC Network  . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Stream Header . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Stream Demultiplexing and Multiplexing  . . . . . . . . .   4
     3.3.  Multi-Path  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Moving Streams  . . . . . . . . . . . . . . . . . . . . .   5
     3.5.  QUIC State Machine  . . . . . . . . . . . . . . . . . . .   5
     3.6.  Stream based Packet Pacing  . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   QUIC employs stream multiplexing by interleaving frames from multiple
   streams into one conversation between QUIC endpoints.  These streams
   are identified by a Stream ID and multiplexed on top of the same UDP
   flow.  These streams do not have any priority assigned to them and
   all of them are treated with the same priority.  A high priority
   stream is affected by network conditions similar to low priority
   streams.  [MEG2016] shows studies where HTTP performs better than
   QUIC because it opens multiple connections for each stream.  When
   large amounts of data are to be downloaded and when there is high
   bandwidth available, QUIC underperforms compared to HTTP.

   This draft proposes to make the Stream ID visible in the public
   header and add a priority byte.  Session aware routers and other
Show full document text