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

APC-1631 uploaded
by Pete Cordell 28 Jul '99

28 Jul '99

APC-1631 has been uploaded to the PictureTel Incoming directory. The title is: "A Package based Extensible Object-Oriented Framework for H.225" Apologies for the delay. Pete ============================================= Pete Cordell pete(a)tech-know-ware.com =============================================

1 0

Attachment to APC-1558
by Sakae OKUBO 28 Jul '99

28 Jul '99

Dear Q.12-14/16 experts, I have found that APC-1558 (reproduction of TD-24/GEN from the Santiago meeting) has an attachment E.mm. This is now available at the ftp site. ftp://standard.pictel.com/avc-site/9908_Ber/APC-1558-att.zip or http://standard.pictel.com/ftp/avc-site/9908_Ber/APC-1558-att.zip 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(a)giti.or.jp ***********************************************************

1 0

List of uploaded APC documents
by Noriko Hosokawa 28 Jul '99

28 Jul '99

Dear Q.12-14/16 experts, Attached please find the list of uploaded contributions as of 15:00 (Tokyo time) Tuesday 27 July. Those documents yet to be uploaded are marked with *. 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(a)giti.or.jp ******************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9908_Ber/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9908_Ber/APC-1???.??? * yet to be uploaded # to be uploaded after the SG11 Rapporteur meeting this week + to be uploaded on Thursday ------------------------------------------------------------------------ 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 Editor Draft H.323 Annex J: Security for H.323 Annex F 1564 L M Ericsson H.224 Modified for text conversation 1565 DataBeam Corporation Usage of Expanded T.35 Country Codes in Recommendations H.225.0,H.245, and H.283 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 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 IETF Megaco Working Group Media Gateway control protocol architecture and requirements 1581 Lucent Technologies and Nortel Networks H.323 v3 and H.225 v3 Support for Improved Alias Registrations 1582 Lucent Technologies H.323 v3 and H.225 v3 Endpoint Registration Clarifications 1583 Siemens AG Error in Coding Bearer Capabilities 1584 Siemens AG Inter-Zone Addressing 1585 Siemens AG Correction of Alias Conflict in H.225.0v3 1586 Siemens AG Identification of Gateway Protocol 1587 Siemens AG Null AliasAddress 1588 SIEMENS Restricted Numbers/Aliases in Supplementary Service APDUs 1589 SIEMENS Work on Supplementary Service Interworking started 1590 SIEMENS Draft H.450.9 "Call Completion Supplementary Services for H.323 1591 AT&T, VocalTec, DataBeam and Alcatel Functional Requirements and Service Classes to Support QOS in H.323 1592 Lucent Technologies Q.SIG Transport in H.323 Systems 1593 PictureTel and Nortel Networks Backward compatibility and clarification text in H.323 Annex C 1594 PictureTel Problem with XRS (Message Not Understood) RAS message 1595 PictureTel Additional information in ARQ for Gateway calls 1596 PictureTel H.245 support for G.722.1 1597 Siemens Feature key management extensions for H.323 SET terminals 1598 VocalTec Communications Ltd Adopting a Pragmatic Approach to IPT-IN InterWorking 1599 VocalTec Clarifications to the fast connect procedure 1600 VocalTec Comments on Transporting DTMF in H.323 1601 VocalTec Changes to H.323 to support operation via basic NAT devices #1602 VocalTec Communications Ltd IN-IPT interworking - feecback from the SG11 Rapporteur #1603 VocalTec Communications Ltd and Marconi Communications Ltd Scope definition of Annex D to H.246 1604 VocalTec Changes to H.248 to assure H.323 GW interoperability *1605 Intel Corporation Proposed Terms of Reference for H.323 Mobility 1606 Cisco Systems Proposal for Transporting User Input via RTP 1607 Cisco Systems Proposal for Enforcing Symmetric Codec Operation with Fast Connect 1608 Tech-Know-Ware and Lucent H.GCP/Megaco Structured Message Encoding Using an ASCII Line Format 1609 Lucent Technologies Support for Q.931 TNS and NSF IEs in H.225.0 *1610 Q.14 Rapporteur Changes to H.248 Proposed by IETF Megaco 1611 RAD Data Communications LTD Proposals for the next version of H.341 MIB 1612 Lucent Technologies,Intel Corporation,FORE Systems Inc.,Teles AG Proposing structured media and bearers for H.248, 1613 Lucent Technologies Proposal for PUT and DELETE commands in H.248, 1614 Lucent Technologies Scripting framework for H.248, 1615 Lucent Technologies H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 1616 LM Ericsson H.GCP and encoding in networks 1617 LM Ericsson Signalling Transport for H.GCP 1618 LM Ericsson Handling of Optional H.GCP commands 1619 LM Ericsson Notification Indicators in H.323 1620 LM Ericsson Signalling Transport in H.323 *1621 LM Ericsson Draft H.246 Annex C *1622 Lucent Technologies Expression of Gateway Call Capacity 1623 Lucent Technologies Need for the Q.931 Disconnect and Release Messages in H.225.0 1624 TAO Some considerations on the new Annex to H.323 for high quality audiovisual communications 1625 Oki Electric Indsutry Editorial errors in H.450.5 and H.450.7 1626 Nortel Networks Tunneling of Q.SIG information in H.225.0 1627 IETF Megaco Working Group R2 Package for MEGACO Protocol 1628 IETF Megaco Working Group Megaco IP Phone Media Gateway +1629 IETF Megaco Working Group Basic Packages For Megaco/H.248 1630 Cisco Systems,Inc. SDP Encoding for H.248. *1631 Tech-Know-Ware and BT A Package based Extensible Object-Oriented Framework for H.225 1632 Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Structured Syntax for H.248 1633 Mitel Proposals for Enhanced Feature Support in H.323 1634 Intel Security tokens for releaseComplete UUIE 1635 Telcordia Technologies Mapping H.245 semantics to SDP 1636 Telcordia Technologies Comparing EBNF and ASN.1 for text encoding *1637 Rapporteur Q13 Protocols for Trunking and Access Gateways *1638 LucentTechnologies Gatekeeper Modification of Destination Addresses *1639 LucentTechnologies Trunk and Line Selection in H.323 Gateways 1640 Nortel Networks Clarification on the use of E.164 numbers *1641 Lucent Interoperabity between H.323 Systems using G.711 and SD/CNG 1642 Alcatel and Nortelnetworks Reference to af-saa-0124.000 specification in H.323.V3 1643 MPEG Liaison Statement from SC 29/WG 11 to ITU-T SG 16 on MPEG-4 Over H.32x Terminals [SC 29/WG 11 N 2887] ---------------------------------------------------------------------------- ----

