H.323 Mobility: docs

[Edgar Martinez [1]]

I've done my homework and filled in the references for the Megaco/H.248
requirements document (draft-ietf-megaco-reqs-09.txt) (thanks to those who
helped me fill them in):

> draft-ietf-megaco-reqs-09.txt references:
> 13.  References
> 
> [1]  S. Bradner, "Key words for use in RFCs to Indicate Requirement Lev-
>      els", RFC 2119, March 1997.
> [2]  Draft ITU-T Recommendation Q.2630.1, AAL type 2 Signalling Protocol
> (Capability Set 1), ITU-T Meeting Report COM 11-R 149-E, July 1999
> [3]  ITU-T Recommendation H.341, Line Transmission of Non-Telephone
> Signals, May 1999.
> [4]  ATM Forum Technical Committee, af-vtoa-0083.001, Voice and Telephony
> Over ATM to the Desktop Specification, March 1999.
> [5]  ITU-T Recommendatio H.323v2, Packet-based Multimedia Comunications
> Systems (includes Annex C - H.323 on ATM), February 1998. 
> [6]  ATM Forum Technical Committee,  af-saa-0124.000, Gateway for H.323
> Media Transport Over ATM, May 1999.
> [7]  ITU-T Recommendation T.140, Protocol for Multimedia Application Text
> Conversation, February 1998.
> [8]  ITU-T Recommendation V.18, Operational and Interworking Requirements
> for DCEs Operating in Text Telephone Mode, February 1998.
> [9]  ITU-T Q.931, Digital Subscriber Signalling System No. 1 (DSS 1) -
> ISDN User-Network Interface Layer 3 Specification fro Basic Call Control,
> March 1993
> 
> Nancy
> --------------------------------------------------------------------------
> Nancy M. Greene 
> Internet & Service Provider Networks, Nortel Networks
> T:514-271-7221 (internal:ESN853-1077) E:ngreene at nortelnetworks.com
> 
> 
> ----------
> From:         Taylor, Tom-PT [CAR:B904-I:EXCH]
> Sent:         Friday, December 10, 1999 9:41 AM
> To:   ITU-SG16 at MAILBAG.INTEL.COM
> Subject:      Re: I-D ACTION:draft-ietf-megaco-reqs-09.txt
> 
> I propose WG Last Call based on this document, with the expiry two weeks
> hence (24 December). 
> 
> Changes from the previous version are as follows: 
> 
> - removed reqt 5.6 c) Support general test capabilities, for example
> loopbacks through the MG to test DSP operation. 
> It was agreed that inward loopbacks are outside the scope of the protocol
> - they are not part of call control, so would be handled by some other
> maintenance protocol. Thus the above requirement is deleted.
> 
> - reqt 5.7 a) - changed word call to connection 
> 
> - table in section 11 - removed  wiretap 
> 
> - reqt 11.1.3.1 a) rewording of 2nd bullet  on addressing - didn't mean
> wildcarding, meant instead allowing the gateway to choose (part of) the
> identifier
> 
> 
> The references need to be completed still, and there may be an editor's
> note or two that should still come out. 
> 
>       -----Original Message----- 
> From:   Internet-Drafts at IETF.ORG [SMTP:Internet-Drafts at IETF.ORG] 
> Sent:   Friday, December 10, 1999 8:08 AM 
> To:     MEGACO at STANDARDS.NORTELNETWORKS.COM 
> Subject:        I-D ACTION:draft-ietf-megaco-reqs-09.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-09.txt 
>         Pages           : 45 
>         Date            : 09-Dec-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-09.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-09.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-09.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. << Message:  >> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/19991215/0d1819c3/attachment-0001.htm>