Coding for QUIC
draft-swett-nwcrg-coding-for-quic-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-04
Stream (None)
Intended RFC status (None)
Formats 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)
nwcrg                                                           I. Swett
Internet-Draft                                                    Google
Intended status: Informational                              M. Montpetit
Expires: September 4, 2018                                Triangle Video
                                                                 V. Roca
                                                                   INRIA
                                                           March 3, 2018

                            Coding for QUIC
                  draft-swett-nwcrg-coding-for-quic-00

Abstract

   This document introduces means of integrating loss recovery coding in
   the proposed QUIC transport protocol.  While no specific code is
   specified, the document defines how to integrate recent coding
   research to recover packets lost in QUIC sessions.  This research
   targets the codes themselves as well as how to use them in real world
   protocols.  Loss recover should improve the QUIC performance in
   sessions impacted by loss.

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 September 4, 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

Swett, et al.           Expires September 4, 2018               [Page 1]
Internet-Draft               Coding for QUIC                  March 2018

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Design Considerations . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Framing . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Coding Symbol . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Negotiation . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     3.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Appendix A.  Appendix: Reference Algorithms . . . . . . . . . . .   5
   Appendix B.  Appendix: Participating Middleboxes  . . . . . . . .   5
   Appendix C.  Appendix: APIS . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   QUIC is a new transport that wants to improve network performance by
   enabling out of order delivery, partial reliability, and methods of
   recovery besides retransmission while also improving security.  This
   document specifies a design to enable error correcting codes to be
   used to recover lost data in QUIC.  Error correcting codes have the
   ability to recover packet losses in less than 1 round trip at the
   cost of more total data transmission and decoding delay.  The design
   does not specify a code but allows to negotiate it hence assumes that
   more than one code could be offered concurrently as well as leaving
   open the possibility of new codes in the future.  Without loss of
   generality in the document we consider that the encoding operations
   compute a linear combination of QUIC packets.  Terms and definitions
   that apply to coding are available in RFC xxxx [nc-taxonomy]

1.1.  Requirements Language

   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 RFC 2119 [RFC2119].

Swett, et al.           Expires September 4, 2018               [Page 2]
Internet-Draft               Coding for QUIC                  March 2018

2.  Design Considerations

2.1.  Framing

   A new QUIC frame type is defined within the current framework
Show full document text