- sg16-avd - lists.packetizer.com

Re: Request AVD number
by OKUBO Sakae 15 Jun '02

15 Jun '02

Dear Paul, At 17:39 -0400 02/06/15, Paul E. Jones wrote: >Could you please allocate an AVD number for H.460.6? It has been allocated as follows: AVD-2249 2 Draft H.460.6 Extended Fast Connect Feature Editor (R Gilman) Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: Document number request for Bruges Rapporteur's meeting
by OKUBO Sakae 15 Jun '02

15 Jun '02

Dear Mr. Boyle, At 14:11 -0400 02/06/14, Kevin Boyle wrote: >Please issue numbers for the following two documents, which I will publish >Monday to the pictel site: AVD numbers have been allocated as follows: AVD-2247 3 Updated Draft H.248.16, "Enhanced Digit Collection Packages and Procedures" Editor (K. Boyle II) AVD-2248 3 Considerations for discussion of, and initial proposal for, update of ServiceChange procedures for H.248 Nortel Networks (USA) Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

AVD-2245
by Miner Gleason 14 Jun '02

14 Jun '02

Hello OKUBO san, I have uploaded the file AVD-2245.zip to the Incoming directory on the pictel FTP server. Please move these to the Bruges directory. This zip file contains two versions of the document. The version with name ending in "-ncm" has the change marks removed so it is readable. The version with name ending in "-cm" contains all the change marks, for reference. Thank you! -- best regards, miner --------------------------------------+------------------------ Miner Gleason, Software Engineer | | | mgleason(a)cisco.com | :|: :|: 7025 Kit Creek Road, P.O. Box 14987 | :|||||: :|||||: Research Triangle Park, NC 27709-4987 | .:|||||||:.:|||||||:. 919-392-8752 fax: 919-392-7065 | c i s c o S y s t e m s

1 0

AVD-2195: H.248 Overload Control Package
by Martin J Whitehead 14 Jun '02

14 Jun '02

Dear Mr Okubo I have uploaded AVD-2195 for the Bruges meeting to the incoming directory of the PictureTel ftp site. Please can you upload it to the Bruges directory? Regards, Martin Whitehead British Telecommunications

1 0

AVD-2202, AVD-2203 and AVD-2204
by YOSHIKAWA Tomoyuki 14 Jun '02

14 Jun '02

Dear Mr. Okubo, Dear Experts, I uploaded AVD-2202, AVD-2203 and AVD-2204 to Incoming directory of PictureTel's FTP site for the Bruges meeting. Please upload these documents to the 0206_Bru directory. Sincerely yours, ------------------------------------------------------ YOSHIKAWA Tomoyuki NTT Network Service Systems Laboratories 1-6 Nakase Mihama-ku Chiba-shi, Chiba 261-0023 Japan TEL +81-43-211-3210 FAX +81-43-211-8910 E-Mail yoshikawa.tomoyuki(a)nslab.ntt.co.jp ------------------------------------------------------

1 0

Re: AVD Number request
by OKUBO Sakae 14 Jun '02

14 Jun '02

Dear Mr. Anderson, Dear Mr. Gleason, Your contributions and mine have been registered as follows: AVD-2244 3 H.248 Implementors Guide Draft Editor (T Anderson) AVD-2245 2 H.225.0 Annex G Version 2 Editor (M Gleason) AVD-2246 2, 4, 5 Comments on the use of Instant Messaging and Presence in H.323 systems Waseda University Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

AVC-2199 and AVC-2200
by Sasha Ruditsky 13 Jun '02

13 Jun '02

Dear Mr Okubo I have uploaded AVD-2199 and AVD-2200 for the Bruges meeting to the incoming directory of the PictureTel ftp site. Please upload these documents to the Bruges directory Note: AVD-2199 has changed/updated title. Thanks. Sasha Ruditsky RADVISION

1 0

Re: Request for AVD Numbers
by Miner Gleason 13 Jun '02

13 Jun '02

Hello Okubo san, Can you please assign an AVD number for the following document: H.225.0 AnnexG Version 2 I will seek to have this approved in the fall, but would like to publish the latest draft now. Thanks! -- best regards, miner --------------------------------------+------------------------ Miner Gleason, Software Engineer | | | mgleason(a)cisco.com | :|: :|: 7025 Kit Creek Road, P.O. Box 14987 | :|||||: :|||||: Research Triangle Park, NC 27709-4987 | .:|||||||:.:|||||||:. 919-392-8752 fax: 919-392-7065 | c i s c o S y s t e m s

