draft-ietf-megaco-protocol-02.txt   draft-ietf-megaco-protocol-03.txt 
Internet Engineering Task Force Fernando Cuervo Internet Engineering Task Force Fernando Cuervo
INTERNET DRAFT Nortel Networks INTERNET DRAFT Nortel Networks
December 25, 1999 Christian Huitema July 30, 1999 Christian Huitema
Expires October 16, 1999 Telcordia Technologies Expires January 30,2000 Telcordia Technologies
<draft-ietf-megaco-protocol-02.txt> Keith Kelly <draft-ietf-megaco-protocol-03.txt> Keith Kelly
NetSpeak NetSpeak
Brian Rosen Brian Rosen
FORE Systems FORE Systems
Paul Sijben Paul Sijben
Lucent Technologies Lucent Technologies
Eric Zimmerer Eric Zimmerer
Level 3 Communications Level 3 Communications
MEGACO Protocol MEGACO Protocol
skipping to change at page 1, line 32 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress." or to cite them other than as "work in progress."
To view the entire list of current Internet-Drafts, please check the The list of current Internet-Drafts can be accessed at
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe),
ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim),
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
ABSTRACT The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
IMPORTANT NOTE IMPORTANT NOTE
In accordance with agreements reached between IETF and ITU, the text of In accordance with agreements reached between IETF and ITU, the text of
the protocol, IETF version 02, is found at: the protocol, IETF version 03, is found at:
ftp://standards.nortelnetworks.com/megaco/docs/Oslo99/megacoHGCP5.pdf ftp://standards.nortelnetworks.com/megaco/docs/Oslo99/megacoHGCP9.pdf
The source for this document may be found at:
Internet draft MEGACO Protocol June 25, 1999 Internet draft MEGACO Protocol July 30, 1999
ftp://standards.nortelnetworks.com/megaco/docs/Oslo99/megacoHGCP5.pdf Abstract
MEGACO/Recommendation H.GCP defines the protocols used between elements MEGACO/Recommendation H.248 defines the protocols used between elements
of a physically decomposed multimedia gateway. There are no functional of a physically decomposed multimedia gateway. There are no functional
differences from a system view between a decomposed gateway, with dis- differences from a system view between a decomposed gateway, with dis-
tributed sub-components potentially on more than one physical devices, tributed sub-components potentially on more than one physical devices,
and a monolithic gateway. and a monolithic gateway.
This RFC/recommendation does not define how gateways, multipoint control This document does not define how gateways, multipoint control units or
units or integrated voice response units (IVRs) work. Instead it integrated voice response units (IVRs) work. Instead it creates a gen-
creates a general framework that is suitable for these applications. eral framework that is suitable for these applications.
Packet network interfaces may include IP, ATM or possibly others. The Packet network interfaces may include IP, ATM or possibly others. The
interfaces will support a variety of SCN signalling systems, including interfaces will support a variety of SCN signalling systems, including
tone signalling, ISDN, ISUP, QSIG, and GSM. National variants of these tone signalling, ISDN, ISUP, QSIG, and GSM. National variants of these
signaling systems will be supported where applicable. signaling systems will be supported where applicable.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/