February 2007 - sg16-avd - lists.packetizer.com

Re: Shaping the direction of H.325
by OKUBO Sakae 28 Feb '07

28 Feb '07

Dear SG16 Experts, This is a follow-up to Paul's posting. All the "H.325" related contributions/documents are collected at the following place: <http://ftp3.itu.ch/av-arch/avc-site/2005-2008/H325_requirements/> <ftp://ftp3.itu.int/avc-site/2005-2008/H325_requirements/> User ID: avguest, Password: Avguest (Note the uppercase 'A') Its index page is: 0-h325req_index.html 0-h325req_index.xls The first document h325req-000 collected "H.325" related records from the meeting reports. Documents referred to therein have been numbered sequentially from h325req-001 to h325req-048. Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ****************************************************************** At 21:46 -0500 07/02/27, Paul E. Jones wrote: >Dear SG16 Experts, > >Over the past year, we have held a few meetings to discuss the >development of a third-generation multimedia system (namely, H.325). >I have been encouraged by the number of people who have either >stated privately or publicly that, indeed, there is a need and point >to reasons why something new needs to be considered as a replacement >to the now 11 year old second-generation systems (H.323 and SIP). > >At the same time, there have been some who have maintained the >position that we have already put a lot of investment into the >existing second-generation systems and ask why we should change. >Perhaps the simplest answer is that “technology never stops”. A >slow-down in research and development activities that aim to improve >the way that we communicate effectively means that little progress >will be made and we will not improve communication much beyond what >the state of the art is today. Innovation should never slow down >and, in fact, I do not think it will. However, innovating around >the architectures and “baggage” of the second-generation systems >is proving to be a challenge, in my opinion. The development, >management, and operation of second-generation systems are becoming >more expensive and, generally, only provide basic voice services are >provided to end users. > >I am trying to collect all of the requirements that have been >submitted thus far in a single document that will not be considered >accepted or rejected, but will serve as a starting point for further >discussion and elaboration. Having read through some of the >material, I still believe that it is important to receive >contributions that speak to these areas: > > >Why is it important to consider development of a third-generation >multimedia system? >What are the business requirements that we need to consider as part >of such an effort? >What problems are we trying to solve? >What modes of communication would we like to enable that are simply >impossible or too costly due to constraints imposed by existing >systems? > >Perhaps you can also think of other fundamental questions that are >still not answered or not answered sufficiently. In any case, we >have just a few days left before the document registration deadline, >so I would like to request that if you have some ideas to share, >please request a document number from Mr. Okubo and submit a >contribution. Even if your company is not a member of the ITU, >contributions are still welcome at this next meeting! > >Cheers! >Paul >

1 0

Shaping the direction of H.325
by Paul E. Jones 27 Feb '07

27 Feb '07

Dear SG16 Experts, Over the past year, we have held a few meetings to discuss the development of a third-generation multimedia system (namely, H.325). I have been encouraged by the number of people who have either stated privately or publicly that, indeed, there is a need and point to reasons why something new needs to be considered as a replacement to the now 11 year old second-generation systems (H.323 and SIP). At the same time, there have been some who have maintained the position that we have already put a lot of investment into the existing second-generation systems and ask why we should change. Perhaps the simplest answer is that "technology never stops". A slow-down in research and development activities that aim to improve the way that we communicate effectively means that little progress will be made and we will not improve communication much beyond what the state of the art is today. Innovation should never slow down and, in fact, I do not think it will. However, innovating around the architectures and "baggage" of the second-generation systems is proving to be a challenge, in my opinion. The development, management, and operation of second-generation systems are becoming more expensive and, generally, only provide basic voice services are provided to end users. I am trying to collect all of the requirements that have been submitted thus far in a single document that will not be considered accepted or rejected, but will serve as a starting point for further discussion and elaboration. Having read through some of the material, I still believe that it is important to receive contributions that speak to these areas: * Why is it important to consider development of a third-generation multimedia system? * What are the business requirements that we need to consider as part of such an effort? * What problems are we trying to solve? * What modes of communication would we like to enable that are simply impossible or too costly due to constraints imposed by existing systems? Perhaps you can also think of other fundamental questions that are still not answered or not answered sufficiently. In any case, we have just a few days left before the document registration deadline, so I would like to request that if you have some ideas to share, please request a document number from Mr. Okubo and submit a contribution. Even if your company is not a member of the ITU, contributions are still welcome at this next meeting! Cheers! Paul

