QUIC Disable Encryption
draft-banks-quic-disable-encryption-00

Document Type Active Internet-Draft (individual)
Last updated 2020-08-11
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                            August 11, 2020
Expires: February 12, 2021

                        QUIC Disable Encryption
                 draft-banks-quic-disable-encryption-00

Abstract

   The disable_1rtt_encryption transport parameter can be used to
   negotiate the disablement of encryption on 1-RTT packets, allowing
   for reduced CPU load and improved performance.  This extension is
   only meant to be used in environments where both endpoints completely
   trust the path between themselves; not, for instance, on the open
   internet.

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 February 12, 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 February 12, 2021               [Page 1]
Internet-Draft              QUIC-DIS-ENCRYPT                 August 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 . . . . . . . . . . . . . . . . . .   2
     1.2.  Applicable Scenarios for Use  . . . . . . . . . . . . . .   2
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Disable 1-RTT Encryption Transport Parameter  . . . . . .   3
     2.2.  Negotiating the Extension . . . . . . . . . . . . . . . .   3
     2.3.  Disabling 1-RTT Encryption  . . . . . . . . . . . . . . .   4
     2.4.  Interactions with Path Changes  . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   By default QUIC Transport Protocol [I-D.ietf-quic-transport] provides
   secured (authenticated and encrypted) connections via a TLS
   handshake.  The handshake allows for the endpoints to be
   authenticated by a certificate and then securely generates shared
   secrets to encrypt the QUIC packet traffic.  Post-handshake, this
   packet encryption can occupy a considerable percentage of CPU usage,
   depending on the scenario.  Additionally, there are scenarios where
   the protections given by this encryption are either unnecessary or
   unwanted.  For these scenarios, this document defines an extension to
   the QUIC protocol to allow for mutually participating endpoints to
   negotiate the disablement of encryption for the 1-RTT packets sent
   after the handshake.

1.1.  Terms and Definitions

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

1.2.  Applicable Scenarios for Use

   QUIC connections are generally meant to always be encrypted, to
   prevent unauthenticated middleboxes from reading or modifying the
   QUIC packets.  This is the desired behavior for most environments;
   especially any that go over the open internet.  There are two
   possible scenarios where disabling packet encryption makes sense:

Banks                   Expires February 12, 2021               [Page 2]
Internet-Draft              QUIC-DIS-ENCRYPT                 August 2020

   o  Trusted Environment/Path - There are scenarios or environments
      where there is no need for the additional security measures of
Show full document text