Dear Q.12-14/16 experts,
Attached please find an update of the list of contributions for the Berlin meeting.
Please be reminded that the deadline of contribution submission is as follows:
/// Registration of the document: by 23 July (Friday) /// /// Distribution of the document: by 26 July (Monday) ///
Please also be reminded of the following note we confirmed at the Torino meeting in November 1998 (see APC-1485):
"The meeting notes that contributors are requested to upload the documents on time, otherwise their proposals can legitimately be rejected on the ground that the group members lack reviewing time."
Best regards,
Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo@giti.or.jp ***********************************************************
Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 L M Ericsson First draft of a H.246 Annex for text conversation and text telephony 1564 L M Ericsson H.224 Modified for text conversation 1565 (P Jones) T.35 (1999) country codes 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) 1567 L M Ericsson Generic Service ControlTransport 1568 Lucent and H.245 Generic Capabilities Definition and AT&T H.225 Packetization Specification for the North American Cellular/PCS TDMA Vocoders (ACELP and US1) 1569 BT and Tech- Editorial Clarifications to H.323 and the Know-Ware Implementer's Guide 1570 BT and Tech- Clarifications on Third-Party Pause Know-Ware 1571 Rapporteur for Q.12/16 (S Okubo) Status of Draft Amendment 7 to H.222.0|ISO/IEC 13818-1 -- Carriage of ISO/IEC 14496 (MPEG-4) content over H.222.0|ISO/IEC 13818-1 (MPEG-2) System streams 1572 Editor (K Sakai) Draft Implementor's Guide for H.321 V2 1573 Editor (S Okubo) Draft Implementor's Guide for H.310 V2 1574 SG16 Correspondence Representative to DAVIC (S Okubo) DAVIC work on TV Anytime and TV Anywhere systems 1575 Rapporteur for Q.19/16 (S Hayashi) H.245 Generic Capability Definition and H.225.0 Packetization Specification for G.729 1576 Japan Guideline for assigning the T.35 terminal provider codes in Japan 1577 Oki et al Proposed modifications to resolve the inconsistent ASN.1 syntaxes between T.38 Annex B and H.245 1578 Oki et al Proposed additional liasion to SG8 on T.38 Appnedix II 1579 Hitachi, Ltd. Prototype system of H.262 layered video transmission 1580 Nortel Networks Media Gateway control protocol architecture and requirements ------------------------------------------------------------------------
Folks,
Mr. Kaynam Hedayat has pointed out an error in the Implementers Guide that, in order to correct, will require a text change in the H.323v3 document submitted for decision in September.
The particular error is in section 6.1.4 of the Implementers Guide. It refers to section 8.4.3.1 A2d) of H.323. The following text currently exists in the Implementers Guide and was approved in September:
``The recipient of this "routeCallToMC" Facility message should consider the previous exchange completed and send a new SETUP message to the MC(U) address with the chosen conference it wishes to join.''
However, the text shown directly above this change is actually text from section 8.4.3.4 rather than section 8.4.3.1. Additionally, the "routeCallToMC" should be "conferenceListChoice". I would like to propose that we change the paragraph in the Implementers Guide to the following text:
``Upon recipient of this "conferenceListChoice" Facility message, Endpoint 1 may join a conference from the list of conferences by sending a new Setup message to the MC(U) on the Call Signaling Channel which contains the selected CID and which has conferenceGoal = join. If Endpoint 1 chooses not to join any of the listed conferences, it shall send a Release Complete message to the MC(U)."
This text would appear in section 8.4.3.1 A2d) and section 8.4.3.4 (following the second paragraph).
Please let me know if there are any objections to this proposed change.
Thanks, Paul
Paul,
I've got a small editorial comment: replace ``Upon recipient of this "conferenceListChoice" Facility message'' by ``Upon receipt ...''
John
"Paul E. Jones" wrote:
Folks,
Mr. Kaynam Hedayat has pointed out an error in the Implementers Guide that, in order to correct, will require a text change in the H.323v3 document submitted for decision in September.
The particular error is in section 6.1.4 of the Implementers Guide. It refers to section 8.4.3.1 A2d) of H.323. The following text currently exists in the Implementers Guide and was approved in September:
``The recipient of this "routeCallToMC" Facility message should consider the previous exchange completed and send a new SETUP message to the MC(U) address with the chosen conference it wishes to join.''
However, the text shown directly above this change is actually text from section 8.4.3.4 rather than section 8.4.3.1. Additionally, the "routeCallToMC" should be "conferenceListChoice". I would like to propose that we change the paragraph in the Implementers Guide to the following text:
``Upon recipient of this "conferenceListChoice" Facility message, Endpoint 1 may join a conference from the list of conferences by sending a new Setup message to the MC(U) on the Call Signaling Channel which contains the selected CID and which has conferenceGoal = join. If Endpoint 1 chooses not to join any of the listed conferences, it shall send a Release Complete message to the MC(U)."
This text would appear in section 8.4.3.1 A2d) and section 8.4.3.4 (following the second paragraph).
Please let me know if there are any objections to this proposed change.
Thanks, Paul
-- John Segers email: jsegers@lucent.com Lucent Technologies Room HE 306 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954
participants (3)
-
John Segers -
Paul E. Jones -
Sakae OKUBO