An Interface to the QUIC Transport Protocol
draft-pauly-quic-interface-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-10
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                                           T. Pauly
Internet-Draft                                                E. Kinnear
Intended status: Standards Track                              Apple Inc.
Expires: March 14, 2019                               September 10, 2018

              An Interface to the QUIC Transport Protocol
                     draft-pauly-quic-interface-00

Abstract

   This document defines the abstract application interface to the QUIC
   transport protocol.  This allows applications to use a standard
   interface to directly interact with the QUIC protocol for cases that
   may not be using an HTTP mapping.

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 March 14, 2019.

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
   (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.

Pauly & Kinnear          Expires March 14, 2019                 [Page 1]
Internet-Draft               QUIC Interface               September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Specification of Requirements . . . . . . . . . . . . . .   3
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  QUIC Streams  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Transport Connection Interface  . . . . . . . . . . . . .   3
     2.3.  Transferring Messages over Streams  . . . . . . . . . . .   3
   3.  API Mappings  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Transport Connection as QUIC Connection . . . . . . . . .   4
     3.2.  Transport Connection as QUIC Stream . . . . . . . . . . .   5
   4.  Racing QUIC Connections . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The QUIC Transport Protocol [I-D.ietf-quic-transport] defines a
   mechanism for allowing applications to communicate as clients or
   servers to securely send and receive data over multiplexed streams
   associated with a single cryptographic state.  While some
   applications may not need to directly interact with QUIC as a
   transport if they use HTTP over QUIC, others will need to send and
   recieve data directly over the transport.

   Defining a standard application interface to QUIC as a transport has
   several benefits to applications as they adopt the protocol.  These
   benefits are expressed in the following requirements for a transport
   interface to QUIC:

   o  Many of the benefits of QUIC, such as reducing head-of-line
      blocking or being able to send zero-RTT data, can be lost if the
      transport API does not provide adequate support.  The interface
      SHOULD allow such features to be accessed in a reliable fashion.

   o  Various implementations of the QUIC protocol SHOULD provide
      similar transport interfaces in order to allow applications to
      easily adopt them across different platforms and deployments.

   o  The interface to configure QUIC security properties SHOULD be
      restricted to a standard set of functionality to ensure that
      applications cannot easily diminish the security properties of the
      protocol, while still retaining control over the configuration.

Pauly & Kinnear          Expires March 14, 2019                 [Page 2]
Internet-Draft               QUIC Interface               September 2018

1.1.  Specification of Requirements
Show full document text