FW: RFC 2805 on MG Control Protocol Requirements

[Tom-PT Taylor]

FYI -- it has finally passed through the RFC Editor's queue.

> -----Original Message-----
> From: RFC Editor [SMTP:rfc-ed at ISI.EDU]
> Sent: Wednesday, April 19, 2000 7:31 PM
> To:   MEGACO at STANDARDS.NORTELNETWORKS.COM
> Subject:      RFC 2805 on MG Control Protocol Requirements
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 2805
>
>         Title:      Media Gateway Control Protocol Architecture and
>                     Requirements
>         Author(s):  N. Greene, M. Ramalho, B. Rosen
>         Status:     Informational
>         Date:       April 2000
>         Mailbox:    ngreene at nortelnetworks.com, mramalho at cisco.com,
>                     brosen at eng.fore.com
>         Pages:      45
>         Characters: 88190
>         Updates/Obsoletes/SeeAlso: None
>
>         I-D Tag:    draft-ietf-megaco-reqs-10.txt
>
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2805.txt
>
>
> This document describes protocol requirements for the Media Gateway
> Control Protocol between a Media Gateway Controller and a Media
> Gateway.
>
> This document is a product of the Media Gateway Control Working Group
> of the IETF.
>
> This memo provides information for the Internet community.  It does
> not specify an Internet standard of any kind.  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 at IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
> help: ways_to_get_rfcs.  For example:
>
>         To: rfc-info at 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 at 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 at 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. <<Untitled Attachment>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20000419/442e35c5/attachment-0003.html>
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: 
Date: Wed, 19 Apr 2000 19:53:50 -0500
Size: 1533
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20000419/442e35c5/attachment-0003.mht>