QRT: QUIC RTP Tunnelling
draft-hurst-quic-rtp-tunnelling-00

Document Type Active Internet-Draft (individual)
Author Sam Hurst 
Last updated 2020-10-30
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                           S. Hurst
Internet-Draft                                BBC Research & Development
Intended status: Informational                           30 October 2020
Expires: 3 May 2021

                        QRT: QUIC RTP Tunnelling
                   draft-hurst-quic-rtp-tunnelling-00

Abstract

   QUIC is a UDP-based transport protocol for stream-orientated,
   congestion-controlled, secure, multiplexed data transfer.  RTP
   carries real-time data between endpoints, and the accompanying
   control protocol RTCP allows monitoring and control of the transfer
   of such data.  With RTP and RTCP being agnostic to the underlying
   transport protocol, it is possible to multiplex both the RTP and
   associated RTCP flows into a single QUIC connection to take advantage
   of QUIC features such as low-latency setup and strong TLS-based
   security.

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 3 May 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 carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components

Hurst                      Expires 3 May 2021                   [Page 1]
Internet-Draft                     QRT                      October 2020

   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 and Definitions . . . . . . . . . . . . . . .   3
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases for an RTP Mapping over QUIC  . . . . . . . . . . .   4
     2.1.  Live Event Contribution Feed  . . . . . . . . . . . . . .   4
     2.2.  Audio and Video Conference via a Central Server . . . . .   5
   3.  QRT Sessions  . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  RTP Sessions  . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  QRT Flow Identifier . . . . . . . . . . . . . . . . . . .   6
     4.2.  RTCP Mapping  . . . . . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Restricted RTCP Packet Types  . . . . . . . . . . . .   7
   5.  Loss Recovery and Retransmission  . . . . . . . . . . . . . .   8
   6.  Using the Session Description Protocol to Advertise QRT
           Sessions  . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Using the Session Description Protocol to Advertise QRT
           Sessions using RTP Retransmission . . . . . . . . . . . .   9
   7.  Exposing Round-Trip Time to RTP applications  . . . . . . . .  10
   8.  Protocol Identifier . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Draft Version Identification  . . . . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Registration of Protocol Identification String . . . . .  11
     10.2.  Registration of SDP Protocol Identifier  . . . . . . . .  11
     10.3.  Registration of SDP Attribute Field  . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     11.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The Real-time Transport Protocol (RTP) [RFC3550] provides end-to-end
   network transport functions suitable for applications transmitting
   data, such as audio and video, over multicast or unicast network
   services for the purposes of telephony, video streaming, conferencing
   and other real-time applications.

   The QUIC transport protocol is a UDP-based stream-orientated and
Show full document text