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

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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-J. Montpetit
Expires: January 9, 2020                                  Triangle Video
                                                                 V. Roca
                                                                   INRIA
                                                               F. Michel
                                                               UCLouvain
                                                            July 8, 2019

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

Abstract

   This document focuses on the integration of FEC coding in the QUIC
   transport protocol, in order to recover from packet losses.  This
   document does not specify any FEC code but defines mechanisms to
   negotiate and integrate FEC Schemes in QUIC.  By using proactive loss
   recovery, it is expected to improve QUIC performance in sessions
   impacted by packet losses.  More precisely it is expected to improve
   QUIC performance with real-time sessions (since FEC coding makes
   packet loss recovery insensitive to the round trip time), with short
   sessions (since FEC coding can help recovering from tail losses more
   rapidely than through retransmissions), with multicast sessions
   (since the same repair packet can recover several different losses at
   several receivers), and with multipath sessions (since repair packets
   add diversity and flexibility).

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 January 9, 2020.

Swett, et al.            Expires January 9, 2020                [Page 1]
Internet-Draft               Coding for QUIC                   July 2019

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions and Abbreviations . . . . . . . . . . . . . . . .   3
   3.  General Design Considerations . . . . . . . . . . . . . . . .   4
     3.1.  FEC Code versus FEC Scheme, Block Codes versus Sliding
           Window Codes  . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  FEC Scheme Negotiation  . . . . . . . . . . . . . . . . .   5
     3.3.  FEC Protection Within an Encrypted Channel  . . . . . . .   5
     3.4.  About Middleboxes . . . . . . . . . . . . . . . . . . . .   5
   4.  FEC Protection Principles . . . . . . . . . . . . . . . . . .   5
     4.1.  Cross Packet Frames FEC Encoding  . . . . . . . . . . . .   5
     4.2.  Source Symbol Definition  . . . . . . . . . . . . . . . .   6
       4.2.1.  Packet Payload to Packet Chunk Mapping  . . . . . . .   6
       4.2.2.  Packet Chunk to Source Symbol Mapping . . . . . . . .   7
         4.2.2.1.  Open questions: Content of Source Symbols
                   Metadata? Removing certain frames from FEC
                   protection? . . . . . . . . . . . . . . . . . . .   9
       4.2.3.  Source Symbol Size (E) Considerations . . . . . . . .  10
     4.3.  Source Symbol Signaling . . . . . . . . . . . . . . . . .  11
     4.4.  Repair Symbol Signaling . . . . . . . . . . . . . . . . .  11
     4.5.  Signaling a Symbol Recovery . . . . . . . . . . . . . . .  11
     4.6.  About Gaps in the Set of Source Symbols Considered During
           Encoding  . . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  FEC Scheme Negotiation in QUIC  . . . . . . . . . . . . . . .  12
     5.1.  FEC Scheme Selection Process  . . . . . . . . . . . . . .  13
     5.2.  FEC Scheme Configuration Information  . . . . . . . . . .  14
Show full document text