- sg16-avd - lists.packetizer.com

Re: submitting APC-1692
by Qiaobing Xie 11 Oct '99

11 Oct '99

Thanks, Chip! -Qiaobing On Oct 11, 4:41pm, Chip Sharp wrote: > Subject: Re: submitting APC-1692 > I've uploaded APC-1692 into the avc-site/incoming directory for Qiaobing. > > Chip > > At 12:08 PM 10/11/99 -0500, Qiaobing Xie wrote: > >Please find in the attached .zip file our APC-1692 submission to > >the Red Bank meeting. I have difficulty to directly upload the > >file into the ftp directory due to our company security control. > > > >Thanks, > > > >=============================================================== > > Qiaobing Xie, Ph.D > > Network Architecture & Technology > > Motorola, Inc. > > 1501 W. Shure Dr., Arlington Heights, IL 60004 > >=============================================================== > > > > > > > >X-Zm-Content-Name: APC-1692.zip > >Content-Description: Data > >Content-Type: application/octet-stream ; name="APC-1692.zip" > >X-Zm-Decoding-Hint: mimencode -b -u > > Support NetAid! http://www.netaid.org > -------------------------------------------------- > Chip Sharp Consulting Engineering > Cisco Systems Telco Bio-region > Reality - Love it or Leave it. > -------------------------------------------------- >-- End of excerpt from Chip Sharp

1 0

submitting APC-1692
by Qiaobing Xie 11 Oct '99

11 Oct '99

Please find in the attached .zip file our APC-1692 submission to the Red Bank meeting. I have difficulty to directly upload the file into the ftp directory due to our company security control. Thanks, =============================================================== Qiaobing Xie, Ph.D Network Architecture & Technology Motorola, Inc. 1501 W. Shure Dr., Arlington Heights, IL 60004 ===============================================================

2 1

APC-1735 (draft H.248)
by John Segers 11 Oct '99

11 Oct '99

Dear SG16 experts, The draft text for H.248 is availabe at <ftp://standards.nortelnetworks.com/megaco/docs/latest/MegacoH248v11.pdf >. From this document I will create APC-1735, showing the changes that were made, and upload that as soon as possible. With apologies for not meeting the deadline with APC-1735. Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 344 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

Re: APC-1735 (draft H.248)
by Nancy-M Greene 11 Oct '99

11 Oct '99

Please note that the pdf file pointed to below does NOT have the ITU text in it, as it had the IETF text macro on when I created it - you will see the ITU text in APC-1735 though. At least two places where this is an issue is the scope, and the last paragraphs in Annex G. There are probably more places. Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com > ---------- > From: John Segers[SMTP:jsegers@LUCENT.COM] > Sent: Monday, October 11, 1999 4:15 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: APC-1735 (draft H.248) > > Dear SG16 experts, > > The draft text for H.248 is availabe at > <ftp://standards.nortelnetworks.com/megaco/docs/latest/MegacoH248v11.pdf > >. From this document I will create APC-1735, showing the changes that > were made, and upload that as soon as possible. > > With apologies for not meeting the deadline with APC-1735. > > Regards, > > John Segers > -- > John Segers email: jsegers(a)lucent.com > Lucent Technologies Room HE 344 > Dept. Forward Looking Work phone: +31 35 687 4724 > P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954 >

1 0

Uploaded apc-1653
by Tony Crossman 11 Oct '99

11 Oct '99

Dear colleagues, I have uploaded the proposal to include G.722.1 capabilities in the H.323 Implementors Guide. The contribution can be found at the following location: ftp://standard.pictel.com/avc-site/Incoming/APC1653.zip Tony Crossman ********************************************* Antony Crossman PictureTel Corporation 100 Minuteman Road, Andover, MA 01810, USA Tel. +1 (978) 292 4557 Fax. +1 (978) 292 3228 email. tonyc(a)pictel.com *********************************************

1 0

Annex G use of releaseCompleteReason
by Rich Bowen 11 Oct '99

11 Oct '99

