metasystema.org
ObsoletedHISTORICIETF stream

RFC 3525: Gateway Control Protocol Version 1

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5125.

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 defines the protocol used between elements of a physically decomposed multimedia gateway, i.e., a Media Gateway and a Media Gateway Controller. The protocol presented in this document meets the requirements for a media gateway control protocol as presented in RFC 2805. This document replaces RFC 3015. It is the result of continued cooperation between the IETF Megaco Working Group and ITU-T Study Group 16. It incorporates the original text of RFC 3015, modified by corrections and clarifications discussed on the Megaco E-mail list and incorporated into the Study Group 16 Implementor's Guide for Recommendation H.248. The present version of this document underwent ITU-T Last Call as Recommendation H.248 Amendment 1. Because of ITU-T renumbering, it was published by the ITU-T as Recommendation H.248.1 (03/2002), Gateway Control Protocol Version 1. Users of this specification are advised to consult the H.248 Sub-series Implementors' Guide at http://www.itu.int/itudoc/itu-t/com16/implgd for additional corrections and clarifications. [STANDARDS-TRACK]

Document record

Document ID
RFC3525
Published
June 2003
Authors
C. Groves; M. Pantaleo; T. Anderson; T. Taylor
Status
HISTORIC
Stream
IETF
Area
rai
Pages
213
Also known as
—
Obsoletes:
RFC 3015
Obsoleted by:
RFC 5125

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 2885 (2000)
  2. RFC 2886 (2000)
  3. RFC 3015 (2000)
  4. RFC 3525 (2003)
  5. RFC 5125 (2008) ✓

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.

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?

canonical URL: /rfc/3525-gateway-control-protocol-version-1