1 0

Re: Request for Document Numbers
by OKUBO Sakae 13 Jun '02

13 Jun '02

Dear Mr. Groves, Dear Mr. Modahala, Dear Mr. Euchner, Your contributions have been registered as follows: AVD-2230 2, 3 V.MoIP Draft text Editor (K Chu) AVD-2231 3 Alternate Line Test Packages Draft LM Ericsson AVD-2232 3 Updated Profile Package Draft Editor (C Groves) AVD-2233 3 Packages Supplement Draft Editor (C Groves) AVD-2234 3 Extended H.248.12 Packages LM Ericsson AVD-2235 3 Conventions for use of the Local and Remote Descriptors for H.223 LM Ericsson AVD-2236 2 Addition of Hop count field for call signaling loop prevention Cisco AVD-2237 2 Signaling of Translated Source Number for Primary and Alternate Endpoints from the Gatekeeper Cisco AVD-2238 2 SourceEndpointInfo Signaling in Location Request (LRQ) message Cisco AVD-2239 2 Registration of Carrier Identifier Code, Trunk groups and associated Address Patterns to the Gatekeeper Cisco AVD-2240 2 Signaling of Carrier Identifier Code for call routing Cisco AVD-2241 2 Signaling of a list of via Carrier Identifiers for call traversal through each intermediate gateways Cisco AVD-2242 2 Use of Q.850 Cause Code values in Admission Reject (ARJ) of calls Cisco AVD-2243 G, 2, 3 Considerations for discussion on fast start-based security capability negotiation Siemens AG Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Request AVD Numbers
by Logan Modahala 13 Jun '02

13 Jun '02

OKUBO San, Please assign AVD numbers for the following contributions. Source of all these contributions are Cisco Systems, Inc. 1. Addition Hop count field for call signaling loop prevention. 2. Signaling of Translated Source Number for Primary and Alternate Endpoints from the Gatekeeper 3. SourceEndpointInfo Signaling in Location Request (LRQ) message 4. Registration of Carrier Identifier Code, Trunk groups and associated Address Patterns to the Gatekeeper. 5. Signaling of Carrier Identifier Code for call routing 6. Signaling of a list of via Carrier Identifiers for call traversal through each intermediate gateways. 7. Use of Q.850 Cause Code values in Admission Reject (ARJ) of calls. Thanks. - Logan

1 0

Re: AVD Number request
by OKUBO Sakae 12 Jun '02

12 Jun '02

Dear Mr. Chu, At 16:05 -0700 02/06/12, Keith Chu wrote: >please can you assign an AVD contribution number for the following document. > >V.MoIP Draft text - For information of Q2 and Q3/16. > >Source: Editor(V.MoIP) AVD-2230 has been allocated to your draft Recommendation. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: SG16, Bruges meeting, doc registration
by OKUBO Sakae 12 Jun '02

12 Jun '02

