RFC 2793: RTP Payload for Text Conversation
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4103.
Current version: RFC 4103 — RTP Payload for Text Conversation
In plain English — editorial summary, not part of the RFC
This memo describes how to carry text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2793
- Published
- May 2000
- Authors
- G. Hellstrom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 4103
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.
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 2862RTP Payload Format for Real-Time PointersCurrent
June 2000
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 2326Real Time Streaming Protocol (RTSP)Obsoleted
April 1998
- RFC 3357One-way Loss Pattern Sample MetricsCurrent
August 2002
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?