In the TerminationCause structure of Annex G, the releaseCompleteReason field is mandatory. However, in the H.225.0 Release Complete message, the ReleaseCompleteReason is optional, although it must be specified if the Cause IE is not included. What should a border element place in the releaseCompleteReason field of the TerminationCause if there was no releaseCompleteReason specified in the Release Complete? Should this field have been optional in Annex G? Rich -------------------------------------------------------------------- Richard K. Bowen Cisco Systems, Inc. rkbowen(a)cisco.com Research Triangle Park, NC --------------------------------------------------------------------

1 0

Upload
by Espen Skjæran (ETO) 11 Oct '99

11 Oct '99

Colleagues, I've uploaded these two documents to Incoming: APC-1696 H.323 Annex K (HTTP based service control) APC-1697 Additions of codepoints to H.225.0 for service control Regards, Espen

1 0

None
by Barry Aronson 11 Oct '99

11 Oct '99

Dear All, APC-1738 has been uploaded to the PictureTel Incoming directory as APC-1738.ZIP. TITLE: H.323 Annex I Terms of Reference, v2 SOURCE: Editor Regards, Barry

1 0

APC-1710 and APC-1711 uploaded
by John Segers 11 Oct '99

11 Oct '99

Dear SG 16 experts, The following documents have been uploaded to the Incoming directory on the picturetel archive: APC-1710 Title: Changes to H.248 to allow use in non-IP environments Source: Lucent Technologies APC1711 Title: ASN.1 syntax definition for H.248 Source: Lucent Technologies, Tech-know-ware Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 344 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

APC-1703 and APC-1704
by Francois Audet 11 Oct '99

11 Oct '99

The following contributions have been uploaded to the incoming directory. APC-1703 Tones and annoucement in fast start APC-1704 Removal of subjective material in gateway decomposition architecture ----- François Audet Tel:+1 408 565 5675 mailto:audet@NortelNetworks.com Nortel Networks Fax:+1 408 565 2375 http://www.NortelNetworks.com

1 0

uploaded APC1663.zip
by Irina Suconick 11 Oct '99

11 Oct '99

Dear colleagues, > I posted a draft for H.341V2 here: > > ftp://standard.pictel.com/avc-site/Incoming/APC1663.zip > Regards, Irina > >

1 0

APC-1712 - H.248/Megaco Text Message line format - Uploaded
by Pete Cordell 11 Oct '99

11 Oct '99

Dear All, APC-1712 has been uploaded to the PictureTel Incoming directory. TITLE: H.248/Megaco Structured Message Encoding Using a Text Line Format SOURCE: John Segers, Lucent; Christian Groves, LM-Ericsson; Pete Cordell, Tech-Know-Ware Regards, Pete ============================================= Pete Cordell pete(a)tech-know-ware.com =============================================

1 0

Draft H.225.0 v4 - APC-1686
by Rich Bowen 11 Oct '99

11 Oct '99

The current draft of H.225.0 v4 has been uploaded to the Incoming directory as APC-1686. This draft used H.225v3b (the input document to the Sept 30 meeting in Geneva) as a base, and does not include the minor changes that were made in Geneva but I will incorporate those changes as soon as I have a copy of the Decided H.225.0 v3. This draft should include all contributions that were approved for H.225.0 v4 in Berlin. If you made a contribution that was approved, please review this draft and let me know of any corrections that are needed. The following contributions were incorporated: APC-1567 - HTTP based service control transport (Ericsson) APC-1568 - Support for TDMA wireless coders (AT&T) APC-1581 as amended by TD-27 - Improved alias registration (Lucent, Nortel) APC-1594 as amended by TD-30 - Problems with XRS RAS message (PictureTel) APC-1595 - Additional information in ARQ for Gateway calls (PictureTel) APC-1596 - Support for G.722.1 (PictureTel) APC-1607 - Enforcing Symmetric Operation in Fast Connect (Cisco) APC-1622 as amended by TD-39a - Expression of GW Call Capacity (Lucent) APC 1638 - GK mapping of destination addresses (Lucent) APC 1640 as modified by TD-36 - Clarifications of E.164 numbers (Nortel, Siemens) Regards, Rich -------------------------------------------------------------------- Richard K. Bowen Cisco Systems, Inc. rkbowen(a)cisco.com Research Triangle Park, NC --------------------------------------------------------------------