Dear Mr. Pierce, Dear Mr. Jones, Dear Mr. Euchner, Your documents have been registered as AVD-2211 through AVD-2224 as attached. Please note that this list is on the ftp site in html form: http://standard.pictel.com/ftp/avc-site/0206_Bru/0206_Bru.html PS to Mr. Euchner, please use TD-05 for QG agenda and TD-12 for QG report. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 ********************************************************* Document List for the Bruges Joint Q.D, F, G, 2, 3, 4, 5 Rapporteurs $B!G (B Meeting (24-28 June 2002) AVD-number Questions Title Source AVD-2175 D, 2, 3, 4 PROPOSED NEW QUESTION ON "Syntax language for the support of PSTN/ISDN services within IP session control protocols" SG11 AVD-2176 G Liaison Statement on Multimodality and Multimediality - Ref: A morphological model for multi-sensory technologies and coherence in security SG17 AVD-2177 G, ets Response to Liaison Statement to ITU-T Study Groups on Telecommunication Reliability and Security SG17 AVD-2178 ets Response to Liaison Statement to draft new Question Q.ets/16 on Emergency Telecommunications Service (ETS) SG17 AVD-2179 G Liaison on the Compendia of Communication Systems Security SG17 AVD-2180 All Liaison statement on the User Requirements Notation (URN) SG17 AVD-2181 2, 3 Liaison Statement to Working Parties 6E, 6S and 8A , Joint Task Group 1-6-8-9, and ITU-T Study Groups 9, 13 and 16 on the Sixth revision of the working document for diagrammatic interrelations of Recommendations for interactive broadcasting services and their summaries ITU-R Working Party 6M AVD-2182 F Consent of Draft New Recommendation M.2301 (ex-M.23ip) - PERFORMANCE OBJECTIVES AND PROCEDURES FOR provisioning AND MAINTENANCE OF ip-based networks Working Party 1/4 (Designations, Performance and Test Equipment) AVD-2183 3 CLARIFICATIONS TO H.246 ANNEX C SG11 (Q11/11) AVD-2184 All Consent of M.3030, telecommunications Markup Language (tML) Framework SG4 AVD-2185 ets Response to Study Group 16 Liaison on Draft New Question Qets/16 for Emergency Telecommunications Service (ETS) SG4 AVD-2186 ets Response to SG16 Liaison on International Emergency Services SG4 AVD-2187 F Response to SG 16 on Use of the CORBA in the TMN WP 4/4, Geneva, 8 - 19 April 2002 AVD-2188 All SG 4 Report and Request in its role as Lead SG on TMN SG4 (Geneva, 8 - 19 April 2002) AVD-2189 2, 3, F Progress of the discussion on generic end-to-end QoS service requirements SG11 AVD-2190 D, ets International Emergency Services SG11 AVD-2191 3 Clarification on Automatic Level Control vs. Gain Control SG15 AVD-2192 2, 3 Channel multiplexing protocol for IP-CME application - G.769/Y.1242 SG15 AVD-2193 D, F, 2, 3, 4, 5 Transport of IPv6 Jumbo Frames SG15 AVD-2194 All New versions of the Access Network Transport (ANT) Standardization Plan and Work Plan SG15 AVD-2195 3 Latest revision of Draft H.248.11 "Media Gateway Overload Control Package" Editor (M Whitehead) AVD-2196 F, 2 Draft Recommendation E.QSC "Signaling of Proposed QoS Service Classes for IP-, ATM-, and ATM-Based Multiservice Networks" SG2 AVD-2197 All Liaison Statement on Terrestrial Wireless Interactive Multimedia Applications ITU-R JTG 1-6-8-9 AVD-2198 2 SCTP as a Transport for H.323 RADVISION AVD-2199 2 LDAP schema definitions for H.323 RADVISION AVD-2200 2 Additions to Q.931 timers usage in H.225.0 RADVISION AVD-2201 2 Draft H.460.4 Call Priority Designation for H.323 Calls Editor (G Thom) AVD-2202 2 Technical corrections relating to progress indicator in Recommendation H.225.0 NTT AVD-2203 3 Corrections relating to mapping of cause value in H.246 Annex C NTT AVD-2204 3 Corrections of Recommendation H.246 Annex C regarding Bearer Capability and Handling of fallback information in backward message NTT AVD-2205 2 Clarifications and minor enhancements to H.323/Annex R specification Cisco AVD-2206 2 Clarification to the H.323 Annex E protocol Cisco AVD-2207 2 H.323 Annex O: Use of Internet Protocols with H.323 Systems Editor (O Levin) AVD-2208 2 H.323 Series Implementer's Guide Editor (V Bhargava) AVD-2209 2 (contribution to restructure the H.225.0 document) Cisco AVD-2210 2 Proposal to add the Circuit Status Map to H.225 messages Cisco AVD-2211 2 Comments on draft for H.460.4, Call Priority Designation for H.323 calls Artel AVD-2212 2 Proposal to Add Digit Maps to H.323 Cisco AVD-2213 2, 3 H.245 Additions for MoIP H.323 Annex P Editor (P Jones) AVD-2214 2, 3 Draft Annex P/H.323 Editor (P Jones) AVD-2215 2 Draft H.460.Requery Editor (P Jones) AVD-2216 All FINAL REPORT of MULTIMEDIA CONVERGENCE Workshop(IP Cablecom / MEDIACOM 2004 / Interactivity in Multimedia), 12-15 March 2002, Geneva Q.G/16 Rapporteur (M Euchner) AVD-2217 G, 2, 3 Out-of band DTMF Encryption Siemens AG AVD-2218 G, 2, 3 Enhanced OFB mode in H.235v3 Editor (M Euchner) AVD-2219 G Improved Key Transport in H.235V3 Editor (M Euchner) AVD-2220 G, 2, 3 Secure Fast Start Clarifications in H.235 V3 Editor (M Euchner) AVD-2221 G Improved Diffie-Hellman Signaling Editor (M Euchner) AVD-2222 G Draft H.235 VERSION 3 - SECURITY AND ENCRYPTION FOR H-SERIES (H.323 AND OTHER H.245-BASED) MULTIMEDIA TERMINALS Editor (M Euchner) AVD-2223 G, 2, 3 Considerations for SRTP integration into H.235v3 Siemens AG AVD-2224 G, 2, 3 New draft H.235 Annex G "Secure Real Time Transport Protocol Security Profile (SRTP)" Siemens AG AVD-2225 All Revision of ITU-T Recommendation G.114 SG12 AVD-2226 C, F, ets Response to liaison requesting information on QoS thresholds for Emergency Telecommunications Service degradation SG12 AVD-2227 C, ets REPLY TO THE LIAISON STATEMENT ON DRAFT NEW QUESTION Q.ETS/16 ON EMERGENCY TELECOMMUNICATIONS SERVICE SG12 AVD-2228 D, F, 2, 3, 4, 5 LIAISON STATEMENT ON CALL FOR MODEL SUBMISSION FOR THE ASSESSMENT OF VOICE TRANSMISSION QUALITY FROM PROTOCOL ANALYSIS INFORMATION IN IP NETWORKS SG12 AVD-2229 D, F, 2, 3, 4, 5 Cooperation on measurement/monitoring of end-to-end Quality SG12 --------------

