RFC 9071: RTP-Mixer Formatting of Multiparty Real-Time Text
In plain English — editorial summary, not part of the RFC
This document provides enhancements of real-time text (as specified in RFC 4103) suitable for mixing in a centralized conference model, enabling source identification and rapidly interleaved transmission of text from different sources. The intended use is for real-time text mixers and participant endpoints capable of providing an efficient presentation or other treatment of a multiparty real-time text session. The specified mechanism builds on the standard use of the Contributing Source (CSRC) list in the Real-time Transport Protocol (RTP) packet for source identification. The method makes use of the same "text/t140" and "text/red" formats as for two-party sessions. Solutions using multiple RTP streams in the same RTP session are briefly mentioned, as they could have some benefits over the RTP-mixer model. The RTP-mixer model was selected to be used for the fully specified solution in this document because it can be applied to a wide range of existing RTP implementations. A capability exchange is specified so that it can be verified that a mixer and a participant can handle the multiparty-coded real-time text stream using the RTP-mixer method. The capability is indicated by the use of a Session Description Protocol (SDP) (RFC 8866) media attribute, "rtt-mixer". This document updates RFC 4103 ("RTP Payload for Text Conversation"). A specification for how a mixer can format text for the case when the endpoint is not multiparty aware is also provided.
Document record
- Document ID
- RFC9071
- Published
- July 2021
- Authors
- G. Hellström
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 35
- Also known as
- —
- Updates:
- RFC 4103
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6465A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level IndicationCurrent
December 2011
- RFC 6464A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level IndicationCurrent
December 2011
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
- RFC 8855The Binary Floor Control Protocol (BFCP)Current
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?