March 1999 - sg16-avd - lists.packetizer.com

Re: H.GCP Audio Call
by Bryan Hill 04 Mar '99

04 Mar '99

The H.GCP audio call was held today, 18 ports called in including a group from the TIPHON meeting. The working model =============== Individuals have will be working up submissions to be review by the entire group at the next audio call. The objective is that the principals involved will collaborate off line initially, post the results to the SG16 reflector for comments and a final version will be posted for discussion in an audio call. The result of that final review will be added into the H.GCP by the editor. Every effort will be made to resolve issues but if they cannot they must be presented in Santiago. Work items =============== The following work items were identified and individuals who expressed an interest in working on them are noted. -----Original Message----- From: Bryan Hill [SMTP:bhill@VIDEOSERVER.COM] Sent: Monday, March 01, 1999 2:37 PM To: ITU-SG16(a)mailbag.cps.intel.com Subject: H.GCP Audio Call 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>

1 0

Re: H.323/VoIP QoS (further to Randy Bloomfield's note)
by Demosthenes Kostas 04 Mar '99

04 Mar '99

Could you translate it for some of us that don't read French Kannst du nicht allen gefallen durch deine That und dein Kunstwerk -- mach es wenigen recht, vielen gefallen ist schlimm" -- Schiller --------------------------------------------- Demosthenes Kostas PhD/MBA Manager-Industry Standards GTE 700 Hidden Ridge, HQW02J85 Irving, TX 75038 (972) 718-6291 FAX: (972) 718-4393 Internet: demos.kostas(a)telops.gte.com ------------- Original Text From: "Christian Kuhtz" <ck(a)ns1.adsu.bellsouth.com>, on 3/3/99 4:14 PM: Eric, I think the purpose of this group is to discuss and explore ways of providing IP QoS for VoIP networks, and to evaluate applicable existing technology as well as provide feedback for emerging technology. I don't quite understand why we need a managed membership committee to run this -- particularly the managed membership part is what I find troubling. What benefit are you providing? Personally, I find this difficult to define, because you are obviously not the premier forum for IP related issues (the IETF is). Please explain. So, if you're affiliated with the IETF, why don't you participate in our working group rather than we move our IP network related issues into T1? And, was it really neccessary to carbon copy over half a dozen mailing lists on this subject matter? Thanks in advance. Cheers, Chris -- "Kannst du nicht allen gefallen durch deine That und dein Kunstwerk -- mach es wenigen recht, vielen gefallen ist schlimm" -- Schiller [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] *

1 0

FW: H.323/VoIP QoS
by Malcolm McDonald 04 Mar '99

04 Mar '99

Joon, Please include me in the QoS discussions. Thanks, Malcolm 561 989-2312 malcolm(a)netspeak.com http://www.netspeak.com

1 0

Re: H.323/VoIP QoS
by Ying, Wen-Ping 04 Mar '99

04 Mar '99

Joon, I am a bit confused by the charter of this proposed group, but in general, I am very interested in having a place to discuss generic QoS issues related to voice over a packet data network. Are you planning to include the following topics in your proposed group discussion? 1. VoIP flow reserving resource (flow based RSVP interacting with QoS aware switch/router , SLA based diffserv, SLA based MPLS) - will this group be recommending the model, or will it discuss the pros/cons or interoperability? 2. switch/router resource mgmt (MPLS, Constrained-Based MPLS, diffserv, etc.) - ditto 3. Control of the resource allocation (GK/GW/H.323 endpoints) - problems such as GK granting the bandwidth without having the real control on actual usage (bandwidth mgmt with collaboration from many components.) 4. speech coding/quality - encourage single LBRV to reduce transcoding. 5. absolute delay control. 6. echo cancellation problem with the existence of large jitter. 7. transport efficiency - concerns about header overhead that triggers the proposed solution hop2hop header compression (rfc-2508) and the recent work in MEGACO regarding g.729/udp/rtp/ip/atm & g.729/aal2/atm interworking. Regards, Wen-Ping Ying AT&T Wireless Services PO Box 97059 Redmond, WA 98073 Voice 425-702-2725 Fax 425-702-2568 wying(a)att.com wen-ping.ying(a)attws.com > -----Original Message----- > From: Joon Maeng [SMTP:Joon_Maeng@VTEL.COM] > Sent: Wednesday, March 03, 1999 8:40 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.323/VoIP QoS > > Greetings! My name is Joon Maeng. I work for VTEL Corp in USA. I've > talked to > several companies while I was attending ITU and IETF meetings about > establishing > an ad-hoc group to address QoS (Quality of Service) issues in TRANSPORTING > REAL-TIME TRAFFICS in the packet switched network, especially in the IP > network. > I was very encouraged by responses from those companies. Most of them > agreed > that lack of QoS support for real-time traffics was one of major barriers > in > deploying H.323/VoIP products and the H.323 industry would benefit by > having a > QoS activity group. I would like to ask if your company would be > interested in > the activities described in the following: > > Proposed name of the group: H.323/VoIP QoS Activity Group. > > Motivation: ITU defined a good conference standard, H.323, for the packet > network. IETF is actively defining QoS standards for the IP network. The > deployment of H.323/VoIP products has been slow partially due to lack of > QoS > supports in current IP network. The H.323/VoIP industry shall work > together to > access the issues and provide solutions for the users. > > Proposed charter of the group: > - Assess QoS issues in transporting real-time traffics (calls with > long-duration > compared to web-access) in the IP network, > - Find the solutions to resolve issues, > - Execute solutions via various processes such as building consensus on > various > QoS solutions among participants, > submitting recommendations to standardization bodies if needed, and > facilitating inter-operablity testing between QoS standards and > application > standards, > - and education, promotion, etc. > > I would expect the final charter and the structure of the group will be > determined by the participants and their interests. I would say that > everything is open at this time except that the industry shall look at the > QoS > issues seriously for real-time traffics. I'd like to clarify that the > proposed > group is not a group to standardize the QoS. It is a group or a forum > that is > interested in helping and promoting the real-time QoS for H.323/VoIP > industry > through various methods (to be determined). I plan to set up an email > reflector for the initial discussions among participants and decide the > following steps based on the discussions. Please email me (joon_maeng@ > vtel.com) > if you and your company would be interested in joining the initial talks > via > email reflector. Your comments and suggestions will be greatly > appreciated. > Regards, > Joon

1 0

Re: H.323/VoIP QoS (further to Randy Bloomfield's note)
by Tony.Pillai＠TELLABS.COM 04 Mar '99

04 Mar '99

Please do not include me in your future e-mails. -----Original Message----- From: ehauch Sent: Wednesday, March 03, 1999 3:50 PM To: Joon.Maeng Cc: ehauch; diff-serv-interest; h323implementors; interwkg; voip; int-serv; neal; ITU-SG16; t1a12; t1a15; mpls Subject: Re: H.323/VoIP QoS (further to Randy Bloomfield's note) Joon, My name is Eric Hauch. I am the current Ad Hoc Group leader for a Working Group T1A1.5 activity that appears to closely parallel your initiative. Committee T1 (of which TSC T1A1 is part) is an open standards forum sponsored by the Alliance for Telecommunications Industry Solutions (ATIS) and accredited by the American National Standards Institute (ANSI). As such, Committee T1 is the ANSI authority in the United States for defining telecommunications interface and performance standards. Committee T1 TSC's are also a key source of research and advice to the US State Department's delegations to the ITU - and have formal liaisons with the IETF. The current Ad Hoc Group work on defining multimedia performance requirements for business quality conferences carried over IP based networks is part of addressing these standards setting responsibilities. We very much share the reasons you state for needing these QoS standards soon. The work of the MMoIP Ad Hoc Group is about 60% complete (i.e. we're just over half way to making a recommendation to send our draft standard to T1 letter ballot). The last Ad Hoc group conference call was Feb 25, 99 - the next, Apr 1, 99. Attendance and participation in any T1 activity is completely open. Voting at the TSC and T1 levels is by membership (for example, VTel is a member of T1A1). You can find out more about TSC T1A1, WG T1A1.5 and the Ad Hoc Group activities (through the posted documentation) at www.t1.org. As past chair of WG T1A1.5, I have enjoyed VTel's excellent past contributions to our efforts and have been very supportive and encouraging of VTel's particpation in this particular Ad Hoc group. To the extent your initiative indicates a renewed interest on your part and others in your industry segment, I am delighted - and encourage and welcome all of you to work with us. I'll look forward to hearing from you, Eric G. Hauch Vice-Chair T1A1 615-532-2365 ehauch(a)mail.state.tn.us >>> "Joon Maeng" <Joon_Maeng(a)vtel.com> 03/03 10:40 AM >>> Greetings! My name is Joon Maeng. I work for VTEL Corp in USA. I've talked to several companies while I was attending ITU and IETF meetings about establishing an ad-hoc group to address QoS (Quality of Service) issues in TRANSPORTING REAL-TIME TRAFFICS in the packet switched network, especially in the IP network. I was very encouraged by responses from those companies. Most of them agreed that lack of QoS support for real-time traffics was one of major barriers in deploying H.323/VoIP products and the H.323 industry would benefit by having a QoS activity group. I would like to ask if your company would be interested in the activities described in the following: Proposed name of the group: H.323/VoIP QoS Activity Group. Motivation: ITU defined a good conference standard, H.323, for the packet network. IETF is actively defining QoS standards for the IP network. The deployment of H.323/VoIP products has been slow partially due to lack of QoS supports in current IP network. The H.323/VoIP industry shall work together to access the issues and provide solutions for the users. Proposed charter of the group: - Assess QoS issues in transporting real-time traffics (calls with long-duration compared to web-access) in the IP network, - Find the solutions to resolve issues, - Execute solutions via various processes such as building consensus on various QoS solutions among participants, submitting recommendations to standardization bodies if needed, and facilitating inter-operablity testing between QoS standards and application standards, - and education, promotion, etc. I would expect the final charter and the structure of the group will be determined by the participants and their interests. I would say that everything is open at this time except that the industry shall look at the QoS issues seriously for real-time traffics. I'd like to clarify that the proposed group is not a group to standardize the QoS. It is a group or a forum that is interested in helping and promoting the real-time QoS for H.323/VoIP industry through various methods (to be determined). I plan to set up an email reflector for the initial discussions among participants and decide the following steps based on the discussions. Please email me (joon_maeng@ vtel.com) if you and your company would be interested in joining the initial talks via email reflector. Your comments and suggestions will be greatly appreciated. Regards, Joon << File: Re_ H.TXT >>

1 0

Re: question: asn.1
by Derks, Frank 04 Mar '99

04 Mar '99

Hi Jihye, try: http://www-sop.inria.fr/rodeo/personnel/hoschka/asn1.html to get an overview of ASN.1 products. The OSS ( http://www.oss.com) ASN.1 compiler, which is commercial, support the packed encoding rules, which are required for H.323. Frank -----Original Message----- From: pjh [mailto:pjh@DESKVIEW.NADA.CO.KR] Sent: 04 March 1999 10:55 To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: question: asn.1 Dear ITU-SG16 experts I am searching for commercial or free ASN.1 compiler . Further details are as follows: Features: o ASN.1 to C or C++ source code compiler ( A run-time version of the source code is available) o Fully supports ASN.1:1997 o Library of low-level PER encode/decode functions o Compiler has been tested on following RealTime OS: pSOS, vxWorks, Ets kernel If you are using ASN.1 compiler on RealTime OS, Please let me know where I get it. Please reply to this E-Mail Sincerely, Jihye Park(Miss) Nada Research Co., Ltd. Seoul 137-070 , Korea Tel: 82-2-525-3941 Fax: 82-2-525-3945 pjh(a)deskview.nada.co.kr < mailto:pjh@deskview.nada.co.kr>

2 1

who
by Keith Kelly 04 Mar '99

04 Mar '99

who Keith C. Kelly VP Emerging Technologies and Standards ___________________ keith(a)netspeak.com NetSpeak Corporation 902 Clint Moore Rd. Suite 104 Boca Raton, FL 33487 Direct:(561) 998-8752 Pager (800) 946-4645 #1441506 Main: (561) 998-8700 Fax (561) 997-2401 http://www.netspeak.com The Art of Sound Communication ==================================================================== 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.

1 0

Subscribe
by Keith Kelly 04 Mar '99

04 Mar '99

subscribe Keith C. Kelly VP Emerging Technologies and Standards ___________________ keith(a)netspeak.com NetSpeak Corporation 902 Clint Moore Rd. Suite 104 Boca Raton, FL 33487 Direct:(561) 998-8752 Pager (800) 946-4645 #1441506 Main: (561) 998-8700 Fax (561) 997-2401 http://www.netspeak.com The Art of Sound Communication ==================================================================== 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.

1 0

Re: VoIP QOS!
by Jain, Aridaman K (Aridaman) 04 Mar '99

04 Mar '99

Please do not include me in further e-mails. > ---------- > From: long keping[SMTP:lkp@bupt.edu.cn] > Reply To: long keping > Sent: Thursday, March 04, 1999 2:52 PM > To: Joon_Maeng(a)vtel.com > Cc: mpls(a)UU.NET; ITU-SG16(a)mailbag.cps.intel.com; voip(a)imtc.org; > interwkg(a)imtc.org; h323implementors(a)imtc.org; 'T1A1.2 e-mail reflector'; > diff-serv-interest(a)BayNetworks.COM; int-serv(a)isi.edu > Subject: VoIP QOS! > > Joon, > > please include me in any further discussions. > > thanks > > Long keping > lkp(a)bupt.edu.cn >

1 0

Re: About itu-t files?
by Derks, Frank 04 Mar '99

04 Mar '99

Hi Li, from the ITU-T of course! These documents are not freely available. Check: http://www.itu.ch. Frank -----Original Message----- From: Li Jing [mailto:lijing@CN-WHNEC.CCGW.NEC.CO.JP] Sent: 04 March 1999 08:44 To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: About itu-t files? Please tell me where can I get full files about Recommendation G.XXX ? Thanks a lot!

1 0