- sg16-avd - lists.packetizer.com

Meeting Announcement Joined session Q.29/16 with SG19 in Melbourne
by Leo.Lehmann＠bakom.admin.ch 24 Jan '05

24 Jan '05

Dear experts and colleagues, I have the pleasure to announce a joined session of Q.29/16 together with SG19 during our WP2 Rapporteuer Meeting in Melbourne. SG19 will held an Rapporteuer meeting from March 1st until March 3rd 2005 also in Melbourne. This givese a good opportunity for the exchange and handling of questions on mobility of SG16 and SG19. Unfortunally SG16/WP2 and SG19 uses different meeting locations in Melbourne, which are about 2 hours driving time away from each other. So far one joined session is planned on morning March 1st at SG19 meeting place with WP2 participants , the other on March 2nd at WP2/16 meeting place with SG16 participants. Topics for this joined meeting will be so far - Consolidation of Mobility definitions - new Revision of Technical report on combined mobility betewwen H.323 systems and GPRS/UMTS networks - Further issues Regarding the first both items I am expecting two contributions until beginning of February. If you would like to send further contributions for this Session, please do not hesitate to bring them up until February 12th 2005. If you are interested to participate in the session at the SG19 meeting place, please send the attached registration to 'Leslie.Graf(a)ericsson.com'and please let me also know for information. Best regards Leo Leo Lehmann Rapporteur Q.29/16 Federal Office of Communication (OFCOM) Biel-Bienne Switzerland Tel: +41 32 327 5752 __________________________________________________________________________ __ ___________________________________________________ Dear Mr. Lehmann, At 11:45 +0100 05/01/24, Leo.Lehmann(a)bakom.admin.ch wrote: >I had a telefon conversation with Mr Probst. As this is a good >opportunity for Questions on mobility of SG16 and >SG19 to meet, Mr Probst fully support an additional setting of a >Q.29/16 meeting in Melbourne to enable a joined session with SG19 >qusetions. Thank you very much. Please publicize the Melbourne sessions on mobility through the mailing list. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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 ****************************************************************** Dear Mr Okubo, I had a telefon conversation with Mr Probst. As this is a good opportunity for Questions on mobility of SG16 and SG19 to meet, Mr Probst fully support an additional setting of a Q.29/16 meeting in Melbourne to enable a joined session with SG19 qusetions. Best regards Leo -----Ursprüngliche Nachricht----- Von: OKUBO Sakae [mailto:okubo@mxz.mesh.ne.jp] Gesendet: Sonntag, 23. Januar 2005 17:57 An: Lehmann Leo Cc: Simao Campos-Neto Betreff: Fwd:Re: Fwd:Q.29 interim meeting/joint meeting with SG19 Dear Mr. Lehmann, I have received the following auto-reply to my message seeking his agreement. Could you please kindly get in touch with him via the advised mobile phone and convey our request? It would be too late if we start after 30 March. >From: probst-pa(a)bluewin.ch >Subject: Re: Fwd:Q.29 interim meeting/joint meeting with SG19 >To: okubo(a)mxz.mesh.ne.jp >Date: Sun, 23 Jan 2005 16:43:56 +0000 >Delivered-To: probst-pa(a)bluewin.ch >X-Biglobe-VirusCheck: Mon, 24 Jan 2005 01:43:59 +0900 > >Thank you very much for your message. >I am away from my office for two weeks and will process your mail only >later (30.1.2005). For urgent issues, you have the possibility to reach >me on my mobile >phone: +41 79 229 96 56. > >Best regards, > >P.A.Probst -----Ursprüngliche Nachricht----- Von: OKUBO Sakae [mailto:okubo@mxz.mesh.ne.jp] Gesendet: Sonntag, 23. Januar 2005 17:44 An: Pierre-Andre PROBST Cc: Istvan Sebestyen; Simao Campos-Neto; Lehmann Leo; Christian Groves Betreff: Fwd:Q.29 interim meeting/joint meeting with SG19 Dear Mr. Probst, This is to seek your agreement on that Q.29 will meet in Melbourne early March as requested by Mr. Lehmann. Strictly speaking, the WP2/16 report of last SG16 meeting says that Q.29 will meet only in May and the current SG16 web page <http://www.itu.int/ITU-T/studygroups/com16/meetings.html> also indicates so. As this is a good opportunity for Questions on mobility of SG16 and SG19 to meet, I hope you could accept this additional setting. Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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 ****************************************************************** -----Ursprüngliche Nachricht----- Von: John Visser [mailto:jvisser@nortelnetworks.com] Gesendet: Mittwoch, 19. Januar 2005 16:56 An: David.Mcfarlane(a)nokia.com; 'Farrokh Khatibi'; 'Felix,Zhang'; 'leo.lehmann(a)bakom.admin.ch' Cc: peter.m.adams(a)bt.com; Leslie Graf; tatiana.kurakova(a)itu.int Betreff: RE: documents for joint rapporteurs meeting Colleagues: I think everyone is aware of Q.29/16 "Mobility for Multimedia Systems and Services" http://www.itu.int/ITU-T/studygroups/com16/sg16-q29. Leo Lehman is the Rapporteur and he and I have had several discussions on how best to coordinate our mobility studies. Q.2 and 5/19 and Q.6/13 are meeting jointly in Melbourne 1-3 March. Q.29/16 is meeting in Marysville the week of 28 Feb. Marysville is about 2 hours drive outside Melbourne. In my discussions with Leo, we addressed how best to coordinate our work and we came up with the following proposal: Tuesday, 1 March, Leo (and possibly others) would come to Melbourne for the afternoon to take part in the Q.2 and 5/19 and Q.6/13 joint discussions. The objective would be to identify mobility-related definitions and terminology and work towards alignment so that these would be common across all mobility discussions. I anticipate that Leo would also be willing to provide an overview of the Work of Q.5/16 in the previous study period, and the current work anticipated in Q.29/16. Wednesday, 2 March, I (and possibly others) would go to Marysville to sit in on the Q.29/16 discussions. The objective would be to support alignment on mobility-related definitions and terminology from the previous day. I anticipate that I would also provide an overview of the work of Q.2 and 5/19 and Q.6/13. I would appreciate any comments and concerns from you prior to formalizing this further (though we don't want to get very formal at a rapporteurs' meeting.) Regards, John John Visser, P.Eng. Chairman, ITU-T SG 19 "Mobile Telecommunication Networks" http://www.itu.int/ITU-T/studygroups/com19 Phone: +1-613-763-7028 Fax: +1-613-763-2697 Mobile: +1-613-276-6096 Email: jvisser(a)nortel.com