1 0

Shaping the direction of H.325
by Paul E. Jones 27 Feb '07

27 Feb '07

Dear SG16 Experts, Over the past year, we have held a few meetings to discuss the development of a third-generation multimedia system (namely, H.325). I have been encouraged by the number of people who have either stated privately or publicly that, indeed, there is a need and point to reasons why something new needs to be considered as a replacement to the now 11 year old second-generation systems (H.323 and SIP). At the same time, there have been some who have maintained the position that we have already put a lot of investment into the existing second-generation systems and ask why we should change. Perhaps the simplest answer is that "technology never stops". A slow-down in research and development activities that aim to improve the way that we communicate effectively means that little progress will be made and we will not improve communication much beyond what the state of the art is today. Innovation should never slow down and, in fact, I do not think it will. However, innovating around the architectures and "baggage" of the second-generation systems is proving to be a challenge, in my opinion. The development, management, and operation of second-generation systems are becoming more expensive and, generally, only provide basic voice services are provided to end users. I am trying to collect all of the requirements that have been submitted thus far in a single document that will not be considered accepted or rejected, but will serve as a starting point for further discussion and elaboration. Having read through some of the material, I still believe that it is important to receive contributions that speak to these areas: * Why is it important to consider development of a third-generation multimedia system? * What are the business requirements that we need to consider as part of such an effort? * What problems are we trying to solve? * What modes of communication would we like to enable that are simply impossible or too costly due to constraints imposed by existing systems? Perhaps you can also think of other fundamental questions that are still not answered or not answered sufficiently. In any case, we have just a few days left before the document registration deadline, so I would like to request that if you have some ideas to share, please request a document number from Mr. Okubo and submit a contribution. Even if your company is not a member of the ITU, contributions are still welcome at this next meeting! Cheers! Paul

1 0

[h323forum] Need Video Conference protocol stack over ISDN. Looking for vendors to purchase the same.
by syed.ali2＠wipro.com 12 Feb '07

12 Feb '07

Hi, I am Syed from Wipro Technologies. For one of our project, we require H.320 protocol stack to do video conference over ISDN network. Can anybody suggest, the H.320 Video Conference protocol stack vendors contact list? Regards, M. Syed Ali, Project Engineer, Wipro Technologies, Cochin, India. Ph : +91 (0) 484 305 4439 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com --- You are currently subscribed to h323forum as: unknown lmsubst tag argument: '' To unsubscribe send a blank email to leave-h323forum-92494B(a)mail.imtc.org

1 0

Fwd:RE: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from
by OKUBO Sakae 11 Feb '07

11 Feb '07

Dear WP2/16 experts, These incoming liaison statements from SG17 have been made available at the Shenzhen meeting directory: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0703_She/0703_She.html Please also note Mr Campos-Neto's advice as attached regarding TD 320/Gen (AVD-3012). Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ****************************************************************** >Subject: RE: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from >ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) >Date: Fri, 9 Feb 2007 17:30:06 +0100 >Thread-Topic: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from >ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) >Thread-Index: AcYhk8UeGyMSXPc/R3y4G0SaSkexF0qz+L4g >From: <simao.campos(a)itu.int> >To: <Isabelle.Frost(a)itu.int>, <tsg16mgt(a)ties.itu.int> >Sender: owner-tsg16mgt(a)itu.int >Reply-To: <simao.campos(a)itu.int> > >Dear all, > >I would like to particularly draw the attention to the LS in TD >320/Gen, which contains the draft new X.CAP (OASIS Common Alerting >Protocol). > >This is a content standard specifying XML formatting for alerts that >could range from early warning to disasters to other type of >authority-to-authority and authority-to-citizen communications. I >would invite you to look into it and maybe consider situations where >this might impact the work within your Questions. I can think in >particular of Qs 1, 2, 3, 11, 14, 15, 16, 17, 18, 23, 25, 26, 28 & >29/16: > >- 1 & 2: delivery of alerts within existing conferencing systems >- 3: support in H.248 >- 11: Alerting facilities within gateways, selective traffic, >adaptation to text terminals (also Q26!) >- 14: Extension to fax (or a gateway specification) to >interpret/convert alerts into TIFF for delivery of alerts in fax >machines > >- 15-18: frankly, not sure, but may within the different system >specifications (probably not Q16) >- 23: compressed signals could be attached or referenced by CAP messages >- 25: securing CAP messages againg eavesdropping, forgery, etc >within the context of H.323 >- 28: delivery of health-related alerts >- 29: delivery of CAP messages to mobile MM terminals > >These are possible areas to think about! > >Cheers, >Sim黍 > >_____________________________________________ >From: Frost, Isabelle >Sent: 09 February 2007 17:01 >To: tsg16mgt, ITU (MLIST) >Cc: Campos, Simao >Subject: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 >from ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) > >Dear All, > >Please be informed that several incoming LSs, from ITU-T SG 17 >meeting (Gva, 6-15 Dec. 2006), are now available as follows: > >TD 315 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0315/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0315/en to QALL/16 > >TD 316 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0316/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0316/en to Q25/16 > >TD 317 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0317/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0317/en to Qs 25, 1, 2, 3 & 4/16 > >TD 318 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0318/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0318/en to Q25/16 > >TD 319 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0319/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0319/en to QALL/16 > >TD 320 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0320/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0320/en to Qs 1, 2, 3, 11, 14, 15, 16, 17, 18, 23, 25, 28 & 29/16 > >The draft table is also updated at: ><http://ties.itu.int/u/tsg16/sg16/documents/070626/ls/incoming/>http://ties.itu.int/u/tsg16/sg16/documents/070626/ls/incoming/ > >Best regards. > >Isabelle Frost >Assistant for ITU-T Study Groups 6 & 16 >ITU - Telecommunication Standardization Bureau (TSB) >Office M-516 >Tel: +41 22 730 5865 >Fax: +41 22 730 5853 >SG 6 e-mail: tsbsg6(a)itu.int >SG 16 e-mail: tsbsg16(a)itu.int

