RFC 2885: Megaco Protocol version 0.8
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3015.
Current document in this lineage: RFC 5125 — Reclassification of RFC 3525 to Historic
In plain English — editorial summary, not part of the RFC
This document is common text with Recommendation H.248 as redetermined in Geneva, February 2000. It must be read in conjunction with the Megaco Errata, RFC 2886. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2885
- Published
- August 2000
- Authors
- F. Cuervo; N. Greene; C. Huitema; A. Rayhan; B. Rosen; J. Segers
- Status
- HISTORIC
- Stream
- IETF
- Area
- rai
- Pages
- 170
- Also known as
- —
- Obsoleted by:
- RFC 3015
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of Reclassification of RFC 3525 to Historic →
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 2886Megaco ErrataObsoleted
August 2000
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 5125Reclassification of RFC 3525 to HistoricCurrent
February 2008
- RFC 2897Proposal for an MGCP Advanced Audio PackageCurrent
August 2000
- RFC 2719Framework Architecture for Signaling TransportCurrent
October 1999
- RFC 3057ISDN Q.921-User Adaptation LayerObsoleted
February 2001
- RFC 3149MGCP Business Phone PackagesCurrent
September 2001
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
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?