QUIC Performance
draft-banks-quic-performance-00

Document Type Active Internet-Draft (individual)
Author Nick Banks 
Last updated 2020-12-23
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                           N. Banks
Internet-Draft                                     Microsoft Corporation
Intended status: Experimental                          December 23, 2020
Expires: June 26, 2021

                            QUIC Performance
                    draft-banks-quic-performance-00

Abstract

   The QUIC performance protocol provides a simple, general-purpose
   protocol for testing the performance characteristics of a QUIC
   implementation.  With this protocol a generic server can support any
   number of client-driven performance tests and configurations.
   Standardizing the performance protocol allows for easy comparisons
   across different QUIC implementations.

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 June 26, 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

Banks                     Expires June 26, 2021                 [Page 1]
Internet-Draft                  QUIC-PERF                  December 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terms and Definitions . . . . . . . . . . . . . . . . . .   3
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Protocol Negotiation  . . . . . . . . . . . . . . . . . .   3
     2.2.  Configuration . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Streams . . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.3.1.  Encoding Server Response Size . . . . . . . . . . . .   4
       2.3.2.  Bidirectional vs Unidirectional Streams . . . . . . .   4
   3.  Example Performance Scenarios . . . . . . . . . . . . . . . .   4
     3.1.  Single Connection Bulk Throughput . . . . . . . . . . . .   4
     3.2.  Requests Per Second . . . . . . . . . . . . . . . . . . .   5
     3.3.  Handshakes Per Second . . . . . . . . . . . . . . . . . .   6
     3.4.  Throughput Fairness Index . . . . . . . . . . . . . . . .   6
     3.5.  Maximum Number of Idle Connections  . . . . . . . . . . .   7
   4.  Things to Note  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  What Data Should be Sent? . . . . . . . . . . . . . . . .   7
     4.2.  Ramp up Congestion Control or Not?  . . . . . . . . . . .   7
     4.3.  Disabling Encryption  . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The various QUIC implementations are still quite young and not
   exhaustively tested for many different performance heavy scenarios.
   Some have done their own testing, but many are just starting this
   process.  Additionally, most only test the performance between their
   own client and server.  The QUIC performance protocol aims to
   standardize the performance testing mechanisms.  This will hopefully
   achieve the following:

   o  Remove the need to redesign a performance test for each QUIC
      implementation.

   o  Provide standard test cases that can produce performance metrics
      that can be easily compared across different configurations and
      implementations.

   o  Allow for easy cross-implementation performance testing.

Banks                     Expires June 26, 2021                 [Page 2]
Internet-Draft                  QUIC-PERF                  December 2020

1.1.  Terms and Definitions

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text