Deadline-aware Transport Protocol
draft-shi-quic-dtp-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

QUIC                                                              Y. Cui
Internet-Draft                                                    Z. Liu
Intended status: Informational                                    H. Shi
Expires: January 26, 2021                                       J. Zhang
                                                     Tsinghua University
                                                                K. Zheng
                                                                 W. Wang
                                                                  Huawei
                                                           July 25, 2020

                   Deadline-aware Transport Protocol
                         draft-shi-quic-dtp-02

Abstract

   This document defines Deadline-aware Transport Protocol (DTP) to
   provide block-based deliver-before-deadline transmission.  The
   intention of this memo is to describe a mechanism to fulfill
   unreliable transmission based on QUIC as well as how to enhance
   timeliness of data delivery.

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 26, 2021.

Copyright Notice

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

Cui, et al.             Expires January 26, 2021                [Page 1]
Internet-Draft                     DTP                         July 2020

   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.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of DTP . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Abstraction . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Architecture of DTP . . . . . . . . . . . . . . . . . . .   5
     3.3.  Deadline-aware Scheduler  . . . . . . . . . . . . . . . .   7
     3.4.  Deadline-aware Redundancy . . . . . . . . . . . . . . . .   7
     3.5.  Loss Detection and Congestion Control . . . . . . . . . .   9
   4.  Extension of QUIC . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  New Frame: BLOCK_INFO Frame . . . . . . . . . . . . . . .  10
     4.2.  Adjusted QUIC Frame: Timestamped ACK Frame  . . . . . . .  10
     4.3.  Redundancy Packet . . . . . . . . . . . . . . . . . . . .  11
   5.  DTP Use Cases . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Block Based Real Time Application . . . . . . . . . . . .  12
     5.2.  API of DTP  . . . . . . . . . . . . . . . . . . . . . . .  12
       5.2.1.  Data Transmission Functions . . . . . . . . . . . . .  13
       5.2.2.  Feedback Functions  . . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Many emerging applications have the deadline requirement for their
   data transmission.  However, current transport layer protocol like
   TCP [RFC0793] and UDP [RFC0768] only provide primitive connection
   establishment and data sending service.  This document proposes a new
   transport protocol atop QUIC [QUIC] to deliver application data
   before end-to-end deadline.

1.1.  Conventions

   The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
   they appear in this document, are to be interpreted as described in
   [RFC2119].

Cui, et al.             Expires January 26, 2021                [Page 2]
Internet-Draft                     DTP                         July 2020