SDP Offer/Answer for RTP using QUIC as Transport - Design Issues
draft-dawkins-avtcore-sdp-rtp-quic-issues-00
Document | Type |
Expired Internet-Draft
(avtcore WG)
Expired & archived
|
|
---|---|---|---|
Author | Spencer Dawkins | ||
Last updated | 2022-12-24 (Latest revision 2022-06-22) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Candidate for WG Adoption | |
Document shepherd | Dr. Bernard D. Aboba | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | bernard.aboba@gmail.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document is intended to capture SDP aspects of RTP over QUIC design issues that have arisen, been discussed by the AVTCORE working group, and have reached a resolution that can be included in "SDP Offer/Answer for RTP using QUIC as Transport". This document is a companion document to "SDP Offer/Answer for RTP using QUIC as Transport". That document focuses on the description and registration of SDP "proto" attribute parameters with IANA, to allow applications that rely on SDP Offer/Answer to negotiate the QUIC protocol as an encapsulation for RTP. "SDP Offer/Answer for RTP using QUIC as Transport" is itself a companion document to "RTP over QUIC", and follows the lead of the latter specification as it evolves.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)