1 0

Fwd:RE: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006)
by OKUBO Sakae 11 Feb '07

11 Feb '07

Dear WP2/16 experts, These incoming liaison statements from SG17 have been made available at the Shenzhen meeting directory: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0703_She/0703_She.html Please also note Mr Campos-Neto's advice as attached regarding TD 320/Gen (AVD-3012). Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ****************************************************************** >Subject: RE: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from >ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) >Date: Fri, 9 Feb 2007 17:30:06 +0100 >Thread-Topic: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 from >ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) >Thread-Index: AcYhk8UeGyMSXPc/R3y4G0SaSkexF0qz+L4g >From: <simao.campos(a)itu.int> >To: <Isabelle.Frost(a)itu.int>, <tsg16mgt(a)ties.itu.int> >Sender: owner-tsg16mgt(a)itu.int >Reply-To: <simao.campos(a)itu.int> > >Dear all, > >I would like to particularly draw the attention to the LS in TD >320/Gen, which contains the draft new X.CAP (OASIS Common Alerting >Protocol). > >This is a content standard specifying XML formatting for alerts that >could range from early warning to disasters to other type of >authority-to-authority and authority-to-citizen communications. I >would invite you to look into it and maybe consider situations where >this might impact the work within your Questions. I can think in >particular of Qs 1, 2, 3, 11, 14, 15, 16, 17, 18, 23, 25, 26, 28 & >29/16: > >- 1 & 2: delivery of alerts within existing conferencing systems >- 3: support in H.248 >- 11: Alerting facilities within gateways, selective traffic, >adaptation to text terminals (also Q26!) >- 14: Extension to fax (or a gateway specification) to >interpret/convert alerts into TIFF for delivery of alerts in fax >machines > >- 15-18: frankly, not sure, but may within the different system >specifications (probably not Q16) >- 23: compressed signals could be attached or referenced by CAP messages >- 25: securing CAP messages againg eavesdropping, forgery, etc >within the context of H.323 >- 28: delivery of health-related alerts >- 29: delivery of CAP messages to mobile MM terminals > >These are possible areas to think about! > >Cheers, >Sim黍 > >_____________________________________________ >From: Frost, Isabelle >Sent: 09 February 2007 17:01 >To: tsg16mgt, ITU (MLIST) >Cc: Campos, Simao >Subject: Incoming LSs 315, 316, 317, 318, 319 & 320 GEN/16 >from ITU-T SG 17 meeting (Gva, 6-15 Dec. 2006) > >Dear All, > >Please be informed that several incoming LSs, from ITU-T SG 17 >meeting (Gva, 6-15 Dec. 2006), are now available as follows: > >TD 315 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0315/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0315/en to QALL/16 > >TD 316 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0316/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0316/en to Q25/16 > >TD 317 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0317/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0317/en to Qs 25, 1, 2, 3 & 4/16 > >TD 318 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0318/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0318/en to Q25/16 > >TD 319 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0319/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0319/en to QALL/16 > >TD 320 GEN/16: ><http://www.itu.int/md/T05-SG16-070626-TD-GEN-0320/en>http://www.itu.int/md/T05-SG16-070626-TD-GEN-0320/en to Qs 1, 2, 3, 11, 14, 15, 16, 17, 18, 23, 25, 28 & 29/16 > >The draft table is also updated at: ><http://ties.itu.int/u/tsg16/sg16/documents/070626/ls/incoming/>http://ties.itu.int/u/tsg16/sg16/documents/070626/ls/incoming/ > >Best regards. > >Isabelle Frost >Assistant for ITU-T Study Groups 6 & 16 >ITU - Telecommunication Standardization Bureau (TSB) >Office M-516 >Tel: +41 22 730 5865 >Fax: +41 22 730 5853 >SG 6 e-mail: tsbsg6(a)itu.int >SG 16 e-mail: tsbsg16(a)itu.int

