RFC 2805: Media Gateway Control Protocol Architecture and Requirements
In plain English — editorial summary, not part of the RFC
This document describes protocol requirements for the Media Gateway Control Protocol between a Media Gateway Controller and a Media Gateway. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2805
- Published
- April 2000
- Authors
- N. Greene; M. Ramalho; B. Rosen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 45
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2824Call Processing Language Framework and RequirementsCurrent
May 2000
- RFC 2960Stream Control Transmission ProtocolObsoleted
October 2000
- RFC 3054Megaco IP Phone Media Gateway Application ProfileCurrent
January 2001
- 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 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
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?