JSRs: Java Specification Requests
JSR 125: JAINTM SIP Lite
This JSR has been Withdrawn
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: davidtw
Telephone Number: +1 613 763 1725
Fax Number: -
Section 1. Identification
Submitting Member: Ubiquity Software Corporation Ltd
Name of Contact Person: Carole Goddard
E-Mail Address: firstname.lastname@example.org
Telephone Number: +44 1633 765600
Fax Number: +44 1633 765601
Specification Lead: Chris Rafferty
E-Mail Address: crafferty
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:
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.
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
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
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
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.
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.