1 0

APC-1630 ("SDP Encoding for H.248") uploaded/enclosed
by Chip Sharp 28 Jul '99

28 Jul '99

I have uploaded APC-1630 for potential consideration at the upcoming rapporteur's meeting. It is also enclosed below. Warning: This contribution is text encoded. ;-) Chip ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document APC- 1630 | | Study Group 16 | | Q.12-14/16 Rapporteur Meeting 27 August, 1999| | Berlin, 2-6 August 1999 | | | | SOURCE*: Cisco Systems, Inc. | | TITLE : SDP Encoding for H.248 | | PURPOSE: Proposal | | | | _________________________ | | | | | | | | *Contact: Chip Sharp, chsharp(a)cisco.com | ------------------------------------------------------------------ Abstract: The use of SDP encoding has been proposed for H.248. This contribution proposes the following: 1) The SDP encoding that has been proposed since the March compromise should be maintained at least as an option. 2) The encodedparameter should refer to RFC2327 for the SDP encoding. 3) The package names and event names should be text encoded and registered with IANA for extensibility. 4) An IANA considerations section needs to be added to provide guidelines for registering with IANA. Session Description Protocol: --------------------------- The Session Description Protocol (SDP) is described in RFC2327 (ftp://nis.nsf.net/internet/documents/rfc/rfc2327.txt). It is a standards-track protocol in the IETF. Refer to the current edition of the "Internet Official Protocol Standards" (STD 1, ftp://ftp.isi.edu/in-notes/std/std1.txt) for the standardization state and status of this protocol. >From the abstract of RFC2327: "SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation." SDP Proposal: ------------ The encodedDescriptor should maintain the option for SDP encoding. The encodedDescriptor production should be changed to: encodedDescriptor = (SDPToken COMMA *SDPinformation) | (H245Token COMMA quotedOctetString ) | (extensionParameter COMMA quotedOctetString ) Add the following production: SDPinformation = announcement ;Normative: <announcement> is ;defined in Appendix A of RFC2327 In addition, an extension mechanism should be defined. It is recommended that a similar mechanism to that defined in http://search.ietf.org/internet-drafts/draft-huitema-megaco-mgcp-v1- 00.txt be used. Package and Event Proposal: -------------------------- Various Packages are currently being defined for H.248. It is expected that a certain number of packages will be included in the base standard. However, it is also expected that more packages will need to be defined as more applications are defined. This contribution recommends that the package names and event names be text acronyms that are registered with IANA. This will allow new packages and events to be added in an extensible manner. This mechanism is already used for many applications on the Internet. For example, MIME types are registered with IANA. This practice allows extensions to the base capabilities without having to rev the base specification every time a new capability is added. The ITU in general and SG16 in particular already have established precedence in using IANA registration in ITU Recommendations. This is a well-established practice in SG16. All the TCP/UDP ports used in the H.323 series recommendations are registered with IANA. Therefore, there should be no procedural problem with using IANA registration. The following text should be added: In Section 7.2.2.6 Packages, add the following sentence: "Package names, referred to in this document as PackageName, will be registered with IANA." The following changes should be made to the packageName and eventParameterName productions: packageName = NAME ;Normative - The values this production takes are ; registered with IANA as defined in Section ??? eventParameterName = NAME ;Normative - The values this production takes are ; registered with IANA as defined in Section ??? A Section should be added defining the guidelines for registering events and packages with IANA. For example, the following text could be used (taken from SIP): " When registering a new SIP option, the following information MUST be provided: o Name and description of option. The name MAY be of any length, but SHOULD be no more than twenty characters long. The name MUST consist of alphanum (See Figure 3) characters only; o Indication of who has change control over the option (for example, IETF, ISO, ITU-T, other international standardization bodies, a consortium or a particular company or group of companies); o A reference to a further description, if available, for example (in order of preference) an RFC, a published paper, a patent filing, a technical report, documented source code or a computer manual; o Contact information (postal and email address); This procedure has been borrowed from RTSP [4] and the RTP AVP [26]." However, this is not sufficient. Guidelines similar to those defined in RFC2327 should be developed. CONCLUSION ---------- In conclusion: 1) The SDP encoding that has been proposed since the March compromise should be maintained at least as an option. 2) The encodedparameter should refer to RFC2327 for the SDP encoding. 3) The package names and event names should be text encoded and registered with IANA for extensibility. 4) An IANA considerations section needs to be added to provide guidelines for registering with IANA. -------------------------------------------------- Chip Sharp Consulting Engineering Cisco Systems Telco Bio-region Reality - Love it or Leave it. --------------------------------------------------

