UpdatedPROPOSED STANDARDIETF stream

RFC 4103: RTP Payload for Text Conversation

Still current, but amended. Parts of this document are changed or extended by RFC 9071. Read both.

In plain English — editorial summary, not part of the RFC

This memo obsoletes RFC 2793; it 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 text on a separate RTP session dedicated for the transmission of text. 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. [STANDARDS-TRACK]

Document record

Document ID
RFC4103
Published
June 2005
Authors
G. Hellstrom; P. Jones
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
20
Also known as
Obsoletes:
RFC 2793
Updated by:
RFC 9071

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4103-rtp-payload-for-text-conversation