1 0

Follow up: Question 2,3,4,5,21,22,24,25 and 29/16 Rapporteur Meeting
by Christian Groves 20 Jan '05

20 Jan '05

Hello all, As per the Meeting Announcement please send the your meeting registration to me. Please do so even if you had replied previously to my informal request on who intends to come. The registration from the meeting announcement means you are actually coming! Regards, Christian

1 0

Meeting Announcement: Question 2,3,4,5,21,22,24,25 and 29/16 Rapporteur Meeting
by Christian Groves 16 Jan '05

16 Jan '05

To Experts of ITU-T SG16 Questions 2,3,4,5,21,22,24,25 and 29/16. Cc Mr. P-A. Probst, Chairman of SG16 <probst-pa(a)bluewin.ch> Mr. Paul Barrett, Vice Chairman of SG16 <paul.barrett(a)psytechnics.com> Mr. Yushi Naito, Vice Chairman of SG16 <naitoy(a)attglobal.net> Ms. Claude Lamblin, Vice Chairman of SG16 <claude.lamblin(a)rd.francetelecom.com> Mr. I Sebestyen, Vice Chairman of SG16 <Istvan.Sebestyen(a)siemens.com> Mr. S. Campos-Neto, ITU TSB <simao.campos(a)itu.int> De P Jones Rapporteur for Q.2/16 <paulej(a)packetizer.com> C Groves Rapporteur for Q.3/16 <Christian.Groves(a)ericsson.com.au> S Okubo Rapporteur for Q.4/16 <sokubo(a)waseda.jp> R Gilman Rapporteur for Q.5/16 <rrg(a)avaya.com> B Lamer Rapporteur for Q.21(B)/16 <bastien.lamer(a)rd.francetelecom.com> S Okubo Interim Rapporteur for Q.22(C)/16 <sokubo(a)waseda.jp> S.H. Jeong Rapporteur for Q.24(F)/16 <shjeong(a)hufs.ac.kr> M Euchner Rapporteur for Q.25(G)/16 <Martin.Euchner(a)siemens.com> L Lehmann Rapporteur for Q.29(K)/16 <Leo.Lehmann(a)bakom.admin.ch> ------------------------------------------------------------------- Subject: Notice of Joint Rapporteur Meeting in Melbourne, Australia Date: 28 February - 4 March 2005 ------------------------------------------------------------------- Dear Experts of Questions 2,3,4,5,21,22,24,25 and 29/16, The subject meeting of ITU-T SG16 experts will be held in Marysville, outside of Melbourne, Australia at the Maryland Country House. Details of the meeting are contained herein. 1. Date ^^^^^^^ 28th (Monday) February - 4 (Friday) March 2005 Meeting will start at 9:00 AM on the first day Closing around 18:00 on the final day 2. Venue ^^^^^^^^ Maryland Country House, Marysville Victoria Australia Falls Rd, Marysville, Victoria 3779 Australia http://www.marylands.com.au/ Ph: +61 3 5963 3204 Fax: +61 3 5963 3251 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group activities 2) Q.2/16 Real-Time Audio, Video, and Data Communication over Packet-Switched Networks - Coordinate with other SDOs, Questions, or Study Groups - Review items proposed for the H.323-series Implementers Guide - Progress work on the following work items * H.323 Annex Gv2 * H.323 Annex I * H.323 Annex Ov2 * H.460.17 (RAS Tunneling) * H.460.cdor * H.460.geo * H.460.location * H.460.dhcp * H.460.gaam * H.460.presence * H.460.sms - Discuss miscellaneous and new work items 3) Q.3/16 Multimedia Gateway Control Architectures and Protocols - Coordinate with other SDOs, Questions, or Study Groups - Progress work on * H.248.1v3, * H.248.1 Annex F * Revised H.248.8 * H.248.36 * H Series Supplement BHCoA, * H.248.1 V1 IG * H.248 Sub-series IG * H Series Supplement 2 v7. - Consider new material. 4) Q.4/16 Advanced multimedia communication service features on top of the ITU-T defined multimedia system platforms - Progress work on * H.350-series maintenance * Addition to H.350-series * Study of new service features 5) Q.5/16 Control of NAT and Firewall Traversal for H.300-Series Multimedia Systems - Coordinate with other SDOs, Questions, or Study Groups - Work to finalize the requirements for NAT/FW traversal - Progress work on H.proxy - Consider various solution proposals for NAT/FW traversal 6) Q.21/16 Multimedia Architecture - Progress work on * Multimedia Architecture and End to end Open Services Architectural Framework. * Analysis of relevant Architectures prepared by other bodies 7) Q.22/16 Multimedia applications and services - Progress work on * F.VTIP, * F.MMCIP, * F.DL, * F.AVoD * Other new services ? Service description and requirements 8) Q.24/16 Quality of Service and End-to-end Performance in Multimedia Systems - Progress work on * H.323 Annex N (QoS) * H.priority (Service Priority) * H.trans.control (QoS Signalling to Transport Domains) - Discussion on new and miscellaneous items 9) Q.25/16 Multimedia Security in Next-Generation Networks The objectives for this meeting are: - Progress work on * H.235.x V4 subseries, * H.FSIC, * H.460.spn, - Coordination, - Maintenance H.235, - Consider new material. 10) Q.29/16 Mobility for Multimedia Systems and Services - Follow up status of work items - Finalization of technical report regarding combined mobility 11) Interaction with other groups 12) Future work plan 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 23:59 UTC, 18 February 2005 /// /// Distribution of the document: by 23:59 UTC, 21 February 2005 /// /// Use the ftp site (or e-mail reflector) for distribution /// 1) When you are going to submit a document, please notify Sakae Okubo < sokubo(a)waseda.jp>, document manager of this meeting, as soon as possible, by 23:59 UTC, Friday 18 February 2005 at the latest. Document number AVD-nnnn will be allocated. Early indication of your submission plan is welcome and encouraged. Note - Prefix "AVD" comes from Audio, Video and Data. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document AVD-{nnnn}| | Study Group 16 {Version m if relevant}| | 2,3,4,5,21,22,24,25 and 29/16 Rapporteur Meeting {Date}| | Melbourne, 28 February - 4 March 2005 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ Note: A template for the AVD document can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/AVD-template.doc> This may be modified and used for the purpose of document submission at this meeting. 3) File format: Use of Word, PDF, ASCII or HTML is recommended. 4) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (23:59 UTC, Monday 21 February 2005 or before) by posting them at either of the following: - Uploading via FTP Site: ftp3.itu.int/ User ID: avguest Password: Avguest (Note the uppercase 'A') Directory: avc-site/Incoming - E-mail reflector E-mail address: itu-sg16(a)external.cisco.com To subscribe: Send e-mail to majordomo(a)cisco.com In the body of the message, put: subscribe itu-sg16 Please avoid the use of reflector when your document is voluminous. 5) Input documents can be retrieved from 0502_Mel directory of the ftp site once Mr. Okubo has an opportunity to put them into place. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/0502_Mel 6) The document distribution / presentation at the meeting will be all electronic. Participants must bring along a laptop, wireless lan card and/or Ethernet card, and Ethernet cable in order to access the documents. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be hosted by Ericsson Australia at the Maryland Country House in Marysville outside Melbourne Australia. The meeting invitation containing logistic information can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/Mel_Invitation.do c> 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send e-mail to Christian Groves <Christian.Groves(a)ericsson.com>, providing the family name, given name, company name, and e-mail address of person(s) attending. Early registration of your attendance is welcome and encouraged. 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be held at the Maryland Country House. This will be a "live-in" meeting. To secure a room please fill in the hotel registration form in the meeting invitation (http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/Mel_Invitation.do c) as soon as possible and return as indicated on the form. We are looking forward to meeting with you in Melbourne. Sincerely yours, Paul JONES Christian GROVES (meeting organizer of this meeting) Sakae OKUBO (document manager of this meeting) Robert GILMAN Istvan Sebestyen Bastien LAMER Seong-ho JEONG Martin EUCHNER Leo LEHMANN ----------

