RFC 3015 on Megaco Protocol Version 1.0

RFC Editor <rfc-ed@ISI.EDU> Sat, 02 December 2000 01:54 UTC

Message-Id: <200012020123.RAA04676@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3015 on Megaco Protocol Version 1.0
Cc: rfc-ed@ISI.EDU, megaco@standards.nortelnetworks.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 01 Dec 2000 17:23:12 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 3015

        Title:	    Megaco Protocol 1.0
        Author(s):  F. Cuervo, N. Greene, A. Rayhan, C. Huitema,
                    B. Rosen, J. Segers
        Status:     Standards Track
	Date:       November 2000
        Mailbox:    cuervo@nortelnetworks.com,
                    ngreene@nortelnetworks.com,
                    arayhan@nortelnetworks.com, huitema@microsoft.com,
                    brian.rosen@marconi.com, jsegers@lucent.com  
        Pages:      178
        Characters: 385432
        Obsoletes:  2885, 2886

        I-D Tag:    draft-ietf-megaco-merged-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc3015.txt


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 document is common text with
ITU-T Recommendation H.248 and is a result of applying the changes
yin RFC 2886 to the text of RFC 2885.
 
The protocol presented in this document meets the requirements
for a media gateway control protocol as presented in RFC 2805.

This document is a product of the Media Gateway Control Working Group
of the IETF.  

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3015.txt"><ftp://ftp.isi.edu/in-notes/rfc3015.txt>

RFC 3015 on Megaco Protocol Version 1.0 RFC Editor