1 0

Re: Message Structure in H.225.0 Annex G
by Lior Moscovici 10 Oct '99

10 Oct '99

Well, this would make the change even "more" impossible - it would require a change in the ASN.1 per each type of PDU, e.g.: AccessRequest ::= SEQUENCE { common AnnexGCommonInfo, destinationInfo PartyInformation, sourceInfo PartyInformation OPTIONAL, callInfo CallInformation OPTIONAL, usageSpec UsageSpecification OPTIONAL, ... } Also it doesn't guarantee that the common part gets into every PDU that will be invented in the future. Well, that's ASN.1 and we have to leave with it. Regards, Lior "Krishna Kr Banka" <kkbanka(a)HSS.HNS.COM> on 10/08/99 10:26:16 AM To: Lior Moscovici cc: "ITU-SG16" <itu-sg16(a)mailbag.cps.intel.com>, "H323 Implementors" <h323implementors(a)imtc.org>, "Krishna Kr Banka" <kkbanka(a)HSS.HNS.COM>, "Chirag Vaidya" <cvaidya(a)HSS.HNS.COM> Subject: Re: Message Structure in H.225.0 Annex G Hi Lior..!! There seems to be yet another issue regarding the following : > Since the "common" part includes the Sequence Number and other information > needed for lower level treatment of the message, this part should be > decoded first, and the natural order should have been reversed. This is > important since the size of the "body" is not fixed, and for cases in which > there is an error in the encoding of the body. If the *common* part is placed above the *message-specific* portion, then we shall have a problem extracting the message type out of the encoded message PDU. Since the common part contains fields such as : tokens, cryptoTokens, nonStandard, which can be of variable length; the message-type cannot be accessed without decoding the whole message. One of the possibilities, in my opinion, is that the common part should be made the first field of the message-body itself. Regards Krishna

1 0

Re: Request for APC for Red Bank Meeting
by Sakae OKUBO 09 Oct '99

09 Oct '99

Dear Mr. Aronson, Dear Mr. Ott, Dear Ms. Levin, In response to your request, the following APC numbers have been allocated to your contributions: APC-1738 > Title: H.323 Annex I Terms of Reference, v2 > Source: Barry Aronson, Editor APC-1739 > Source: Teles et al > Title: H.323 robustness mechanisms APC-1740 > Source: Teles et al > Title: Organizing work on H.323 - SIP - Interworking APC-1741 > Source: RADVision > Title: Clarifications for Fast Connect Procedure APC-1742 > Source: RADVision > Title: Clarifications for the use of Call Signaling Address in H.225.0 > SETUP Procedure 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

Re: APC Number
by Sakae OKUBO 08 Oct '99

08 Oct '99

Dear Mr. Potter, APC-1737 has been allocated to your contribution. > Methods of transporting ISUP across H.323: Issues for consideration > > Source: Morgan Potter, BT. 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

Re: Request APC number for Red Bank meeting
by Sakae OKUBO 08 Oct '99

08 Oct '99

Dear Mr. Rosen, APC-1736 has been allocated to your contribution. > Title: H.248 Transport for ATM > Source: Brian Rosen, FORE Systems 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

Re: Request APC number for Red Bank meeting
by Sakae OKUBO 08 Oct '99

08 Oct '99

Dear Mr. Segers, APC-1735 has been allocated to your contribution. > Title: Draft H.248 > Source: Editors (John Segers, Brian Rosen) 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

Re: Request for APC numbers
by Sakae OKUBO 08 Oct '99

08 Oct '99

