Performance Metrics Subprotocol for QUIC
draft-kazuho-quic-perf-metrics-00

Document Type Active Internet-Draft (individual)
Last updated 2018-02-11
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                             K. Oku
Internet-Draft                                                    Fastly
Intended status: Standards Track                       February 12, 2018
Expires: August 16, 2018

                Performance Metrics Subprotocol for QUIC
                   draft-kazuho-quic-perf-metrics-00

Abstract

   This memo proposes a subprotocol that can be used to query the
   performance metrics of a QUIC path.

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 August 16, 2018.

Copyright Notice

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

Oku                      Expires August 16, 2018                [Page 1]
Internet-Draft              quic-perf-metrics              February 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  METRICS Packet  . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  REQUEST Subtype . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  RESPONSE Subtype  . . . . . . . . . . . . . . . . . . . .   6
     3.3.  DENY Subtype  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Server State  . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Observation of upstream loss, reorder, and round-trip time is crucial
   to diagnosing issues on the network.  With TCP, it is possible for an
   on-path device to make estimation of such metrics by observing the
   sequence number and the ACK packets being sent in clear.  But with
   QUIC, packet number is never used twice and ACK is encrypted, hence
   such on-path observation has become difficult.  There is also an
   ongoing discussion about encrypting the packet numbers to avoid
   ossification and also to miminize privacy concern.  Such change will
   make observation even more challenging.

   There have been proposals to include signals in each QUIC packet that
   conveys enough information for diagnosis but does not cause
   ossification nor privary issues.  However, it is difficult if not
   impossible to figure out an approach that will work well for the
   lifetime of a transport protocol.

   This memo proposes an alternative solution.  In the proposal, an on-
   path device willing to obtain the performance metrics of a QUIC path
   sends a query to the server, and the server responds with the
   necessary information to calculate such metrics.

   There are three primary benefits in the approach:

   o  Observation becomes an active action rather than passive, giving
      the endpoints a chance to record observation attempts as well as
      rejecting undesirable ones.

   o  Observation becomes accurate due to the endpoints' knowledge of
      what is being exchanged encypted.

   o  Flexibility against issues (both performance- and privacy-related)
      that might arise in the future, since bits for observation no

Oku                      Expires August 16, 2018                [Page 2]
Internet-Draft              quic-perf-metrics              February 2018

      longer exists hard-coded in each packet.  The metrics protocol can
      evolve indenpendently to the QUIC transport protocol.

2.  Overview

   An on-path device that is willing to query the performance metrics of
   a QUIC path sends a METRICS packet of subtype REQUEST to the server-
   side endpoint of the path.

   When receiving the request packet, A QUIC server sends a response to
Show full document text