RFC 4351: Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream
In plain English — editorial summary, not part of the RFC
This memo describes how to carry real-time text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140. One payload format is described for transmitting audio and text data within a single RTP session. This RTP payload description recommends a method to include redundant text from already transmitted packets in order to reduce the risk of text loss caused by packet loss. This memo defines a Historic Document for the Internet community.
Document record
- Document ID
- RFC4351
- Published
- January 2006
- Authors
- G. Hellstrom; P. Jones
- Status
- HISTORIC
- Stream
- IETF
- Area
- rai
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4353A Framework for Conferencing with the Session Initiation Protocol (SIP)Current
February 2006
- RFC 4348Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio CodecUpdated
January 2006
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
- RFC 4375Emergency Telecommunications Services (ETS) Requirements for a Single Administrative DomainCurrent
January 2006
- RFC 4376Requirements for Floor Control ProtocolsCurrent
February 2006
- RFC 4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
- RFC 4320Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
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?