RFC 1890: RTP Profile for Audio and Video Conferences with Minimal Control
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3551.
Current version: RFC 3551 — RTP Profile for Audio and Video Conferences with Minimal Control
In plain English — editorial summary, not part of the RFC
This memo describes a profile for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1890
- Published
- January 1996
- Authors
- Audio-Video Transport Working Group; H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
- Obsoleted by:
- RFC 3551
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 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 2805Media Gateway Control Protocol Architecture and RequirementsCurrent
April 2000
- RFC 2824Call Processing Language Framework and RequirementsCurrent
May 2000
- RFC 2960Stream Control Transmission ProtocolObsoleted
October 2000
- RFC 4582The Binary Floor Control Protocol (BFCP)Obsoleted
November 2006
- RFC 1901Introduction to Community-based SNMPv2Current
January 1996
- RFC 1902Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
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?