RFC 1889: RTP: A Transport Protocol for Real-Time Applications
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3550.
Current version: RFC 3550 — RTP: A Transport Protocol for Real-Time Applications
In plain English — editorial summary, not part of the RFC
This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1889
- Published
- January 1996
- Authors
- Audio-Video Transport Working Group; H. Schulzrinne; S. Casner; R. Frederick; V. Jacobson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 75
- Also known as
- —
- Obsoleted by:
- RFC 3550
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 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 2862RTP Payload Format for Real-Time PointersCurrent
June 2000
- RFC 6416RTP Payload Format for MPEG-4 Audio/Visual StreamsCurrent
October 2011
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
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?