Dear Mr. Bowen, In response to your request, the following APC numbers have been allocated to your three contributions: APC-1732 > Source: Cisco Systems: > "Proposed FacilityReason Codepoint for New Tokens" APC-1733 > Source: Cisco Systems: > "Addition of Billing Information to the DRQ Message" APC-1734 > Source: Cisco Systems: > "Support for Multiple Payload Types in Logical Channels" 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

Re: [Fwd: Request for APC numbers]
by Sakae OKUBO 08 Oct '99

08 Oct '99

Dear Mr. Groves, In response to your request, the following APC numbers have been allocated to your 19 Ericsson contributions: APC-1713 > Title: H.248 Line Encoding > Source: LM Ericsson (Christian Groves) APC-1714 > Title: H.248 IANA consideration for Package extension > Source: LM Ericsson (Christian Groves) APC-1715 > Title: H.248 Signal Direction > Source: LM Ericsson (Christian Groves) APC-1716 > Title: Cause Handling in H248 > Source: LM Ericsson (Christian Groves) APC-1717 > Title: H.248 Functional Outage > Source: LM Ericsson (Christian Groves) APC-1718 > Title: H.248 ServiceChange > Source: LM Ericsson (Christian Groves) APC-1719 > Title: Monitoring in H248 > Source: LM Ericsson (Christian Groves) APC-1720 > Title: H.248 Event Enhancements > Source: LM Ericsson (Christian Groves) APC-1721 > Title: H.248 Multiple Virtual MG Enhancements > Source: LM Ericsson (Christian Groves) APC-1722 > Title: H.248 Loss of association btwn the MG and MGC > Source: LM Ericsson (Christian Groves) APC-1723 > Title: H.248 Priority calls > Source: LM Ericsson (Christian Groves) APC-1724 > Title: Native Descriptors in H248 > Source: LM Ericsson (Christian Groves) APC-1725 > Title: H.248 Signalling Transport Converter for MTP > Source: LM Ericsson (Alf Heidermark) APC-1726 > Title: H.248 Description of the generic signalling > Source: LM Ericsson (Alf Heidermark) APC-1727 > Title: Draft H.246 Annex C > Source: Editor (Christian Groves) APC-1728 > Title: Negotiation of Protocol Capabilities in H225 RAS > Source: LM Ericsson (Ian Rytina) APC-1729 > Title: Sigtran in H225 > Source: LM Ericsson (Ian Rytina) APC-1730 > Title: Architectural strives for Conversational Multi Media with Multi > Access > Source: LM Ericsson (Gosta Linder) APC-1731 > Title: A layered network architecture for Voice and Multimedia over IP > Source: LM Ericsson (Gosta Linder) 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

Documents uploaded
by Euchner Martin 08 Oct '99

08 Oct '99

The following contributions have been uploaded in the incoming directory: APC-1674 Draft H.323 Annex J: Security for H.323 Annex F APC-1675 Draft H.235 Version 2 APC-1676 ClearToken enhancement in H.235 Version 2 APC-1677 AES support in H.235 Version 2 APC-1678 Elliptic curve support in H.235 Version 2 APC-1679 Security Profile negotiation in H.235 Version 2 ----------------------------------------------------------------------- | Dipl.-Inf. Phone: +49 89 636-46201 | Martin Euchner Fax : +49 89 636-48000 | Siemens AG | ZT IK 3 mailto:Martin.Euchner@mchp.siemens.de | Intranet: http://zt-security.mchp.siemens.de/Standardization/ITU-T_SG16/index.html | Otto-Hahn-Ring 6 Internet: http://www.siemens.de | D-81730 Muenchen | __________________ | Germany -----------------------------------------------------------------------

1 0

Re: Message Structure in H.225.0 Annex G
by Krishna Kr Banka 08 Oct '99

08 Oct '99