1 0

Meeting Announcement: Question 2,3,4,5,21,22,24,25 and 29/16 Rapporteur
by Christian Groves 16 Jan '05

16 Jan '05

To Experts of ITU-T SG16 Questions 2,3,4,5,21,22,24,25 and 29/16. Cc Mr. P-A. Probst, Chairman of SG16 <probst-pa(a)bluewin.ch> Mr. Paul Barrett, Vice Chairman of SG16 <paul.barrett(a)psytechnics.com> Mr. Yushi Naito, Vice Chairman of SG16 <naitoy(a)attglobal.net> Ms. Claude Lamblin, Vice Chairman of SG16 <claude.lamblin(a)rd.francetelecom.com> Mr. I Sebestyen, Vice Chairman of SG16 <Istvan.Sebestyen(a)siemens.com> Mr. S. Campos-Neto, ITU TSB <simao.campos(a)itu.int> De P Jones Rapporteur for Q.2/16 <paulej(a)packetizer.com> C Groves Rapporteur for Q.3/16 <Christian.Groves(a)ericsson.com.au> S Okubo Rapporteur for Q.4/16 <sokubo(a)waseda.jp> R Gilman Rapporteur for Q.5/16 <rrg(a)avaya.com> B Lamer Rapporteur for Q.21(B)/16 <bastien.lamer(a)rd.francetelecom.com> S Okubo Interim Rapporteur for Q.22(C)/16 <sokubo(a)waseda.jp> S.H. Jeong Rapporteur for Q.24(F)/16 <shjeong(a)hufs.ac.kr> M Euchner Rapporteur for Q.25(G)/16 <Martin.Euchner(a)siemens.com> L Lehmann Rapporteur for Q.29(K)/16 <Leo.Lehmann(a)bakom.admin.ch> ------------------------------------------------------------------- Subject: Notice of Joint Rapporteur Meeting in Melbourne, Australia Date: 28 February - 4 March 2005 ------------------------------------------------------------------- Dear Experts of Questions 2,3,4,5,21,22,24,25 and 29/16, The subject meeting of ITU-T SG16 experts will be held in Marysville, outside of Melbourne, Australia at the Maryland Country House. Details of the meeting are contained herein. 1. Date ^^^^^^^ 28th (Monday) February - 4 (Friday) March 2005 Meeting will start at 9:00 AM on the first day Closing around 18:00 on the final day 2. Venue ^^^^^^^^ Maryland Country House, Marysville Victoria Australia Falls Rd, Marysville, Victoria 3779 Australia http://www.marylands.com.au/ Ph: +61 3 5963 3204 Fax: +61 3 5963 3251 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group activities 2) Q.2/16 Real-Time Audio, Video, and Data Communication over Packet-Switched Networks - Coordinate with other SDOs, Questions, or Study Groups - Review items proposed for the H.323-series Implementers Guide - Progress work on the following work items * H.323 Annex Gv2 * H.323 Annex I * H.323 Annex Ov2 * H.460.17 (RAS Tunneling) * H.460.cdor * H.460.geo * H.460.location * H.460.dhcp * H.460.gaam * H.460.presence * H.460.sms - Discuss miscellaneous and new work items 3) Q.3/16 Multimedia Gateway Control Architectures and Protocols - Coordinate with other SDOs, Questions, or Study Groups - Progress work on * H.248.1v3, * H.248.1 Annex F * Revised H.248.8 * H.248.36 * H Series Supplement BHCoA, * H.248.1 V1 IG * H.248 Sub-series IG * H Series Supplement 2 v7. - Consider new material. 4) Q.4/16 Advanced multimedia communication service features on top of the ITU-T defined multimedia system platforms - Progress work on * H.350-series maintenance * Addition to H.350-series * Study of new service features 5) Q.5/16 Control of NAT and Firewall Traversal for H.300-Series Multimedia Systems - Coordinate with other SDOs, Questions, or Study Groups - Work to finalize the requirements for NAT/FW traversal - Progress work on H.proxy - Consider various solution proposals for NAT/FW traversal 6) Q.21/16 Multimedia Architecture - Progress work on * Multimedia Architecture and End to end Open Services Architectural Framework. * Analysis of relevant Architectures prepared by other bodies 7) Q.22/16 Multimedia applications and services - Progress work on * F.VTIP, * F.MMCIP, * F.DL, * F.AVoD * Other new services ? Service description and requirements 8) Q.24/16 Quality of Service and End-to-end Performance in Multimedia Systems - Progress work on * H.323 Annex N (QoS) * H.priority (Service Priority) * H.trans.control (QoS Signalling to Transport Domains) - Discussion on new and miscellaneous items 9) Q.25/16 Multimedia Security in Next-Generation Networks The objectives for this meeting are: - Progress work on * H.235.x V4 subseries, * H.FSIC, * H.460.spn, - Coordination, - Maintenance H.235, - Consider new material. 10) Q.29/16 Mobility for Multimedia Systems and Services - Follow up status of work items - Finalization of technical report regarding combined mobility 11) Interaction with other groups 12) Future work plan 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 23:59 UTC, 18 February 2005 /// /// Distribution of the document: by 23:59 UTC, 21 February 2005 /// /// Use the ftp site (or e-mail reflector) for distribution /// 1) When you are going to submit a document, please notify Sakae Okubo < sokubo(a)waseda.jp>, document manager of this meeting, as soon as possible, by 23:59 UTC, Friday 18 February 2005 at the latest. Document number AVD-nnnn will be allocated. Early indication of your submission plan is welcome and encouraged. Note - Prefix "AVD" comes from Audio, Video and Data. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document AVD-{nnnn}| | Study Group 16 {Version m if relevant}| | 2,3,4,5,21,22,24,25 and 29/16 Rapporteur Meeting {Date}| | Melbourne, 28 February - 4 March 2005 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ Note: A template for the AVD document can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/AVD-template.doc> This may be modified and used for the purpose of document submission at this meeting. 3) File format: Use of Word, PDF, ASCII or HTML is recommended. 4) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (23:59 UTC, Monday 21 February 2005 or before) by posting them at either of the following: - Uploading via FTP Site: ftp3.itu.int/ User ID: avguest Password: Avguest (Note the uppercase 'A') Directory: avc-site/Incoming - E-mail reflector E-mail address: itu-sg16(a)external.cisco.com To subscribe: Send e-mail to majordomo(a)cisco.com In the body of the message, put: subscribe itu-sg16 Please avoid the use of reflector when your document is voluminous. 5) Input documents can be retrieved from 0502_Mel directory of the ftp site once Mr. Okubo has an opportunity to put them into place. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/0502_Mel 6) The document distribution / presentation at the meeting will be all electronic. Participants must bring along a laptop, wireless lan card and/or Ethernet card, and Ethernet cable in order to access the documents. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be hosted by Ericsson Australia at the Maryland Country House in Marysville outside Melbourne Australia. The meeting invitation containing logistic information can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/Mel_Invitation.do c> 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send e-mail to Christian Groves <Christian.Groves(a)ericsson.com>, providing the family name, given name, company name, and e-mail address of person(s) attending. Early registration of your attendance is welcome and encouraged. 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be held at the Maryland Country House. This will be a "live-in" meeting. To secure a room please fill in the hotel registration form in the meeting invitation (http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/Mel_Invitation.do c) as soon as possible and return as indicated on the form. We are looking forward to meeting with you in Melbourne. Sincerely yours, Paul JONES Christian GROVES (meeting organizer of this meeting) Sakae OKUBO (document manager of this meeting) Robert GILMAN Istvan Sebestyen Bastien LAMER Seong-ho JEONG Martin EUCHNER Leo LEHMANN ----------

