Media Gateway Control (megaco)

This Working Group did not meet

NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 02/18/2002

Chair(s):
Tom Taylor <taylor@nortelnetworks.com>
Transport Area Director(s):
Scott Bradner <sob@harvard.edu>
A. Mankin <mankin@isi.edu>
Transport Area Advisor:
Scott Bradner <sob@harvard.edu>
Mailing Lists:
General Discussion: megaco@ietf.org
To Subscribe: megaco-request@ietf.org
In Body: subscribe megaco
Archive: ftp://ftp.ietf.org/ietf-mail-archive/megaco/
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 02  Submit RFC MIBs for MC and MG to IESG for publication as RFCs
FEB 02  Submit standards Track document reproducing the content of H.248v2 to the IESG
MAR 02  Submit Megaco/H.248 MIB to the IESG
MAR 02  Submit standards Track document, naming pattern package, to the IESG
MAY 02  Submit Informational document, example Megaco/H.248 call flows, to the IESG
Internet-Drafts:
  • - draft-ietf-megaco-mib-03.txt
  • - draft-ietf-megaco-naspkg-04.txt
  • - draft-ietf-megaco-3015corr-01.txt
  • - draft-ietf-megaco-h248v2-01.txt
  • - draft-ietf-megaco-callflows-00.txt
  • Request For Comments:
    RFCStatusTitle
    RFC2805 I Media Gateway Control Protocol Architecture and Requirements
    RFC2886 PS Megaco Errata
    RFC2885 PS MEGACO Protocol
    RFC3015 PS Megaco Protocol (With erratta folded in)
    RFC3054 I Megaco IP Phone Media Gateway Application Profile

    Current Meeting Report

    None received.

    Slides

    None received.