Skip to main content

SDP Offer/Answer for RTP using QUIC as Transport

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Spencer Dawkins
Last updated 2022-08-01 (Latest revision 2022-01-28)
Replaces draft-dawkins-sdp-rtp-quic
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes these new SDP "proto" attribute values: "QUIC", "QUIC/RTP/SAVP", "QUIC/RTP/AVPF", and "QUIC/RTP/SAVPF", and describes how SDP Offer/Answer can be used to set up an RTP connection using QUIC as a transport protocol. These proto values are necessary to allow the use of QUIC as an underlying transport protocol for applications such as SIP and WebRTC that commonly use SDP as a session signaling protocol to set up RTP connections.


Spencer Dawkins

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)