Partially Reliable Message Streams for QUIC
draft-lubashev-quic-partial-reliability-03

Document Type Active Internet-Draft (individual)
Last updated 2018-05-29
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                                                         I. Lubashev
Internet-Draft                                       Akamai Technologies
Intended status: Informational                              May 29, 2018
Expires: November 30, 2018

              Partially Reliable Message Streams for QUIC
               draft-lubashev-quic-partial-reliability-03

Abstract

   This memo introduces a new EXPIRED_STREAM_DATA frame to enable
   partial reliability for QUIC streams.  The EXPIRED_STREAM_DATA frame
   allows a sender to give up on retransmitting older parts of a stream
   and to notify the receiver about this decision.  The content of this
   draft is intended for merging into QUIC transport, recovery, and
   applicability drafts as a negotiable extension and/or QUIC Version 2
   transport feature.

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 November 30, 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
   (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

Lubashev                Expires November 30, 2018               [Page 1]
Internet-Draft                   quic-pr                        May 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Stream-per-Message Alternative  . . . . . . . . . . . . .   3
     2.2.  Partially Reliable Message Streams  . . . . . . . . . . .   3
     2.3.  Minimum retransmittable offset and smallest receive
           offset  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  EXPIRED_STREAM_DATA Frame . . . . . . . . . . . . . . . . . .   4
   4.  Sender Interface and Behavior . . . . . . . . . . . . . . . .   5
     4.1.  Communicating Message Boundary  . . . . . . . . . . . . .   5
     4.2.  Translating Application Offsets to QUIC Offsets . . . . .   5
     4.3.  Sender Behavior . . . . . . . . . . . . . . . . . . . . .   5
       4.3.1.  Coalescing Minimum Retransmittable Offset Updates . .   6
       4.3.2.  Example . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Receiver Interface and Behavior . . . . . . . . . . . . . . .   7
   6.  Retransmission of EXPIRED_STREAM_DATA . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Since version 00  . . . . . . . . . . . . . . . . . . . .   8
     9.2.  Since version 01  . . . . . . . . . . . . . . . . . . . .   8
     9.3.  Since version 02  . . . . . . . . . . . . . . . . . . . .   8
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   Some applications, especially applications with near real-time
   requirements, need transport that supports partially reliable streams
   - streams that deliver bytes in order but allow for applicaiton-
   controlled gaps.  These applications communicate using application-
   specific messages that are serialized over QUIC streams.
   Applications desire partially reliable streams when their messages
   expire and lose their usefulness due to later events (time passing,
Show full document text