Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests

This JSR has been Withdrawn
Reason: Withdrawn after no one on the Expert Group offered to take over the Spec Lead role. Because of the resourcing issues, Nortel had to withdraw from JSR125. Nortel was unable to provide the RI and the TCK, but believed that this is the right approach for a Proxy and small footprint SIP servers/Clients.

Updates to the Original JSR

The following information has been updated from the original request.

2003.09.25: The Spec Lead was changed from Ubiquity to Nortel.

Specification Lead: David Tweedie

E-Mail Address:

Telephone Number: +1 613 763 1725

Fax Number: -

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Ubiquity Software Corporation Ltd

Name of Contact Person: Carole Goddard

E-Mail Address:

Telephone Number: +44 1633 765600

Fax Number: +44 1633 765601

Specification Lead: Chris Rafferty

E-Mail Address:

Telephone Number: +44 163 376 5600

Fax Number: +44 163 376 5601

NOTE that this information has been updated from this original request.

Initial Expert Group Membership:

Sun Microsystems

Section 2: Request

2.1 Please describe the proposed Specification:

The Session Initiation Protocol (SIP) is a signaling protocol that can be used to establish, modify, and terminate sessions in IP network.
A session can be as simple as a two-way telephone call or it could be a more complicated multi-media conference session. This JSR
requests the creation of a specification which will provide a high-level API to a SIP stack. By high level, the API will aim to provide an
API that utilises SIP as the underlying protocol but provides a high-level means of using this protocol. Thus the advantages of using SIP
as a protocol will not be lost yet the developer will not have to have a thorough knowledge of the SIP protocol. This API will be aimed
at application developers, who will use the API to write applications such as end-point applications or applications that act as back to back
users-agents. Another use of the API could be as an interface within a gateway. This will be version 1.0

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

The target for JAINTM SIP Lite is Java 2 Platform, Standard Edition (J2SE) and possibly for Java 2 Enterprise Edition (J2EE), along with Java 2 Micro Edition (J2ME).

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

The goal of this high-level API will be to allow application developers to create application's that have SIP as their underlying protocol
without having to have an extensive knowledge of the SIP protocol. This will allow developers to rapidly create applications, such as
user-agent type applications. JAIN SIP Lite will be a thin Java API that can be used as a high-level wrapper around the SIP protocol
that will provide application developers with an API that is easy to use.

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

JAINTM SIP API (JSR 32) defines a low-level API to a SIP stack. The API requires extensive knowledge of the underlying SIP protocol to be
able to make full use of the API. On the other hand, JCC is a high level API which completely abstracts away from the underlying protocol.
JAIN SIP Lite would provide an API which does not require a thorough knowledge of the SIP protocol but does not hide the advantages of SIP
as the underlying protocol. JAIN SIP Lite will not preclude the use of JAIN SIP or JAIN JCC.

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

Session Initiation Protocol (SIP) is a protocol which is responsible for creating, managing and tearing down sessions between one or more
end-points in an IP network. There are two main components to a SIP system. User Agents which act as the end-points are responsible for
creating, sending and responding to SIP requests. Proxies provide name resolution and user location for these SIP requests. The ability to create
sessions means that a number of different services such as Instant Messaging and voice-enriched e-commerce become possible. JAIN SIP Lite
is aimed at the User Agent application development.

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


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


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


2.9 Are there any internationalization or localization issues?


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


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

Creation of expert group as soon as JSR is approved.
Regular sessions during JAIN meetings and conference calls when required.

Community Review : mid Q3 2001
Public Review : early Q4 2001
Proposed Final Draft : late Q4 2001
RI & TCK : mid Q1 2002
Final Release : early Q2 2002

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

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.

M.Handley, H. Schulzrinne, E. Schooler and J. Roseberg, "SIP: Session Initiation Protocol", Nov. 2000

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

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

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.