FW: conference call on GW decompostion
I would also like to attend this call. Thanks,
Malcolm
561 989-2312 malcolm@netspeak.com http://www.netspeak.com
---------------------------------------------------------------------------- NetSpeak Privacy and Confidentiality Notice: The information contained in this transmission is intended for the above-named recipient(s) only and contains privileged and confidential information. If the reader of this message is not an intended recipient, you are strictly prohibited from using, copying, distributing, or taking any action in reliance on such information. If you have received this communication in error, please notify us immediately .
-----Original Message----- From: Nancy-M Greene [SMTP:Nancy-M.Greene.ngreene@NT.COM] Sent: Sunday, October 18, 1998 9:36 PM To: ITU-SG16@mailbag.cps.intel.com Subject: Re: conference call on GW decompostion
I would also like to attend this call.
Nancy
Nancy Greene (internally Nancy-M Greene) Internet & Service Provider Networks, Nortel NOTE NEW #'s: T:514-271-7221 (internally ESN853-1077) E:ngreene@nortel.com
-----Original Message----- From: Mark Reid [SMTP:mreid@VIDEOSERVER.COM] Sent: Friday, October 16, 1998 1:53 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject:
Dear Colleagues,
I would like to invite you to participate in an audio call, Tuesday October 20th from 11AM to 1PM EST to discuss our work plan for the study of gateway decomposition as outlined in TD 89 (WP2).
The goals of the audio call will be to identify what work items we
need
to
completed and in what order should we attack them. Once we have an
agreed
to work plan, we can talk about building an architecture document and the specific requirements of each interface.
As a place to start the discussions, I think we need the following (referenced to TD 89):
New Protocols:
Interface A - Device Control Interface
New H.246 Annexes:
- H.323 to Voice/Voiceband Terminals = The breakdown of the media.
How
DTMF is converted to/from UserInputIndication messages, etc. (There is a
draft
of this in the current H.246 Annex B) 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) 3) H.323 to Q.931 (Similar to the section in Annex A for H.320)
Interface B, C, D
For the Proposed Interfaces B, C, and D. Given that the messages
passing
across these interfaces must reflect all of the content of the
signaling
that the respective signaling functions receive from and send to
extern
entities, aren't these protocols modified or extended ISUP for
Interface
D, modified or extended Q.931 for Interface C, and modified or extended
H.225
for Interface B? For C & D, can they be the real protocols if carried
on
a
T1 and some derivation of them if running over TCP/IP?
Please try and get all attendee requests in by Monday the 19th at
12:00
Noon EST so that I can make the proper arrangements. I will send port assignments later that day. Here is a summary of attendees so far:
- G. Thom
- S. Nayak
- R. Badri
- P Kallur
- K. Hedayat
- R Spitzer
- R Chopra
- A Amir
- R Even
- H Liu
- J Yeh
- R Radhika
- B Bell
- T Taylor
- G Freundlich
- M Reid/B Hill/G Kajos
All comments welcome,
Mark Reid 1-781-505-2368 mreid@videoserver.com
Bryan Hill 1-781-505-2159 bhill@videoserver.com
participants (1)
-
Malcolm McDonald