Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Sending Multiple Types of Media in a Single RTP Session
RFC 8860

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2021-11-08	Tina Dang	Posted related IPR disclosure Qualcomm Incorporated's Statement about IPR related to RFC 8860
2021-11-08	Tina Dang	Posted related IPR disclosure Qualcomm Incorporated's Statement about IPR related to RFC 8860
2021-11-08	Tina Dang	Posted related IPR disclosure Qualcomm Incorporated's Statement about IPR related to RFC 8860
2021-01-18	(System)	Received changes through RFC Editor sync (created alias RFC 8860, changed abstract to 'This document specifies how an RTP session can contain RTP streams … Received changes through RFC Editor sync (created alias RFC 8860, changed abstract to 'This document specifies how an RTP session can contain RTP streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP specifications (RFCs 3550 and 3551), and thus this document updates RFCs 3550 and 3551 to enable this behaviour for applications that satisfy the applicability for using multiple media types in a single RTP session.', changed pages to 15, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-01-18, changed IESG state to RFC Published, created updates relation between draft-ietf-avtcore-multi-media-rtp-session and RFC 3550, created updates relation between draft-ietf-avtcore-multi-media-rtp-session and RFC 3551)
2021-01-18	(System)	RFC published