RFC 5125: Reclassification of RFC 3525 to Historic
In plain English — editorial summary, not part of the RFC
This document reclassifies RFC 3525, Gateway Control Protocol Version 1, to Historic Status. This memo also obsoletes RFC 3525. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5125
- Published
- February 2008
- Authors
- T. Taylor
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
- Obsoletes:
- RFC 3525
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 2885 (2000)
- RFC 2886 (2000)
- RFC 3015 (2000)
- RFC 3525 (2003)
- RFC 5125 (2008)
Read the full history of Reclassification of RFC 3525 to Historic →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3015Megaco Protocol Version 1.0Obsoleted
November 2000
- RFC 2886Megaco ErrataObsoleted
August 2000
- RFC 2885Megaco Protocol version 0.8Obsoleted
August 2000
- RFC 3149MGCP Business Phone PackagesCurrent
September 2001
- RFC 2897Proposal for an MGCP Advanced Audio PackageCurrent
August 2000
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 3057ISDN Q.921-User Adaptation LayerObsoleted
February 2001
- RFC 2719Framework Architecture for Signaling TransportCurrent
October 1999
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?