1 0

RE: Upcoming Rapporteur's meeting
by Laurent Vreck 12 Jun '02

12 Jun '02

Paul, According to my latest version of the TIPHON participant list there should still be some room left in the Novotel, which means that some of your delegates could stay there. Yet I would prefer to wait for an answer from Joseph-Philippe: he is in much closer contact with the hotels than I am, and he could tell you whether the Scandik block-booking has already been fully used by ITU-T people or if it is an error from one of the Scandik staff who would have tried to reserve a room for one of your people without using one of the pre-booked rooms... Laurent -----Original Message----- From: Paul E. Jones [mailto:paulej@packetizer.com] Sent: 11 June 2002 23:23 To: ITU-SG16(a)echo.jf.INTEL.COM Cc: Laurent Vreck; Joseph-Philippe. Hogenhuis (E-mail); Folts, Harold Subject: Upcoming Rapporteur's meeting Dear Experts, I just received word that the Scandic Hotel is fully booked now. Apparently, there are a few more people planning to attend who I do not have on my list, as I have about 30 folks listed and we were supposed to have about 40 rooms. Perhaps some are attending the Qets/16 meeting. In any case, there may still be rooms available at the hotel reserved for TIPHON attendees. If there is anybody planning to attend the meeting and who has not yet made hotel reservations, please contact me as soon as possible. Thanks, Paul

1 0

Upcoming Rapporteur's meeting
by Paul E. Jones 11 Jun '02

11 Jun '02

Dear Experts, I just received word that the Scandic Hotel is fully booked now. Apparently, there are a few more people planning to attend who I do not have on my list, as I have about 30 folks listed and we were supposed to have about 40 rooms. Perhaps some are attending the Qets/16 meeting. In any case, there may still be rooms available at the hotel reserved for TIPHON attendees. If there is anybody planning to attend the meeting and who has not yet made hotel reservations, please contact me as soon as possible. Thanks, Paul

1 0

Fwd: Re: Request for AVD number
by OKUBO Sakae 10 Jun '02

10 Jun '02

Dear Mr. Fourie, At 21:15 -0700 02/06/09, Louis Fourie wrote: > Please allocate an AVD number for the contribution: >Proposal to add the Circuit Status Map to H.225messages AVD-2110 has been allocated to your contribution. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Fwd: Re: Req for 2 AVD Numbers
by OKUBO Sakae 07 Jun '02

07 Jun '02

Dear Mr. Bhargava, At 22:43 -0400 02/06/06, Vivek Bhargava wrote: >Could you please allocate two AVD numbers for me? One for H.323 Series >Implementer's Guide and another for a contribution to restructure the >H.225.0 document. AVD-2208 and 2209 have been allocated to your two documents. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: Request for an AVD number
by OKUBO Sakae 06 Jun '02

06 Jun '02

Dear Orit, At 17:01 -0400 02/06/06, Orit Levin wrote: >Could you, please, allocate an AVD number to the document: >"H.323 Annex O: Use of Internet Protocols with H.323 Systems" by Editor. AVD-2207 has been allocated to your draft Recommendation. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: Document number
by OKUBO Sakae 05 Jun '02

05 Jun '02