1 0

Fwd:Update on AAP Status for SG 16 Recs Consented in November 04
by OKUBO Sakae 14 Jan '05

14 Jan '05

*** FYI *** >Subject: Update on AAP Status for SG 16 Recs Consented in November 04 >Date: Thu, 13 Jan 2005 22:00:19 +0100 >From: <simao.campos(a)itu.int> >To: <tsg16mgt(a)ties.itu.int> > >Dear all, > >for your info: >- all 35 Recs that started LC on Dec 1st [AAP#3] have been approved >- the two Recs that started LC on Dec 16 [AAP#4] have also been approved >- F.750 will start LC this weeked (16 Jan) [AAP#5] >- H.264, H.264.1 and H.264.2 will start LC on Feb 1st [AAP#6], >taking advantage of the Q.6 Rapporteurs meeting starting next week > >Cheers, >Simao > >===================================================================== >Sim黍 Ferraz de Campos Neto Counsellor, ITU-T SG 6&16 >International Telecommunication Union Tel: +41-22-730-6805 >Place des Nations Fax: +41-22-730-5853 >Geneva CH1211 - Switzerland E-mail: simao.campos(a)itu.int >On the web: www.itu.int/ITU-T/studygroups/com16 >===================================================================== > ***** Practice random kindness and senseless acts of beauty ***** >=====================================================================

1 0

RE: H.460.cdor
by Even, Roni 13 Jan '05

13 Jan '05

Paul, I support Ernst view. This is also my recollection of the issues in San Jose. A caller asking to retarget against my diversions or filtering is considered to be a spammer. Roni _____ From: Horvath Ernst [mailto:ernst.horvath@SIEMENS.COM] Sent: Thursday, January 13, 2005 4:19 PM To: 'Paul E. Jones'; itu-sg16(a)external.cisco.com Cc: 'Danilo Kempf' Subject: RE: H.460.cdor Paul, I consider the concerns serious enough to discontinue work on this item unless the author will provide a significantly amended draft. My recollection of the San Jose discussions is: * the scope of the service is not precise enough; currently it covers all forms of "retargeting", even such things as the "diversion" of a party to an MCU in order to join it to a conference; the scope should be narrowed to real diversion cases; * the service is quite complex and would need to be supported by a large number of entities, otherwise it would not work in the desired way; * due to the complexity and the vague scope interoperable implementations may be hard to achieve; * people were concerned about possible mis-use of the service for spamming. So, in order to move forward, is the editor prepared to have another go on this service along the lines indicated above? Maybe what is needed is something like a simple "preference indication" for reaching the original destination only. I would also like to mention that in H.450.x there is already an operation defined for overriding diversion-on-busy; this is needed to enable services like call intrusion. Regards, Ernst -----Original Message----- From: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Sent: Donnerstag, 13. Jänner 2005 08:47 To: itu-sg16(a)external.cisco.com Cc: 'Danilo Kempf' Subject: H.460.cdor Dear Experts, We need to bring closure to the open work item H.460.cdor. The last discussion did not end up with any decision. The concerns I noted were that people might abuse the functionality and that it might cause some confusion. In my opinion, neither of those concerns are serious enough to delay the work further. Can we get agreement to move this forward? Paul

1 0

RE: H.460.cdor
by Horvath Ernst 13 Jan '05

13 Jan '05

Paul, I consider the concerns serious enough to discontinue work on this item unless the author will provide a significantly amended draft. My recollection of the San Jose discussions is: * the scope of the service is not precise enough; currently it covers all forms of "retargeting", even such things as the "diversion" of a party to an MCU in order to join it to a conference; the scope should be narrowed to real diversion cases; * the service is quite complex and would need to be supported by a large number of entities, otherwise it would not work in the desired way; * due to the complexity and the vague scope interoperable implementations may be hard to achieve; * people were concerned about possible mis-use of the service for spamming. So, in order to move forward, is the editor prepared to have another go on this service along the lines indicated above? Maybe what is needed is something like a simple "preference indication" for reaching the original destination only. I would also like to mention that in H.450.x there is already an operation defined for overriding diversion-on-busy; this is needed to enable services like call intrusion. Regards, Ernst -----Original Message----- From: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Sent: Donnerstag, 13. Jänner 2005 08:47 To: itu-sg16(a)external.cisco.com Cc: 'Danilo Kempf' Subject: H.460.cdor Dear Experts, We need to bring closure to the open work item H.460.cdor. The last discussion did not end up with any decision. The concerns I noted were that people might abuse the functionality and that it might cause some confusion. In my opinion, neither of those concerns are serious enough to delay the work further. Can we get agreement to move this forward? Paul

1 0

H.460.cdor
by Paul E. Jones 13 Jan '05

13 Jan '05

Dear Experts, We need to bring closure to the open work item H.460.cdor. The last discussion did not end up with any decision. The concerns I noted were that people might abuse the functionality and that it might cause some confusion. In my opinion, neither of those concerns are serious enough to delay the work further. Can we get agreement to move this forward? Paul

1 0

FW: RFC 3944 on H.350 Directory Services
by simao.campos＠ITU.INT 05 Jan '05

05 Jan '05

Dear colleagues, FYI Simao -----Original Message----- From: rfc-editor(a)rfc-editor.org Sent: 11 December 2004 01:24 To: ietf-announce(a)ietf.org Cc: rfc-editor(a)rfc-editor.org Subject: RFC 3944 on H.350 Directory Services A new Request for Comments is now available in online RFC libraries. RFC 3944 Title: H.350 Directory Services Author(s): T. Johnson, S. Okubo, S. Campos Status: Informational Date: December 2004 Mailbox: Tyler_Johnson(a)unc.edu, sokubo(a)waseda.jp, simao.campos(a)itu.int Pages: 30 Characters: 61160 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-johnson-h350-directory-serv-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3944.txt The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store. Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute .. Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.

1 0

Output documents of the SG16 meeting
by OKUBO Sakae 15 Dec '04

15 Dec '04

Dear Christian and all, The Q3 output documents you provided have been moved to the /0411_Gen directory. Please see http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/0411_Gen.html for the index. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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

Meeting Dates for Interim WP2 Rapporteurs Meeting
by Christian Groves 14 Dec '04

14 Dec '04

Hello all, I'd like to confirm that the I have booked the meeting venue for the Monday 28th February 2005 to 4th March 2005. Could you please send me a reply email by "Sunday the 19th of December" if you are intending on coming? If you are a regular attender please also send if you are not attending. Note: This is NOT a booking it is only an indication. We will send out a proper invitation/registration early in 2005. I need to have an idea of numbers so that I can book an appropriate number of rooms. The venue is around 90minutes drive from Melbourne Airport so I would envisage that some people would like to arrive the day before and possibly stay the friday night. Please indicate with an [x]: I will be attending 28/02/2005 - 04/03/2005 [ ] Yes [ ] No I will need accomodation on Sunday 27/02/2005 [ ] Yes [ ] No I will need accomodation on Friday Night 04/02/2005 [ ] Yes [ ] No Regards, Christian

1 0

FW: RFC 3944 on H.350 Directory Services
by Euchner Martin 13 Dec '04

13 Dec '04

FYI: -----Original Message----- From: ietf-announce-bounces(a)ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor(a)rfc-editor.org Sent: Samstag, 11. Dezember 2004 01:24 To: ietf-announce(a)ietf.org Cc: rfc-editor(a)rfc-editor.org Subject: RFC 3944 on H.350 Directory Services <<Untitled Attachment>> <<ATT51554.txt>> A new Request for Comments is now available in online RFC libraries. RFC 3944 Title: H.350 Directory Services Author(s): T. Johnson, S. Okubo, S. Campos Status: Informational Date: December 2004 Mailbox: Tyler_Johnson(a)unc.edu, sokubo(a)waseda.jp, simao.campos(a)itu.int Pages: 30 Characters: 61160 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-johnson-h350-directory-serv-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3944.txt The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store. Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute .. Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- In order to maintain computing infrastructure integrity, Cisco Systems Enterprise Messaging Services and InfoSec teams have set a mail policy disallowing executable attachments in email. This message contained an executable attachment type that is prohibited by this policy. The attachment has been removed from this message and copied to quarantine by our systems. It will be held in quarantine for seven days in the event that the content needs to be retrieved. Please be aware many viruses attempt to look like legitimate email or notifications from anti-virus systems. We will clearly mark a seperation between our notifications and the original email as follows: "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY" For further reference information about viruses and email antivirus efforts within Cisco, please visit: http://wwwin.cisco.com/it/ems/services/antiviral If your concern isn't addressed by the information in this notification or the above web page, you may open a support request: http://wwwin.cisco.com/support/ Select "Messaging", "Email-Related", "Mail Routing" Please include in the text of your case the following information: * Full headers of the message. Documentation on displaying the full headers is available at this URL: http://wwwin.cisco.com/support/library/faqs/solution002471.html * This unique quarantine identifier: iBD8aMm4007020 If the matter is urgent, you may follow up by calling one of the below referenced numbers. Please make every effort to provide the above requested information via the support web tool prior to calling as it will greatly aid the resolution of your issue. Americas: 1 408 526 8888 Asiapac +61 2 8446 8888 EMEA +31 20 485 4888 Japan +81 3 5549 6888 US (Toll Free) 1| 800| 888| 8187| (ext.68888) Thank you for your cooperation, Enterprise Messaging Services Cisco Systems, Inc

1 0

Megaconference VI is under way
by Nadim El-Khoury 09 Dec '04

09 Dec '04

Hi Everyone, Megaconference VI is under way. The largest H.323 and Sip Conference in the world. You can find out more about the participants and also view the streaming of the event. http://www.megaconference.org/ Thank you Nadim Elias El-Khoury

1 0

Fwd:Results of SG 16 meeting
by OKUBO Sakae 02 Dec '04

02 Dec '04

Dear WP2/16 experts, Mr. Campos-Neto's message is forwarded. At 09:10 +0100 04/12/02, <simao.campos(a)itu.int> wrote: >Please note that the results for the SG 16 meeting are available at: > >http://www.itu.int/ITU-T/studygroups/com16/results.html > >Please broadcast to your groups. > >Any comments, etc, please send asap. > >Thanks >Simao > >===================================================================== >Sim黍 Ferraz de Campos Neto Counsellor, ITU-T SG 16 >International Telecommunication Union Tel: +41-22-730-6805 >Place des Nations Fax: +41-22-730-5853 >Geneva CH1211 - Switzerland E-mail: simao.campos(a)itu.int >On the web: www.itu.int/ITU-T/studygroups/com16 >===================================================================== > ***** Practice random kindness and senseless acts of beauty ***** -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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

Outcome of the SG16 meeting - WP2
by OKUBO Sakae 26 Nov '04

26 Nov '04

Dear WP2/16 experts, The two week SG16 meeting has been finished with the major outcome listed after my signature. The following output documents have been uploaded to /2001-2004/0411_Gen directory of the avc-site: Editor (J Li) Requirements for Network Address Translator and Firewall Traversal for H.323 Multimedia Systems Editor (F Siyavudeen) Draft revised H.323 Implementers’ Guide (for Approval) WP2/16 Chair Draft Report of Working Party 2/16 (Multimedia Systems and Terminals) WP2/16 Chair List of outgoing liaison statements from WP2 Please see http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/0411_Gen.html for the index. Taking this opportunity, Rapporteurs and Editors are encouraged to upload their output documents for final submission to the /Incoming of the avc-site or e-mail them to me. Last but not least, I would like to thank all the Rapporteurs, Editors, contributors and participants who have made the meeting productive. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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 ****************************************************************** =============================== Draft Recommendations consented =============================== New H.222.0 Amendment 4 "ISAN and V-ISAN use in the content labelling descriptor" New H.222.0 Amendment 5 "New Audio profile and level Signalling and change to audio_type table entry" New H.222.0 Corrigendum 3 "Information technology - Generic coding of moving pictures and associated audio information: Systems" Revised H.224 "A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels" New H.241 Amendment 1 "Extended video procedures and control signals for H.300 series terminals" New H.310 Corrigendum 1 "Broadband audiovisual communication systems and terminals" New H.321 Corrigendum 1 "Adaptation of H.320 visual telephone terminals to B-ISDN environments" New H.324 Amendment 1 "Terminal for low bit-rate multimedia communication" Revised V.140 "Procedures for establishing communication between two multiprotocol audiovisual terminals using digital channels at a multiple of 64 or 56 kbit/s" Draft new Recommendation H.460.16 "Multiple Message Release Sequence Capability" Draft revised H.323 Annex D ("Annex Dv3") Draft new H.323 Annex M.4 "Tunnelling of Narrowband Signalling Syntax (NSS) for H.323" Draft revised H.245 "Control protocol for multimedia communication" Version 11 Revision 1 of H.248.2, "Facsimile, text conversation and call discrimination packages" Revision 1 of H.248.9, "Advanced Audio Server Packages" Revision 1 of H.248.23, "Enhanced Alerting packages" Amendment 1 to H.248.26, "Enhanced Analogue Line Packages" New H.248.29, "International CAS Compelled Register Signalling Packages" New H.248.32, "Detailed Congestion Reporting Package" New H.248.33, "PCM Frame Spare Bit Package" New H.248.34, "Stimulus Analogue Lines package" New H.248.35, "Coin package" Draft new F.750 (ex-F.MDF) "Metadata Framework Recommendation" for Consent New Corrigendum 1 of H.235 (2003) "Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals" New H.235 Annex G "Usage of the MIKEY Key Management Protocol for the Secure Real Time Transport Protocol (SRTP) within H.235" ================== Documents approved ================== Revised H.320-series Implementors' Guide Draft revised H.323 Implementors' Guide Draft revised H-series Supplement 4: "Repository of generic parameters for ITU-T Recommendations H.460.x sub-series Implementors' Guide for Recommendation H.248.1 Version 1 (03/2002) ("Media Gateway Control Protocol") H.248.x Sub-series Implementors' Guide Supplement 2 to the H-Series: H.248 Sub-Series: Packages Guide Release 6 H.350-series Implementors' Guide Draft new Supplement 1 to T-Series Recommendations "Conformance Testing Requirements for Recommendations of the T.170-Series" ============================= Important document progressed ============================= Requirements for Network Address Translator and Firewall Traversal for H.323 Multimedia Systems -----------

1 0

Firewall/NAT traversal description related to D.85
by Patrick Luthi 16 Nov '04

16 Nov '04

>-----Original Message----- >From: Tom-Ivar Johansen [mailto:tom.ivar.johansen@tandberg.no] >Sent: 16. november 2004 20:47 >To: itu-sg16 (itu-sg16(a)external.cisco.com) >Subject: Firewall/NAT traversal description related to D-85 > >Dear experts, >the attached document is shared with the group to further discussions on >Firewall/NAT traversal as requested by some experts at the Study Group >meeting. It gives more details about the TANDBERG Firewall/NAT traversal >solution mentioned in Delayed Contribution 85. > >Questions and comments are welcome. > >Best regards, >Tom-Ivar Johansen >Phone: + 47 67 125 125 >Direct: + 47 98 289 878 >Fax: + 47 67 125 234 >MailTo:tom.ivar.johansen@tandberg.net >http://www.tandberg.net > > ><file://C:\Program%20Files\Eudora\data\attach\ASSENT-ITU%20distributed.rtf>ASSENT-ITU >distributed.rtf

1 0

Re: Editor_Draft_H.235.8
by OKUBO Sakae 15 Nov '04

15 Nov '04

Dear Mr. Fourie, At 17:29 -0800 04/11/14, Louis Fourie wrote: > I have uploaded Editor_Draft_H.235.8.zip to avc-site/Incoming. At 20:47 -0800 04/11/14, Louis Fourie wrote: > I have uploaded Editor_TD_comment_on_H.235.8.zip to avc-site/Incoming. These have been moved to /2001-2004/0411_Gen directory. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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 for your review
by OKUBO Sakae 13 Nov '04

13 Nov '04

Dear all, At 17:42 +0100 04/11/10, Tegeler Juergen wrote: >I have just uploaded one document to the ftp server for WP2/Q.3. >It is called: >SG16-041116-TD-WP2-0036 Siemens01_H.248.9 Revision1 enhanced INAP IF.zip >It was transfered to tsb on time and appears on the ITU website. At 11:45 -0500 04/11/11, Kevin Boyle wrote: >I have uploaded to the incoming folder my 9 editor's documents, 2 >delayed documents from Nortel, and one delayed document from the >United States for the information of the delegates. These and other documents have been moved from /Incoming to /0411_Gen directory. The index is as follows: http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/0411_Gen.html -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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

Delayed contributions for the SG16 meeting
by OKUBO Sakae 05 Nov '04

05 Nov '04

Dear SG16 experts, At 08:17 +0200 04/11/05, Tsahi Levent-Levi wrote: >3 contributions from RADVISION At 01:55 -0500 04/11/05, Albrecht.Schwarz(a)alcatel.de wrote: >I've uploaded yesterday 12 Delayed Contributions to ITU FTP drop box. >[...]=> I've just uploaded them in the incoming directory of our >avc-site, too. At 06:33 -0700 04/11/05, Robert R. Gilman wrote: >I have submitted the attached document for this month's meeting. >Martin Euchner has agreed to represent the document. They have been placed at the avc-site: http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/0411_Gen.html -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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

Alcatel contributions to H.248; Re: Documents for the coming meeting in
by Albrecht.Schwarz＠alcatel.de 05 Nov '04

05 Nov '04

Prof Okubo, I've uploaded yesterday 12 Delayed Contributions to ITU FTP drop box. >PS If you have already submitted your documents to ITU-TSB, please >send them to me. I will make them available at the avc-site to >facilitate advance review by the experts. => I've just uploaded them in the incoming directory of our avc-site, too. Best Regards Albrecht OKUBO Sakae <okubo(a)mxz.mesh. To: itu-sg16(a)external.cisco.com ne.jp> cc: Sent by: Subject: Documents for the coming meeting in Geneva owner-tsg16qf@it u.int 05.11.2004 03:57 Please respond to OKUBO Sakae Dear SG16 experts, The following delayed contributions have been placed at the avc-site for your advance review: France Telecom: Location Number for H.323 http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/FT-location_number.… Waseda University: Phase synchronization of video sources http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/Waseda-video_phase_… PS If you have already submitted your documents to ITU-TSB, please send them to me. I will make them available at the avc-site to facilitate advance review by the experts. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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 for the coming meeting in Geneva
by OKUBO Sakae 04 Nov '04

04 Nov '04

Dear SG16 experts, The following delayed contributions have been placed at the avc-site for your advance review: France Telecom: Location Number for H.323 http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/FT-location_number.… Waseda University: Phase synchronization of video sources http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/Waseda-video_phase_… PS If you have already submitted your documents to ITU-TSB, please send them to me. I will make them available at the avc-site to facilitate advance review by the experts. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering 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

Clarification needed - H245 Specification
by Venkata Nanduri 29 Oct '04

29 Oct '04

Hi, I want a clarification about the H245 Annex I defined for AMR codec: What is the parameter "bitRate" defined for? Is it defined for AMR mode change out-of-band? I want to know how the AMR mode changes can be performed out-of-band using H245? For example, assume that we are having a voice call with 12.2kbps and during the call, how can we change it to 7.4kbps using H245? Please let me know at the earliest... Thanks Venkata

1 0

RE: Clarification needed about AMR codec support
by Horvath Ernst 19 Oct '04

19 Oct '04

Venkata, they could be added as optional parameters to the existing defintions for AMR in H.245 Annex I. AMR is defined as a generic capability, which is extensible. Just make sure that the additional parameters use new identifiers. There should also be some text describing the meaning and usage of the new parameters, and if applicable, their relationship with existing parameters. This would require sending a delayed contribution to the next SG16 meeting (note the deadline - 4 November 2004 - and the procedural aspects - Paul Jones may be able to advice you). If accepted, the changes could still be edited into the draft for H.245 version 11. Ernst -----Original Message----- From: Venkata Nanduri [mailto:vnanduri@cisco.com] Sent: Montag, 18. Oktober 2004 19:18 To: Horvath Ernst Cc: paulej(a)cisco.com; itu-sg16(a)external.cisco.com; vdukki(a)cisco.com Subject: RE: Clarification needed about AMR codec support Hi, If that is the case, how those parameters can be negotiated using H245? Any information in this regard is highly appreciated... Similar parameters for SIP are defined in RFC3267, Section 8.1. Thanks Venkata At 10:01 AM 10/18/2004 -0400, Horvath Ernst wrote: Venkata, D-284 was a contribution to the October-2002 meeting of SG16, but Question 3/16 did not accept the proposed text because of conflicts with the existing AMR definitions in H.245. The editor of D-284 was invited to bring a revised proposal to the next meeting, which seemingly did not happen. That's the reason why the parameters proposed in D-284 never became a part of H.245. Hope this solves your doubts. Ernst -----Original Message----- From: Venkata Nanduri [ mailto:vnanduri@cisco.com <mailto:vnanduri@cisco.com> ] Sent: Donnerstag, 14. Oktober 2004 23:41 To: itu-sg16(a)external.cisco.com Cc: paulej(a)cisco.com Subject: Clarification needed about AMR codec support Hi, This email is regarding a clarification needed about a document submitted to SG16(SG 16 - Delayed contribution 284). In the Document titled "Update on AMR speech codec support for H.245", Table X.4 a parameter "octetAlign" is mentioned. But the same is missing from the latest H245 formal specification. As per the document(Delayed contribution 284), "octetAlign" parameter can be used to specify whether the bandwidth efficient or Octet aligned mode of operation is used. Since, In the formal spec, this parameter is missing, how should we negotiate whether we want to use Bandwidth efficient or Octet aligned operation. I also see other parameters(modeSet, ModeChangePeriod, ModeChangeNeighbour, Crc, robustSorting and interleaving) mentioned in your document, but are missing from the formal spec. Any information about how to negotiate those parameters? Thanks Venkata

1 0

RE: Clarification needed about AMR codec support
by Venkata Nanduri 18 Oct '04

18 Oct '04

Hi, If that is the case, how those parameters can be negotiated using H245? Any information in this regard is highly appreciated... Similar parameters for SIP are defined in RFC3267, Section 8.1. Thanks Venkata At 10:01 AM 10/18/2004 -0400, Horvath Ernst wrote: >Venkata, > >D-284 was a contribution to the October-2002 meeting of SG16, but Question >3/16 did not accept the proposed text because of conflicts with the >existing AMR definitions in H.245. The editor of D-284 was invited to >bring a revised proposal to the next meeting, which seemingly did not >happen. That's the reason why the parameters proposed in D-284 never >became a part of H.245. > >Hope this solves your doubts. > >Ernst >-----Original Message----- >From: Venkata Nanduri [mailto:vnanduri@cisco.com] >Sent: Donnerstag, 14. Oktober 2004 23:41 >To: itu-sg16(a)external.cisco.com >Cc: paulej(a)cisco.com >Subject: Clarification needed about AMR codec support > >Hi, > >This email is regarding a clarification needed about a document submitted >to SG16(SG 16 - Delayed contribution 284). > >In the Document titled "Update on AMR speech codec support for H.245", >Table X.4 a parameter "octetAlign" >is mentioned. But the same is missing from the latest H245 formal >specification. > >As per the document(Delayed contribution 284), "octetAlign" parameter can >be used to specify >whether the bandwidth efficient or Octet aligned mode of operation is used. > >Since, In the formal spec, this parameter is missing, how should we >negotiate whether >we want to use Bandwidth efficient or Octet aligned operation. > >I also see other parameters(modeSet, ModeChangePeriod, >ModeChangeNeighbour, Crc, robustSorting and interleaving) >mentioned in your document, but are missing from the formal spec. > >Any information about how to negotiate those parameters? > >Thanks >Venkata

1 0

Question on T.38 bandwidth
by faisal.siyavudeen＠cisco.com 18 Oct '04

18 Oct '04

Hi All, H.323 Annex D (D.6) <quote> When TCP is used for T.38 fax transmission, maxBitRate in the ARQ/BRQ does not include the fax data rate, and if a voice link is switched off when the fax session starts, a BRQ shall be used to indicate to the Gatekeeper that the bandwidth has changed. When UDP is used for T.38 fax transmission, maxBitRate in the ARQ/BRQ does include the bit rate needed for the fax session. The endpoint (terminal, gateway) shall send BRQs to the Gatekeeper as bandwidth needs change during the call. </quote> Is there any specific reason why we do not include the fax data rate in the requested bandwidth for TCP? If TCP is the transport protocol, what will be the bandwidth value that is requested in ARQ/BRQ? rgds Faisal

1 0