RFC 2885 on Megaco Protocol

RFC Editor <rfc-ed@ISI.EDU> Thu, 31 August 2000 00:12 UTC

Message-Id: <200008302359.QAA26933@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2885 on Megaco Protocol
Cc: rfc-ed@ISI.EDU, megaco@standards.nortelnetworks.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 30 Aug 2000 16:59:06 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2885

        Title:	    Megaco Protocol 0.8
        Author(s):  F. Cuervo, N. Greene, C. Huitema, A. Rayhan,
                    B. Rosen, J. Segers
        Status:     Standards Track
	Date:       August 2000
        Mailbox:    fcuervo@nortelnetworks.com,
                    ngreene@nortelnetworks.com, huitema@microsoft.com,
                    arayhan@nortelnetworks.com,
                    brian.rosen@marconi.com, 
                    jsegers@lucent.com 
        Pages:      169
        Characters: 344871
        Obsoletes/Updates/SeeAlso:  None

        I-D Tag:    draft-ietf-megaco-protocol-08.txt

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


This document is common text with Recommendation H.248 as
redetermined in Geneva, February 2000.  It must be read in
conjunction with the Megaco Errata, RFC 2886.
A merged document presenting the Megaco protocol with the Errata
incorporated will be available shortly.
 
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/rfc2885.txt"><ftp://ftp.isi.edu/in-notes/rfc2885.txt>

RFC 2885 on Megaco Protocol RFC Editor