Skip to main content

SDP Offer/Answer for RTP using QUIC as Transport
draft-dawkins-sdp-rtp-quic-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Spencer Dawkins
Last updated 2021-09-08
Replaced by draft-dawkins-avtcore-sdp-rtp-quic
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-dawkins-avtcore-sdp-rtp-quic
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:

Abstract

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 that commonly use SDP as a session signaling protocol to set up RTP connections with UDP as its underlying transport protocol, such as SIP and WebRTC.

Authors

Spencer Dawkins

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