Manageability of the QUIC Transport Protocol
draft-ietf-quic-manageability-07

Document Type Active Internet-Draft (quic WG)
Last updated 2020-07-08
Replaces draft-kuehlewind-quic-manageability
Stream IETF
Intended RFC status Informational
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Jul 2020 - QUIC Applicability a... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      M. Kuehlewind
Internet-Draft                                                  Ericsson
Intended status: Informational                               B. Trammell
Expires: 9 January 2021                                           Google
                                                             8 July 2020

              Manageability of the QUIC Transport Protocol
                    draft-ietf-quic-manageability-07

Abstract

   This document discusses manageability of the QUIC transport protocol,
   focusing on caveats impacting network operations involving QUIC
   traffic.  Its intended audience is network operators, as well as
   content providers that rely on the use of QUIC-aware middleboxes,
   e.g. for load balancing.

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

Kuehlewind & Trammell    Expires 9 January 2021                 [Page 1]
Internet-Draft             QUIC Manageability                  July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
   2.  Features of the QUIC Wire Image . . . . . . . . . . . . . . .   4
     2.1.  QUIC Packet Header Structure  . . . . . . . . . . . . . .   4
     2.2.  Coalesced Packets . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Use of Port Numbers . . . . . . . . . . . . . . . . . . .   6
     2.4.  The QUIC handshake  . . . . . . . . . . . . . . . . . . .   6
     2.5.  Integrity Protection of the Wire Image  . . . . . . . . .  11
     2.6.  Connection ID and Rebinding . . . . . . . . . . . . . . .  11
     2.7.  Packet Numbers  . . . . . . . . . . . . . . . . . . . . .  11
     2.8.  Version Negotiation and Greasing  . . . . . . . . . . . .  11
   3.  Network-visible information about QUIC flows  . . . . . . . .  12
     3.1.  Identifying QUIC traffic  . . . . . . . . . . . . . . . .  12
       3.1.1.  Identifying Negotiated Version  . . . . . . . . . . .  13
       3.1.2.  Rejection of Garbage Traffic  . . . . . . . . . . . .  13
     3.2.  Connection confirmation . . . . . . . . . . . . . . . . .  13
     3.3.  Application Identification  . . . . . . . . . . . . . . .  14
     3.4.  Flow association  . . . . . . . . . . . . . . . . . . . .  14
     3.5.  Flow teardown . . . . . . . . . . . . . . . . . . . . . .  14
     3.6.  Flow symmetry measurement . . . . . . . . . . . . . . . .  15
     3.7.  Round-Trip Time (RTT) Measurement . . . . . . . . . . . .  15
       3.7.1.  Measuring initial RTT . . . . . . . . . . . . . . . .  15
       3.7.2.  Using the Spin Bit for Passive RTT Measurement  . . .  15
   4.  Specific Network Management Tasks . . . . . . . . . . . . . .  17
     4.1.  Stateful treatment of QUIC traffic  . . . . . . . . . . .  17
     4.2.  Passive network performance measurement and
           troubleshooting . . . . . . . . . . . . . . . . . . . . .  18
     4.3.  Server cooperation with load balancers  . . . . . . . . .  18
     4.4.  DDoS Detection and Mitigation . . . . . . . . . . . . . .  18
     4.5.  UDP Policing  . . . . . . . . . . . . . . . . . . . . . .  19
     4.6.  Distinguishing acknowledgment traffic . . . . . . . . . .  19
     4.7.  QoS support and ECMP  . . . . . . . . . . . . . . . . . .  19
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  20
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
Show full document text