Hi Lior..!! There seems to be yet another issue regarding the following : > Since the "common" part includes the Sequence Number and other information > needed for lower level treatment of the message, this part should be > decoded first, and the natural order should have been reversed. This is > important since the size of the "body" is not fixed, and for cases in which > there is an error in the encoding of the body. If the *common* part is placed above the *message-specific* portion, then we shall have a problem extracting the message type out of the encoded message PDU. Since the common part contains fields such as : tokens, cryptoTokens, nonStandard, which can be of variable length; the message-type cannot be accessed without decoding the whole message. One of the possibilities, in my opinion, is that the common part should be made the first field of the message-body itself. Regards Krishna

1 0

Re: draft-04 vs. Results from Berlin
by Nancy-M Greene 08 Oct '99

08 Oct '99

Oops, I got the URLs wrong - as Qiaobing pointed out, the prefix is missing megaco/docs - I've corrected the URLs: > For each point raised at the ITU-T SG16 meeting in Berlin, I have put the > reference in the new Megaco/H.248 draft that covers it. This can be used > to determine how the current draft implements the desired change requested > in Berlin. > > The Berlin draft is: ftp://standards.nortelnetworks.com/megaco/docs/wash99/MegacoH248v9Chgs.doc > or ftp://standards.nortelnetworks.com/megaco/docs/wash99/MegacoH248v9Chgsdoc.zi p > The draft-04 of Megaco/H.248 is: ftp://standards.nortelnetworks.com/megaco/docs/latest/megaco-h248_protocol.p df > or ftp://standards.nortelnetworks.com/megaco/docs/latest/draft-ietf-megaco-prot ocol-04.txt <snip> sorry about the extra mail, Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com

3 2

Upload of White Paper for Version 6 of H.245 (New version)
by mike.nilsson＠BT.COM 08 Oct '99

08 Oct '99

I have sent the White Paper for version 6 of H.245 to the ITU and have uploaded it to ftp://standard.pictel.com/avc-site/Incoming/h245_k.zip This contains three files: WCM (full version with change marks), NCM (full version with no change marks) and DEL (cut down version with change marks). The only change from the version I posted to the ftp site on 14 September concerns Annex I, GSM Adaptive Multi Rate Capability Definitions, where a number of the tables have been changed. Best regards Mike Nilsson ********************************************************************** * Mike Nilsson Tel: +44 1473 645413 * * Applications Technology Group Fax: +44 1473 645011 * * Internet and Multimedia Applications Email: mike.nilsson(a)bt.com * * BT Advanced Communications Technology Centre [B54 Room 94] * * Adastral Park * * Martlesham Heath * * Ipswich IP5 3RE * * UK * **********************************************************************

2 1

APC Document number
by Noriko Hosokawa 08 Oct '99

08 Oct '99