Dear Surya Gogineni and Vivek Kakkar, Thank you for your document registration. AVD numbers have been allocated as follows: AVD-2205 2 Clarifications and minor enhancements to H.323/Annex R specification Cisco AVD-2206 2 Clarification to the H.323 Annex E protocol Cisco Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: Contributions to the Bruges meeting
by Ogishi Hisataka 05 Jun '02

05 Jun '02

Dear Mr. Okubo, Thank you very much. I will upload these collections and announce it later. Best regards, OGISHI Hisataka, NTT, Japan > -----Original Message----- > From: Mailing list for parties associated with ITU-T Study Group 16 > [mailto:ITU-SG16@echo.jf.INTEL.COM] On Behalf Of OKUBO Sakae > Sent: Wednesday, June 05, 2002 5:41 PM > To: ITU-SG16(a)echo.jf.INTEL.COM > Subject: Contributions to the Bruges meeting > > Dear Mr. Ogishi, > > In response to your request, the following AVD numbers have been allocated > to your three contributions: > > AVD-2202 > 2 > Technical corrections relating to progress indicator in Recommendation H.225.0 > NTT > > AVD-2203 > 3 > Corrections relating to mapping of cause value in H.246 Annex C > NTT > > AVD-2204 > 3 > Corrections of Recommendation H.246 Annex C regarding Bearer Capability and > Handling of fallback information in backward message > NTT > > Best regards, > > OKUBO Sakae > ********************************************************* > Global Information and Telecommunication Institute (GITI) > Waseda University > 29-7 Waseda University Bldg. > 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo > 169-0051 Japan > e-mail: okubo(a)giti.waseda.ac.jp > Tel: +81 3 3204 8194 > Fax: +81 3 5286 3832 > *********************************************************

1 0

Contributions to the Bruges meeting
by OKUBO Sakae 05 Jun '02

05 Jun '02

Dear Mr. Ogishi, In response to your request, the following AVD numbers have been allocated to your three contributions: AVD-2202 2 Technical corrections relating to progress indicator in Recommendation H.225.0 NTT AVD-2203 3 Corrections relating to mapping of cause value in H.246 Annex C NTT AVD-2204 3 Corrections of Recommendation H.246 Annex C regarding Bearer Capability and Handling of fallback information in backward message NTT Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: AVD numbers allocation for Bruges meeting.
by OKUBO Sakae 04 Jun '02

04 Jun '02

Dear Gary, At 09:32 -0400 02/06/04, Gary Thom wrote: >please assign a document number for draft H.460.4 Call Priority >Designation for h.323 Calls AVD-2201 has been allocated to your draft Recommendation. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: AVD numbers allocation for Bruges meeting.
by OKUBO Sakae 03 Jun '02

03 Jun '02

Dear Sasha, Thank you for your contributions, to which AVD-2198, 2199, 2200 have been allocated. At 16:07 -0400 02/06/03, Sasha Ruditsky wrote: >I would like to ask you to allocate AVD numbersfor following documents >for upcoming SG-16 meeting in Bruges: AVD-2198 2 SCTP as a Transport for H.323 RADVISION AVD-2199 2 LDAP schema definitions for H.323 RADVISION AVD-2200 2 Additions to Q.931 timers usage in H.225.0 RADVISION Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Re: document in incoming
by OKUBO Sakae 30 May '02

30 May '02

Dear Mr. Anderson, At 13:32 -0400 02/05/30, Terry L Anderson wrote: >I have uploaded >avc-site/Incoming/2-019r1_h248IG_before_Corrigendum.zip >a TD from the 0202 meeting, that some have expressed interest in. Could >you move it to the 0202_Gen directory? Thank you. Done as requested. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0

Qets/16 Meeting
by Folts, Harold 26 May '02

26 May '02

Greetings, During the meeting of the SG16 WP2/16 Experts meeting in Bruges, Belgium June 24-28, 2002, Swiss Telecom will be hosting a meeting on Qest/16 on June 25 at the Scandic Hotel. Attached is the information about the hotel and reservation request form. The agenda is as follows: Opening @ 9:30 a.m. Review and approval of agenda Review of liaison responses received Coffee break at 11:00 Continue discussions Lunch h @ 12:30 Resume @ 2:00 Develop revisions to Draft Question as necessary Afternoon Break @ 3 :30 Review other issues including applicability of Metadata Game plan for future work. Adjournment @ 5:30 This is a provisional agenda and is subject to further revision and refinement Please let me know directly if you plan to attend this session. I look forward to your\r support and participation in this important endeavour. Many thanks. Best regards, Hal Folts Rapporteur, proposed Qest/16 <<Qest Res.doc>> <<Folts, Hal.vcf>>

