FW: I-D ACTION:draft-ietf-megaco-reqs-08.txt

Nancy-M Greene ngreene at NORTELNETWORKS.COM
Tue Oct 26 12:52:26 EDT 1999


Below is the URL for the latest Megaco/H.248 requirements draft. The changes
between it and reqs-07 (APC-1695) were listed in TD-22 from the Red Bank
meeting.

Nancy
--------------------------------------------------------------------------
Nancy M. Greene
Internet & Service Provider Networks, Nortel Networks
T:514-271-7221 (internal:ESN853-1077) E:ngreene at nortelnetworks.com

> ----------
> From:         Greene, Nancy-M [CAR:5N10:EXCH]
> Sent:         Tuesday, October 26, 1999 12:50 PM
> To:   'megaco at standards.nortelnetworks.com'
> Subject:      RE: I-D ACTION:draft-ietf-megaco-reqs-08.txt
>
> Please find the latest requirements draft  (-08) at:
>
> ftp://standards.nortelnetworks.com/megaco/docs/latest/
>
>
> (be sure to refresh your browser to see it)
>
> It is also available from the public Internet-drafts directory (see
> below).
>
> The main differences between reqs-08 and reqs-07 are:
> - in 11.2.3, requirements added for trunking/access gateway with fax ports
> (based on request from ITU-T SG8):
>
> 11.2.3 Trunking/Access Gateway with fax ports
> a.    A trunking/access gateway with fax ports has these requirements:the
> protocol must be able to indicate detection of fax media
> b.    the protocol must be able to specify T.38 for the transport of the
> fax.
> c.    the protocol must be able to specify G.711 encoding for transport of
> fax tones across a packet network.
>
> - in 11.2.9, the word Audio Server was removed, and replaced by the more
> general term
> Audio Enabled Gateway
> - in 11.2.9, digit collection was qualified to be DTMF digit collection
> - In Section 11.2.9.1, parts d and e on sequences and sets reworked to
> eliminate the implementation specific language
> - In Section 11.2.9.1 parts f, g, h removed
> - reordering of sections, putting Audio Conferencing at the end
> - requirements added to sections 11.2.9.5 and 11.2.9.6
>
> Section 11.2.9 is identical to the text I sent out in an email last week.
> I received no further comments on it.
>
> Nancy
> --------------------------------------------------------------------------
> 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:         Monday, October 25, 1999 7:01 AM
> To:   megaco at standards.nortelnetworks.com
> Subject:      I-D ACTION:draft-ietf-megaco-reqs-08.txt
>
>
> 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-08.txt
>         Pages           : 45
>         Date            : 22-Oct-99
>
> TThis 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:
> http://www.ietf.org/internet-drafts/draft-ietf-megaco-reqs-08.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-ietf-megaco-reqs-08.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> 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-08.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
> readers
>         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
> Internet-Draft.
>
>



More information about the sg16-avd mailing list