Dear Paul E. Jones In response to your request, APC-1707 and APC-1708 have been allocated to your contributions. APC-1707 > Source: Editor (P Jones) > Title: Early Termination of Fast Connect Procedure in H.323 APC-1708 > Source: Cisco Systems > Title: Closure of the Call Signaling Channel by the Gatekeeper 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 Red Bank (18-22 October 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9910_Red/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9910_Red/APC-1???.??? ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1645 TIPHON Proposal for an H.323 "Security Profile" 1646 Motorola Annex-H(User and Service Mobility in H.323) 1647 Lucent Mobility Agents in H.323 Reference Architecture 1648 Lucent Registration Procedure for Wireless Mobile H.323 Terminals 1649 Lucent Mobility States for the Mobile H.323 Terminals 1650 Lucent H.245 Generic Capabilities Definition and H.225 Packetization Specification for the Cellular/PCS CDMA EVRC Voice Codec. 1651 AT&T H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1652 AT&T Viewgraph Presentation of H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1653 PictureTel Proposed text for G.722.1 capabilities in the H.323 Implementor's Guide 1654 Nortel ISO/IEC 11571 addressing in H.323 Annex V Networks 1655 Hitachi Ltd. Real-time system of H.262 layered video transmission 1656 Nortel Networks Tunnelling of signalling messages in H.225.0 1657 Nortel Networks Applicability of signalling tunnelling mechanism to Q.SIG 1658 Editor (K Klaghofer) Draft H.450.9 Call Completion Supplementary Services for H.323 1659 Nokia Functional Requirements for H.323 Annex H (Terminal, User and Service Mobility) 1660 Mitel Proposed H.323 Annex L (Stimulus Protocol) 1661 VocalTec Communications Ltd. Resolution of H.245 ambiguity when using Fast Connect procedure 1662 VocalTec Communications Ltd. et. al. Changes to H.323 to support operation behind basic NAT devices - version 2 1663 Editor (I Suconick) H.341 V2 contribution 1664 AT&T H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1665 AT&T Viewgraph Presentation of H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1666 Nortel and Siemens Megaco/H.248 Generic Packages 1667 Editor (P Jones) H.323v4 draft 1668 AT&T et al Call Flows Supporting H.323 QOS 1669 AT&T et al Extensions of H.225.0 and H.225.0 Annex G Signaling Messages and their ASN.1 Syntax to Support H.323 QOS 1670 AT&T et al Framework for Mapping of H.323 QOS over Packet-based Networks 1671 Intel The H.323 terminal with secured software based Universa Subscriber Identification Module (USIM) and Inter-working Function with PLMN (public land and mobile networks) 1672 Intel User Mobility and Service Mobility services for Wireless Subscribers with H.323 terminals accessing Multimedia over IP (MoIP) and PLMN networks 1673 Hughes Software Systems Redundancy and Fault Tolerance Procedures in H.323 1674 Editor (M Euchner) H.323 Annex J: Security for H.323 Annex F 1675 Editor (M Euchner) H.235 Version 2 1676 Siemens AG ClearToken enhancement in H.235 Version 2 1677 Siemens AG AES support in H.235 Version 2 1678 Siemens AG Elliptic curve support in H.235 Version 2 1679 Siemens AG Security Profile negotiation in H.235 Version 2 1680 SG16 management Draft Questions for SG16 WP2 for the new study period 1681 Siemens AG Identification of Gateway Protocol 1682 InterVoice Media Redirection and Replication 1683 BT ISUP Transport in H.225 using a Generic, Extensible Framework 1684 Lucent Technologies and VocalTec Multiple UsageIndications in Annex G 1685 Lucent Technologies Using CPL with H.323 1686 Editor (R Bowen) Draft H.225.0 v4 1687 Lucent Technologies H.323 Annex F Hookflash Signaling Enhancements 1688 Editor (G HellstromR H.323 Annex G Text Conversation, draft 1689 Ericsson RTP-Text for H.323 Annex G Text Conversation 1690 Ericsson F.MCVS conversation service description with Total Conversation and Text telephony 1691 Ericsson H.248 packages and additions for text telephony and total conversation. 1692 Motorola Using SCTP as an Alternate H.248 Transport 1693 Editor (P Jones) H.323 Implementers Guide 1694 BT Object Profile for ISUP Transport in H.225 using Generic Extensible Framework 1695 IETF Megaco Working Group Megaco/H.248 Requirements - Communication from IETF 1696 Editor (E.Skjaeran, Ericsson) H.323 Annex K (HTTP based service control) 1697 Ericsson (E.Skjaeran) Additions of codepoints to H.225.0 for service control channel 1698 Siemens,Munich University of Technology Progressive AV coding for packet switched lossy networks - a principle approach 1699 Trillium Digital Systems Modifications to the H.225 Annex G protocol 1700 Rapporteur of Q.19/16 Support of proposed modifications on H.245 ASN.1 1701 NTT DoCoMo Multiplexed stream transmission over H.323 logical channel 1702 NEC Editorial errors in H.245 version 4, version 5 1703 Nortel Networks Tones and announcement in fast start 1704 Nortel Networks Modification to gateway decomposition architecture 1705 Nokia On H.323 QoS 1706 Nokia On H.323 Mobility 1707 Editor (P Jones) Early Termination of Fast Connect Procedure in H.323 1708 Cisco Systems Closure of the Call Signaling Channel by the Gatekeeper 1709 1710 ---------------------------------------------------------------------------- ----

1 0