- sg16-avd - lists.packetizer.com

Re: Liaison from ITU Question 21/15
by Callaghan, Robert 02 Mar '99

02 Mar '99

This is an interesting view of the IP world SG 16 - speech coding and interworking protocols SG 13 - lead group on overall IP issues SG 11 - signaling issues SG 4 - administration IETF - sigtran, megaco and iptel Working Groups I don't think that this is our view, is it? Bob <<q21_text.html>> ------------------------------------------------------------------ Robert Callaghan Siemens Information & Communication Networks Tel: +1.561.997.3756 Fax: +1.561.997.3403 Email: … [View More]

1 0

Re: H.GCP Audio Call
by Ami Amir 02 Mar '99

02 Mar '99

Bryan, Please count me in. I'll join at 12AM. Ami -----Original Message----- From: Rex Coldren [SMTP:coldrenr@AGCS.COM] Sent: Monday, March 01, 1999 9:49 PM To: ITU-SG16(a)mailbag.cps.intel.com Subject: Re: H.GCP Audio Call Bryan, Good e-mail. Count me in on the call, of course. I will keep your mail around and refer to it in my response to Nortel's proposal. Thanks, Rex Bryan Hill … [View More]wrote: > > Colleagues, > > I would like to invite you to participate in audio call on Thursday March > 4th from 11AM until 1PM EST to discuss H.GCP. The call details are as > follows: > > Calls from outside the US: 312-470-7273 > Calls from within the US: 888-847-7598 > Passcode: BryanHill > Confirmation number: 5193957 > > Please respond to me directly to reserve a port for this call (where ever > possible please try to minimize port requirements by sharing a port with a > colleague). > > The main purpose of this initial call will be to review requirements and > terminology for H.GCP which were discussed in Monterey. I have been editing > these sections and will make them available on the ptel SG16 ftp site no > later than tomorrow 3/2. The second purpose of the call is to identify > other areas that need to be discussed in subsequent audio calls. An initial > pass of topics is listed below. I would like to solicit volunteers to > submit written contribution in each of the areas identified and use these > submissions as a basis for discussing topics in future audio calls. In this > manner I hope to scope our discussion to specific technical topics and > combine the benefits from MDCP and MGCP approaches into H.GCP. > > 1) Control model > a) Controller to gateway associations > b) Controller to internal gateway entity associations > c) Failover > d) Security > 2) Connection model > a) Controllable entities > b) Controllable entity properties > 3) Commands > a) Types > b) Parameters > c) Acknowledgement styles/sequencing > 4) Messages (i.e.-command packaging) > 5) Message Encoding > 6) Resource management > 7) Scripting/Packages > 8) Interface C protocol (Q.931/Q.764) > 9) Interface B protocol (Q.931 ) > > Best Regards, > Bryan > _________________________________________________________ > Bryan Hill > VideoServer Inc. > (781) 505-2159 > <mailto:bhill@videoserver.com> [View Less]

1 0

H.GCP Audio Call
by Bryan Hill 01 Mar '99

01 Mar '99

Colleagues, I would like to invite you to participate in audio call on Thursday March 4th from 11AM until 1PM EST to discuss H.GCP. The call details are as follows: Calls from outside the US: 312-470-7273 Calls from within the US: 888-847-7598 Passcode: BryanHill Confirmation number: 5193957 Please respond to me directly to reserve a port for this call (where ever possible please try to minimize port requirements by sharing a port with a colleague). The main purpose of this initial call … [View More]

6 5

Monterey meeting participants
by Sakae OKUBO 01 Mar '99

01 Mar '99

Dear Q.11-15/16 Monterey meeting participants, For inclusion in the Q.12-14 meeting report (APC-1554), I have edited a list of participants based on Georgia's list. Please take a look at ftp://standard.pictel.com/avc-site/Incoming/Participants.doc or http://standard.pictel.com/ftp/avc-site/Incoming/Participants.doc and advise me if you are not correctly represented. Particularly I am not sure which is the family name for some participants, and which country should be indicated for … [View More]

1 0

Use of ftp site
by Sakae OKUBO 01 Mar '99

01 Mar '99

Dear Mr. Hill, Dear H.GCP collaborators, When you place (or have placed) a document at the /Incoming of PictureTel ftp site, please advise me in any form; directly or indirectly through a message to the mailing list. This is to ensure that all the files in /Incoming are relevant to our ITU-T work. If you expect many working documents for the H.GCP editing, I can make a temporary folder for this purpose (to be deleted after the Santiago meeting). Please advise me if it helps you. The service I … [View More]

1 0

Liaison from ITU Question 21/15
by Glen Freundlich 01 Mar '99

