Name of Contact Person: Orit Levin

E-Mail Address: orit@radvision.com

Telephone Number: +1 201 529 4300 (Ext. 230)

Fax Number: +1 201 529 3516

Specification Lead: Orit Levin

E-Mail Address: orit@radvision.com

Telephone Number: +1 201 529 4300 (Ext. 230)

Fax Number: +1 201 529 3516

Initial Expert Group Membership:

RADVision

Section 2: Request

2.1 Please describe the proposed Specification:

H.323 defines a system for moving real-time bi-directional multimedia (video, voice, data, fax, etc.) across packet-based networks. The signaling protocols are defined by H.225.0 and include "Registration, Admission and Status" (RAS) and a the "Call Signaling" (derived from ISDN Q.931). The Media Control protocol is defined by H.245. H.245 provides, among others, negotiation of media capabilities; opening and closure of the media channels; changing the characteristics of a media channel.

H.323 uses the IETF RTP/RTCP protocol to transmit the media streams.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

All of the above.

2.3 What need of the Java community will be addressed by the proposed specification?

After four years experience, H.323 Protocol is stable and the most widely deployed protocol on the "Multi-media over IP" arena, including VoIP.

H.323 is being used in a variety of multimedia applications such as Call Center, VoIP trunking applications, remote education, etc. H.323, as the most mature specification, is the standard of choice for systems that need multi-vendor components.

2.4 Why isn't this need met by existing specifications?

H.323 hasn't been addressed by JAIN^TM so far.

2.5 Please give a short description of the underlying technology or technologies:

The purpose of this specification is to define a standard H.323 API for independant H.323 Protocol stacks that can be run as a programm, applet, servlet, or bean will be considered. As a minimum, the H.323 API for J2SE will be addressed. Among the design considerations of the API are:

1. providing an abstraction of the H.323 protocol details
2. modular design allowing for building various applications defined by Annexes of H.323 and H.225.0

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

jain.protocol.h323.subscriber
jain.protocol.h323.call
jain.protocol.h323.channel

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

None.

2.8 Are there any security issues that cannot be addressed by the current security model?

None. This specification expects to utilize standard JDK security.

2.9 Are there any internationalization or localization issues?

None. H.323 is an ITU Standard.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

"JAIN^TM SIP API" specification addresses analogous applications. H.323 uses RTP/RTCP protocol along with SIP, MGCP and MEGACOP. These are potential areas of mutual influence. Although, currently no discrepancies are known.

2.11 Please describe the anticipated schedule for the development of this specification.

9 months. A subject for change based on a defined feature set.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

The public site to access H.323 standards and working documents is

http://standard.pictel.com/ftp/avc-site/

3.2 Explanation of how these items might be used as a starting point for the work.

It is expected from the H.323 Expert group members to be familiar with the details of the H.323 Protocol.