1 0

H.245v6?
by Paul Long 27 Jul '99

27 Jul '99

H.323v3 references H.225.0v3 and H.245v6, but I cannot find even a draft of H.245v6. Anybody know where it is? Also, why the drastic jump in H.245 versions? Paul Long Smith Micro Software, Inc.

1 0

Documents uploaded
by Kaynam Hedayat 27 Jul '99

27 Jul '99

Dear colleagues, I have uploaded the following documents into the incoming directory: APC-1593: Backward compatibility and clarification text in H.323 Annex C (PictureTel and Nortel) APC-1594: Problem with XRS (Message Not Understood) RAS message (PictureTel) APC-1595: Additional information in ARQ for Gateway calls (PictureTel) APC-1596: H.245 Support for G.722.1 (PictureTel) Regards, Kaynam Hedayat

1 0

APC-1629 -- Basic Packages For H.248
by Tom-PT Taylor 27 Jul '99

27 Jul '99

I have to apologize for late delivery of APC-1629. Editing was going well, but I had to leave for the airport. Due to last-minute distractions I managed to leave my computer behind. I'm afraid I won't be able to upload APC-1629 until Thursday morning. Tom Taylor

1 0

Re: APC-1573
by Sakae OKUBO 27 Jul '99

27 Jul '99