1 0

Re: H.450.1 ASN.1 interoperability issue
by frank.derks＠PHILIPS.COM 21 May '02

21 May '02

Hi, I recall having a discussion on this topic with Ernst Horvath when this clarification text was proposed. I thoroughly checked the ASN.1 back then and based on that I must add that both Sasha and Ernst are right. Again, in the Invoke, the invokeId is encoded as a constrained integer. In the ReturnResult and ReturnError, the invokeId is encoded as "a regular" integer. I do not see any concerns for interoperability, unless it is your intention to copy the encoded invokeId from the Invoke straight to the ReturnResult/ReturnError. There is no inconsistency, between the different APDUs, there just happens to be a different specification for the invokeId in the different APDUs. This specification is identical to the one used in X.880, on which H.450.1 is based. I don't quite understand what you mean with the "two ASN.1 versions" in the "does not gel in" section of your text. Coul you clarify this? Regards, Frank Hi I just want to rewrite the same to be sure we are in sync. 6.6.1.3 of the V4 implementors guide does not CHANGE/CONTRADICT ASN.1 of H.450.1 it EXPLAINS how to encode values correctly according to ASN.1 definitions of H.450.1 And this correct encoding is: (as written in 6.6.1.3) invoke.invokeId shall be encoded as INTEGER(0..65535) returnResult.invokeId and returnError.invokeId shall be encoded as INTEGER Sasha -----Original Message----- From: Horvath Ernst [mailto:ernst.horvath@SIEMENS.COM] Sent: Monday, May 13, 2002 8:49 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: H.450.1 ASN.1 interoperability issue Mark, there was no intention to change any ASN.1 definition in H.450.1. The note was added just to make implementers aware that the InvokeID is encoded differently in the "invoke" APDU and in the "returnResult/returnError" APDUs: in the first case it is constrained by InvokeIdSet, in the second case it is not constrained. This is not an incosistency, just a consequence of the way Packed Encoding Rules were designed. Please also note that "InvokeIdSet" is used in two different meanings: in table 4 it is the name of a parameter of the parameterized structure ROS (i.e. a placeholder), whereas in table 3 it is an "actual" value-set of integers. The brackets in the new note (InvokeIdSet = 0..65535) are not an ASN.1 definition, just an indication what the effective constraint is, namely 0..65535. Table 3 is still the (unchanged) formal definition of the actual "InvokeIdSet". Ernst Horvath Siemens AG > -----Ursprüngliche Nachricht----- > Von: Mark Brown [mailto:Mark.Brown@ED.ACULAB.COM] > Gesendet am: Freitag, 10. Mai 2002 17:29 > An: ITU-SG16(a)echo.jf.INTEL.COM > Betreff: H.450.1 ASN.1 interoperability issue > > We've been experiencing some fairly serious interoperability problems > with some systems due to confusion over what exactly the ASN.1 for > H.450.1 is and were hoping someone could clarify things for us. The > problem stems from section 6.6.1.3 of the V4 implementors guide which > adds a note below table 4: > > In the Invoke APDU, the invokeID is an INTEGER constrained by a > PER-visible constraint (InvokeIdSet = 0..65535) and is therefore > encoded as a *constrained* INTEGER (16 bits, no length field). In > the ReturnResult and ReturnError APDUs, however, the invokeID is > encoded as an *unconstrained* integer (with explicit length field) > because the applicable constraint... is not PER-visible. > > However, in H.450.1 table 3 (on page 8) defines InvokeIdSet to be: > > InvokeIdSet INTEGER ::= {InvokeIds,...} > InvokeIDs ::= INTEGER (0..65535) > > which does not gel with the text in the IG and causes interoperability > issues since the two versions of the ASN.1 for InvokeIdSet are not > encoded identically. This text appears to be unchanged from the > prepublished edition on Packetizer. > > Our understanding of the text added in the IG is that the > intent was to > emphasise that the encoding of the invokeID is not consistent between > the various APDUs and that the no change to the ASN.1 was intended. > This is particularly the case since the IG doesn't modify table 3 as > would be expected if it were correcting the ASN.1 there. Others read > things differently and are using the definition of > InvokeIdSet given in > the IG. > > What is the intention here? If the intention is to redefine the ASN.1 > then some clarification as to why this was done would be very much > appreciated. >

2 1