Media Gateway Control (megaco)

Last Modified: 2006-03-24

Chair(s):

Real-time Applications and Infrastructure Area Director(s):

Real-time Applications and Infrastructure Area Advisor:

Mailing Lists:

General Discussion: megaco@ietf.org
To Subscribe: megaco-request@ietf.org
In Body: subscribe megaco
Archive: http://www.ietf.org/mail-archive/web/megaco/index.html

Description of Working Group:

Note: There is an additional file storage area at
      ftp://standards.nortelnetworks.com/megaco/docs/

      There is a Web interface (up to February 2001 only):
      http://standards.nortelnetworks.com/archives/megaco.html

The Megaco media gateway control protocol, RFC 3015 (also published as
ITU-T Recommendation H.248), was developed by the Megaco Working Group
in close cooperation with ITU-T Study Group 16. The protocol responds
to the requirements documented in RFC 2805.

The Megaco Working Group has identified a large number of corrections
to the protocol specification in the year and a half since RFC
3015/Rec.
H.248 was approved. As guardians of the protocol specification, Study
Group 16 maintains a record of these corrections in the form of an
"Implementor's Guide". Study Group 16 now proposes to issue a new
version of Recommendation H.248 incorporating these corrections and a
limited number of new protocol features. The current charter includes
one package, on naming patterns. If the WG determines that other
packages are of general usefulness, an AD and IESG review is needed to
permit addition of the package to the charter.

The basic mandate of the Megaco Working Group is to cooperate with the
ITU-T in the continuing refinement and evolution of the Megaco/H.248
protocol. This specifically includes participation in the development
of H.248v2 and subsequent versions, creation of packages of general
usefulness to users of the protocol, and creation of documents
providing additional information to the development community on
specific aspects of the protocol.

The work of package development for specific applications is
specifically excluded from the Working Group's mandate. However, the
Megaco list will continue to be a place where such packages can be
discussed and refined before being submitted to the IESG for potential
publication as individually-submitted RFCs.

Goals and Milestones:

Done    Submit Initial draft of architecture and requirements document
Done    Initial draft of protocol between MC and MG
Done    Updated draft of protocol between MC and MG
Done    Initial draft of MG and MC MIBs
Done    Submit architecture and requirements document to IESG
Done    Submit protocol(s) between MC and MG to IESG for publication as RFCs
Done    Submit protocol to ITU-T SG 16 for decision as Recommendation H.248
Feb 2002    Submit RFC MIBs for MC and MG to IESG for publication as RFCs
Feb 2002    Submit standards Track document reproducing the content of H.248v2 to the IESG
Mar 2002    Submit Megaco/H.248 MIB to the IESG
Mar 2002    Submit standards Track document, naming pattern package, to the IESG
May 2002    Submit Informational document, example Megaco/H.248 call flows, to the IESG

No Current Internet-Drafts

Request For Comments:

Media Gateway Control Protocol Architecture and Requirements (RFC 2805) (88190 bytes)
MEGACO Protocol (RFC 2885) (344871 bytes) obsoleted by RFC 3015
Megaco Errata (RFC 2886) (41311 bytes) obsoleted by RFC 3015
Megaco Protocol (With erratta folded in) (RFC 3015) (385432 bytes) obsoletes RFC 2885,RFC 2886/ obsoleted by RFC 3525
Megaco IP Phone Media Gateway Application Profile (RFC 3054) (31971 bytes)
Gateway Control Protocol Version 1 (RFC 3525) (439674 bytes) obsoletes RFC 3015