1 0

City of the next month meeting - Shenzhen
by OKUBO Sakae 08 Feb '07

08 Feb '07

Dear WP2/16 experts, I have received the following advice from Mr Yongbo Lin, Huawei: At 12:28 +0800 07/02/09, Yangbo Lin wrote: >I noticed that there is a small spelling error about the city of >this meeting, i.e. it should be "Shenzhen" instead of "Shenzen". >This error also exists in the rapporteur meeting information on >ITU-T Web page. Would you inform someone to correct it in order to >avoid any potential confusion or trouble? Thank you! Please note that the correct spelling is SHENZHEN. I will do necessary corrections to relevant documents. -- Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

City of the next month meeting - Shenzhen
by OKUBO Sakae 08 Feb '07

08 Feb '07

Dear WP2/16 experts, I have received the following advice from Mr Yongbo Lin, Huawei: At 12:28 +0800 07/02/09, Yangbo Lin wrote: >I noticed that there is a small spelling error about the city of >this meeting, i.e. it should be "Shenzhen" instead of "Shenzen". >This error also exists in the rapporteur meeting information on >ITU-T Web page. Would you inform someone to correct it in order to >avoid any potential confusion or trouble? Thank you! Please note that the correct spelling is SHENZHEN. I will do necessary corrections to relevant documents. -- Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Documents and meeting registration for Shenzhen meeting
by Patrick Luthi 08 Feb '07

08 Feb '07

Dear Q.1 experts, Please let me know as soon as possible of your plans of document submission! Titles can be provisional and adjusted later. I need a good number of input documents and participants in a week time in order to get SG16 management's final permission to hold the Shenzen meeting. Best regards, Patrick >Registration of attendance - by 1st March, to Christian Groves ><Christian.Groves(a)nteczone.com> (meeting organizer), > >Registration of contributions - by 3 March, to Patrick Luthi ><patrick.luthi(a)tandberg.no> > >Distribution of contributions - by 6 March, to >ftp://avguest:Avguest@ftp3.itu.int/lbc-site/dropbox > >Note - Contributions after the above dates are dealt with as "late" >and their consideration is up to the meeting. > >The meeting information is available at the following place: > >http://avguest@ftp3.itu.int/av-arch/lbc-site/0703_Shenzhen/q1g02.doc > >Early indication of your submission plan is welcome and encouraged, >especially since I will be out of the office from 13-23 February and >will likely not assign contribution numbers during that time. > >Best regards, > >Patrick Luthi >Rapporteur of Q.1/16

1 0

Document registration for the Shenzen meeting
by OKUBO Sakae 08 Feb '07

08 Feb '07

Dear WP2/16 experts, At 01:59 -0500 07/02/05, Christian Groves wrote: >[...]Registration of contributions - by 2 March, to Sakae Okubo ><okubo(a)aoni.waseda.jp> > >Distribution of contributions - by 5 March Please advise me of your plan of document submission at the earliest opportunity. Titles could be provisional or even indication of topics could help. We need some number of input documents and participants in a week time to get SG16 management's approval for holding the Shenzen meeting. Document list <http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0703_She/0703_She.html> Document template <http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0703_She/AVD-template_0703_Sh…> -- Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp Visiting Professor Global Information and Telecommunication Institute (GITI) Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0