Megaco reqs draft is 01, not 02...: I-D ACTION:draft-ietf-megaco- reqs-01.txt
ngreene at NORTELNETWORKS.COM
Thu Apr 22 15:52:22 EDT 1999
Since the requirements draft we just issued was the first revision that the
IESG saw, the number of it is -01 instead of -02 as I previously announced.
So, if you are looking for the latest megaco requirements draft, the one to
look for is draft-ietf-megaco-reqs-01.txt, dated April 18/99. (See below).
It is identical to the -02 version at
ftp://standards.nortelnetworks.com/megaco/docs/oslo99 (at some point I will
rename the -02 to -01 on that site...)
Sorry for the mixup.
Nancy M. Greene
Internet & Service Provider Networks, Nortel Networks
T:514-271-7221 (internal:ESN853-1077) E:ngreene at nortelnetworks.com
> From: Internet-Drafts at IETF.ORG[SMTP:Internet-Drafts at IETF.ORG]
> Sent: Wednesday, April 21, 1999 1:10 PM
> To: MEGACO at standards.nortelnetworks.com
> Subject: I-D ACTION:draft-ietf-megaco-reqs-01.txt
> <<Message: Microsoft Exchange Message>>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Media Gateway Control
> Working Group of the IETF.
> Title : Media Gateway Control Protocol Architecture
> and Requirements
> Author(s) : N. Greene, M. Ramalho, B. Rosen
> Filename : draft-ietf-megaco-reqs-01.txt
> Pages : 35
> Date : 20-Apr-99
> This document describes protocol requirements for the Media Gateway
> Control protocol between a Media Gateway Controller and a Media Gateway.
> A URL for this Internet-Draft is:
> Internet-Drafts are also available by anonymous FTP. Login with the
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-megaco-reqs-01.txt".
> A list of Internet-Drafts directories can be found in
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> Internet-Drafts can also be obtained by e-mail.
> Send a message to:
> mailserv at ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-megaco-reqs-01.txt".
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
More information about the sg16-avd