Considerations for Unreliable Streams in QUIC
draft-tiesel-quic-unreliable-streams-01

Document Type Active Internet-Draft (individual)
Last updated 2017-10-30
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
QUIC Working Group                                             P. Tiesel
Internet-Draft                                                 M. Palmer
Intended status: Informational                         B. Chandrasekaran
Expires: May 3, 2018                                         A. Feldmann
                                                               TU Berlin
                                                                  J. Ott
                                                               TU Munich
                                                        October 30, 2017

             Considerations for Unreliable Streams in QUIC
                draft-tiesel-quic-unreliable-streams-01

Abstract

   This memo outlines how to support unreliable streams as well as
   partially-reliable streams within QUIC.  The intention of this
   document is to collect requirements and considerations, to frame the
   design space, and to give an example how unreliable stream support
   could be realized.

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 May 3, 2018.

Copyright Notice

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

Tiesel, et al.             Expires May 3, 2018                  [Page 1]
Internet-Draft           QUIC Unreliable Streams            October 2017

   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.

Table of Contents

   1.  Conventions and Definitions . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Modes of Unreliable Transmission  . . . . . . . . . . . . . .   3
   4.  Protocol Considerations . . . . . . . . . . . . . . . . . . .   3
     4.1.  Unreliable Stream Support Negotiation . . . . . . . . . .   4
     4.2.  Stream as a Message . . . . . . . . . . . . . . . . . . .   4
     4.3.  Stream ID 0x0 . . . . . . . . . . . . . . . . . . . . . .   4
     4.4.  Congestion Control on Unreliable Streams  . . . . . . . .   4
     4.5.  Flow Control on Unreliable Streams  . . . . . . . . . . .   4
     4.6.  Stream Open . . . . . . . . . . . . . . . . . . . . . . .   5
     4.7.  Retransmission of Partially-Reliable Stream Data  . . . .   5
     4.8.  Stream Close  . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Application Interface Considerations  . . . . . . . . . . . .   5
     5.1.  Retransmissions within Unreliable Streams . . . . . . . .   5
     5.2.  Presentation of Unreliable Streams  . . . . . . . . . . .   6
     5.3.  Prioritization of Unreliable Streams  . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Implemenation Proposal . . . . . . . . . . . . . . .   8
     A.1.  Stream Identifiers  . . . . . . . . . . . . . . . . . . .   8
     A.2.  Stream Close  . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Conventions and Definitions

   The words "MUST", "MUST NOT", "SHALL", "SHALL NOT", "SHOULD", and
   "MAY" are used in this document.  It's not shouting; when these words
   are capitalized, they have a special meaning as defined in [RFC2119].

2.  Introduction

   This memo describes how QUIC can provide reliable, partially-
   reliable, and unreliable transmissions within the same connection.
Show full document text