01 Mar '99

Attached is a liaison statement from Question 21/15, of which Jerry Skene is the rapporteur, sent in response to a liaison from Q14 regarding the text of Q21/15. Mr. Skene's contact information is: Jerry Skene | Tellabs, Inc. Director, | 45085 University Drive International Standards | Ashburn, VA 20147.2745 tel: +1 703 724-7302 | URL: www.tellabs.com fax: +1 703 724-7202 | email:jerry.skene@tellabs.com -- Glen Freundlich ggf(a)… [View More]

1 0

Change of address
by Jim Toga 28 Feb '99

28 Feb '99

After today I am joining an IP telephony startup. For any directed email to me, please use the following address - the Intel address will be deactivated. jim.toga(a)metatel.com (my response time might be a little 'spotty' over the next couple of weeks) Best Regards, jimt. +1-503-264-8816(voice) Intel - Hillsboro, OR mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41

1 0

Re: Development of Decomposed Gateway Architecture
by Tom-PT Taylor 27 Feb '99

27 Feb '99

Most of the work items are grundge work to start with. I'm willing to tackle them until I start to run into issues that need others' comment. How would you like to start on the H.245 abstraction (interface ?:e)? > -----Original Message----- > From: Rex Coldren [SMTP:coldrenr@AGCS.COM] > Sent: Friday, February 26, 1999 7:36 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: Development of Decomposed Gateway Architecture > > Tom, > Sorry to respond so late … [View More]to this. In the interest of keeping my > mailbox close > to manageable I deal with the quickies first. Has anyone responded to > this or > are you taking these work items on yourself? I am wondering whether there > is > something here that you want me to tackle. > > Rex > > Tom-PT Taylor wrote: > > > This note is to point out the follow-up work required in the light of > the > > Monterey meeting's adoption of the revised Gateway functional > architecture > > as shown in TD-34 (Monterey). I am prepared to contribute to that work. > > People may wish to comment on the priorities of definition of the > different > > interfaces. > > > > First point: I followed up Bob Callaghan's pointers to the layer 4 > > interfaces applicable to our J:c interface (per the TD-34 definition). > The > > relevant references are the SDL charts shown in Annex A of Q.931 and > Annex H > > of Q.764 respectively. These show the messages exchanged over the J:c > > interface for their respective protocols, but do not show their content. > So > > that's one work item. > > > > Second point: Annex A of Q.931 shows messages going between a Q.931 > Protocol > > Control block and two higher blocks: Call Control and Resource Control > > respectively. Annex H of Q.764 is more complicated: it shows Call > Control > > above the ISUP User Part, but three blocks within it: Signalling > Procedure > > Control, Call Processing Control, and Circuit Supervision Control. I > think > > we should have a Call Control block in our picture, at the same level as > our > > High-Layer Resource Control. I also think the ISUP Circuit Supervision > > Control should report into High-Layer Resource Control rather than Call > > Control. > > > > Third point: the messaging on our ?:b interface can probably be derived > from > > the Q.931 SDL. The content also has to be worked out. Another couple > of > > work items. > > > > Final point: how to determine the content of the ?:e (abstracted H.245) > > interface and where it should flow? Definitely some detailed work items > > here. > > > > Tom Taylor > > E-mail: taylor(a)nortelnetworks.com (internally Tom-PT Taylor) > > Tel.: +1 613 765 4167 (internally 395-4167) > > FAX: +1 613 763 7236 (internally 393-7236) [View Less]

1 0

Development of Decomposed Gateway Architecture
by Tom-PT Taylor 26 Feb '99

26 Feb '99

This note is to point out the follow-up work required in the light of the Monterey meeting's adoption of the revised Gateway functional architecture as shown in TD-34 (Monterey). I am prepared to contribute to that work. People may wish to comment on the priorities of definition of the different interfaces. First point: I followed up Bob Callaghan's pointers to the layer 4 interfaces applicable to our J:c interface (per the TD-34 definition). The relevant references are the SDL charts shown … [View More]

2 1

Monterey meeting report APC-1554
by Sakae OKUBO 24 Feb '99

24 Feb '99

Dear participants of the Q12-14/16 Monterey meeting, I have uploaded Version of the subject document as follows: ftp://standard.pictel.com/avc-site/9902_Mon/APC-1554.zip or http://standard.pictel.com/ftp/avc-site/9902_Mon/APC-1554.zip The current version has been made by integrating TD-30, 31, 32, 37 and other TDs. Please note the following: - Obvious editorial corrections have been made. - Section 4.4 (future plan of Q12) has been added. - List of participants is yet to be edited. - … [View More]

1 0