Dear Mr. Euchner, > it appears to me that file APC-1573.zip does not contain the related > contribution APC-1573.doc as one should assume by the file name. The zip > archive rather contains the APC-1572.doc. Thus, I am not able to locate > APC-1573.doc so far. Thank you very much for your advice. APC-1573.zip has been replaced with the file containing APC-1573.doc. 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(a)giti.or.jp ***********************************************************

1 0

APC-1597 uploaded
by Korpi, Markku 27 Jul '99

27 Jul '99

I have uploaded: APC-1597 "Feature key management extensions for H.323 SET terminals" Markku Korpi Siemens Information & Communication Networks 4900 Old Ironsides Dr., Santa Clara, CA 95054-1811, U.S.A. Phone: +1 408 492 7328, Fax: +1 408 492 4666, Mobile +1 408 390 5677 E-mail: markku.korpi(a)icn.siemens.com

1 0

Current list of registered contributions
by Noriko Hosokawa 27 Jul '99

27 Jul '99

Dear Q.12-14/16 experts, Attached please find the list of registered contributions as of 15:00 (Tokyo time) Tuesday 27 July. Those documents yet to be uploaded are marked with *. If you have uploaded your document but it is marked, please accept my apology and re-send it to the /Incoming directory. If you have not yet uploaded your document, please take your prompt action. Your cooperation is requested to make the Berlin meeting productive. 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(a)giti.or.jp ******************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9908_Ber/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9908_Ber/APC-1???.??? * yet to be uploaded # to be uploaded after the SG11 Rapporteur meeting this week ------------------------------------------------------------------------ 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 Editor Draft H.323 Annex J: Security for H.323 Annex F 1564 L M Ericsson H.224 Modified for text conversation 1565 DataBeam Corporation Usage of Expanded T.35 Country Codes in Recommendations H.225.0,H.245, and H.283 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) 1567 L M Ericsson Generic Service ControlTransport 1568 Lucent and AT&T H.245 Generic Capabilities Definition and H.225 Packetization Specification for the North American Cellular/PCS TDMA Vocoders (ACELP and US1) 1569 BT and Tech-Know-Ware Editorial Clarifications to H.323 and the Implementer's Guide 1570 BT and Tech- Know-Ware Clarifications on Third-Party Pause 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 system 1575 Rapporteur for Q.19/16 (S Hayashi) H.245 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 the IETF Megaco Working Group Media Gateway control protocol architecture and requirements 1581 Lucent Technologies and Nortel Networks H.323 v3 and H.225 v3 Support for Improved Alias Registrations 1582 Lucent Technologies H.323 v3 and H.225 v3 Endpoint Registration Clarifications 1583 Siemens AG Error in Coding Bearer Capabilities 1584 Siemens AG Inter-Zone Addressing 1585 Siemens AG Correction of Alias Conflict in H.225.0v3 1586 Siemens AG Identification of Gateway Protocol 1587 Siemens AG Null AliasAddress 1588 SIEMENS Restricted Numbers/Aliases in Supplementary Service APDUs 1589 SIEMENS Work on Supplementary Service Interworking started 1590 SIEMENS Draft H.450.9 "Call Completion Supplementary Services for H.323 1591 AT&T, VocalTec, DataBeam and Alcatel Functional Requirements and Service Classes to Support QOS in H.323 1592 Lucent Technologies Q.SIG Transport in H.323 Systems *1593 PictureTel and Nortel Networks Backward compatibility and clarification text in H.323 Annex C *1594 PictureTel Problem with XRS (Message Not Understood) RAS message *1595 PictureTel Additional information in ARQ for Gateway calls *1596 PictureTel H.245 support for G.722.1 *1597 Siemens Feature key management extensions for H.323 SET terminals 1598 VocalTec Communications Ltd Adopting a Pragmatic Approach to IPT-IN InterWorking 1599 VocalTec Clarifications to the fast connect procedure 1600 VocalTec Comments on Transporting DTMF in H.323 1601 VocalTec Changes to H.323 to support operation via basic NAT devices #1602 VocalTec Communications Ltd IN-IPT interworking - feecback from the SG11 Rapporteur #1603 VocalTec Communications Ltd and Marconi Communications Ltd Scope definition of Annex D to H.246 1604 VocalTec Changes to H.248 to assure H.323 GW interoperability *1605 Intel Corporation Proposed Terms of Reference for H.323 Mobility 1606 Cisco Systems Proposal for Transporting User Input via RTP 1607 Cisco Systems Proposal for Enforcing Symmetric Codec Operation with Fast Connect 1608 Tech-Know-Ware and Lucent H.GCP/Megaco Structured Message Encoding Using an ASCII Line Format 1609 Lucent Technologies Support for Q.931 TNS and NSF IEs in H.225.0 *1610 Q.14 Rapporteur Changes to H.248 Proposed by IETF Megaco 1611 RAD Data Communications LTD Proposals for the next version of H.341 MIB 1612 Lucent Technologies,Intel Corporation,FORE Systems Inc.,Teles AG Proposing structured media and bearers for H.248, 1613 Lucent Technologies Proposal for PUT and DELETE commands in H.248, 1614 Lucent Technologies Scripting framework for H.248, 1615 Lucent Technologies H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 1616 LM Ericsson H.GCP and encoding in networks 1617 LM Ericsson Signalling Transport for H.GCP 1618 LM Ericsson Handling of Optional H.GCP commands 1619 LM Ericsson Notification Indicators in H.323 1620 LM Ericsson Signalling Transport in H.323 *1621 LM Ericsson Draft H.246 Annex C *1622 Lucent Technologies Expression of Gateway Call Capacity 1623 Lucent Technologies Need for the Q.931 Disconnect and Release Messages in H.225.0 1624 TAO Some considerations on the new Annex to H.323 for high quality audiovisual communications 1625 Oki Electric Indsutry Editorial errors in H.450.5 and H.450.7 1626 Nortel Networks Tunneling of Q.SIG information in H.225.0 1627 IETF Megaco Working Group R2 Package for MEGACO Protocol 1628 IETF Megaco Working Group Megaco IP Phone Media Gateway *1629 IETF Megaco Working Group Basic Packages For Megaco/H.248 *1630 Cisco Systems,Inc. SDP Encoding for H.248. *1631 Tech-Know-Ware and BT A Package based Extensible Object-Oriented Framework for H.225 1632 Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Structured Syntax for H.248 1633 Mitel Proposals for Enhanced Feature Support in H.323 1634 Intel Security tokens for releaseComplete UUIE 1635 Telcordia Technologies Mapping H.245 semantics to SDP 1636 Telcordia Technologies Comparing EBNF and ASN.1 for text encoding *1637 Rapporteur Q13 Protocols for Trunking and Access Gateways *1638 LucentTechnologies Gatekeeper Modification of Destination Addresses *1639 LucentTechnologies Trunk and Line Selection in H.323 Gateways 1640 Nortel Networks Clarification on the use of E.164 numbers *1641 Lucent Interoperabity between H.323 Systems using G.711 and SD/CNG 1642 Alcatel and Nortelnetworks Reference to af-saa-0124.000 specification in H.323.V3 1643 MPEG Liaison Statement from SC 29/WG 11 to ITU-T SG 16 on MPEG-4 Over H.32x Terminals [SC 29/WG 11 N 2887] ----------------------------------------------------------------------------

1 0