NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 23-Oct-00
Chair(s):
Tom Taylor <taylor@nortelnetworks.com>
Transport Area Director(s):
Scott Bradner <sob@harvard.edu>
Allison Mankin <mankin@east.isi.edu>
Transport Area Advisor:
Scott Bradner <sob@harvard.edu>
Mailing Lists:
General Discussion:megaco@standards.nortelnetworks.com
To Subscribe: listserv@standards.nortelnetworks.com
In Body: subscribe megaco first_name last_name
Archive: http://standards.nortelnetworks.com/archives/megaco.html
Description of Working Group:
The working group will develop an informational RFC detailing the architecture and requirements for controlling Media Gateways from external control elements such as a Media Gateway Controller. A media gateway is a network element that provides conversion between the information carried on telephone circuits and data packets carried over the Internet or over other IP networks. This work will be done in consultation with other IETF working groups looking at similar issues.
The working group will also ensure that good information conduits exist with groups in other standards groups with expertise in the relevant PSTN technology. Other IETF working groups include PINT, IPTEL and SIGTRAN. In addition the working group will ensure that reasonable liaisons exist with similar activities in other standards bodies such as the ITU-T and ETSI.
This working group will also define standards track protocol(s) for controlling media gateways from external control elements such as a media gateway controller.
Examples of media gateways are:
* Trunking gateways that interface between the telephone network and a Voice over IP network. Such gateways typically manage a large number of digital virtual circuits. * Access gateways that provide traditional analog or Primary Rate (PRI) line interfaces to a Voice over IP network. * Network Access Servers that can attach a "modem" to a telephone circuit and provide data access to the Internet.
This working group assumes a separation of call control so the call control "intelligence" is outside the media gateways and handled by a media gateway controller. This group will NOT work on media gateway controller to media gateway controller protocols, nor on media gateway to media gateway protocols.
The working group will ensure that the security issues relating to the use of the standards track protocol in hostile environments are fully understood and that the protocol will will include security mechanisms to protect against attacks on the protocol and to ensure confidentiality where needed.
Planned output:
* Architecture & Requirements informational RFC
* Standards Track RFC for the protocol between a media gateway controller and a media gateway.
* Standards Track RFC for the MG and MC MIBs
* Informational RFC for application programming interface for the MC to MG protocol
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 |
Mar 00 |
|
Submit RFC MIBs for MC and MG to IESG for publication as RFCs |
Apr 00 |
|
Close Working Group |
Internet-Drafts:
· Megaco IP Phone Media Gateway Application Profile
· H.248 Annex G (Pre-Decision White Document)
· H.248 Annex H (Pre-Decision White Document)
· H.248 Annex I (Pre-Decision White Document)
· H.248 Annex J (Pre-Decision White Document)
Request For Comments:
RFC |
Status |
Title |
RFC2805 |
Media Gateway Control Protocol Architecture and Requirements | |
RFC3015 |
PS |
Megaco Protocol (With erratta folded in) |
None received.
None received.