 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 164: SIMPLE Presence
Updates to the Java Specification Request (JSR) The following information has been updated from the original JSR: 2013.08.02: Panasonic Corporation has become the Maintenance Lead. Maintenance Lead: Minoru Okamoto E-Mail Address: okamoto.minoru Telephone Number: - Fax Number: -
2007.09.07: E-Mail Address: jekthoon.tan Telephone Number: +65 6550 5495 Fax Number: +65 6550 5459 2007.01.22:
Maintenance Lead: Alan Kaplan, Panasonic Princeton Laboratory E-Mail Address: kaplana@research.panasonic.com Telephone Number: +1 609 734 7339 Fax Number: -
2005.03.16: - Changed JSR name from JAINTM SIMPLE Presence to SIMPLE Presence. Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Panasonic Information and Networking Technologies Laboratory of Panasonic Technologies Company, Division of Matsushita Electric Corporation of America. Name of Contact Person: Mourad Debbabi E-Mail Address: debbabim@research.panasonic.com Telephone Number: +1 609 734 7329 Fax Number: +1 609 987 8827 Specification Lead: Mourad Debbabi Note that this information has been updated from the original JSR.
E-Mail Address: debbabim@research.panasonic.com Telephone Number: +1 609 734 7329 Fax Number: +1 609 987 8827 Initial Expert Group Membership: o Panasonic Information and Networking Technologies Laboratory Supporting this JSR: Section 2: Request
2.1 Please describe the proposed Specification:This JSR aims to elaborate a JAINTM API that leverages the Session Initiation Protocol (SIP) to provide a presence service. The Session Initiation Protocol (SIP) is an IETF standard signaling protocol that can be used to establish, modify and terminate sessions in IP networks. SIMPLE is an IETF working group that advanced a set of extensions to SIP to support presence and instant messaging. This JSR aims to create a JAINTM specification to the SIP extensions for presence. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)The target platform for JAINTM SIMPLE Presence is the JavaTM 2 micro and standard editions. The micro edition is meant to be the platform for client devices (primarily handsets). The standard edition is meant to be the platform for desktop-based clients and also for presence servers.
2.3 What need of the Java community will be addressed by the proposed specification?The proposed specification will spur the development of JAINTM-compliant combined services and applications (web, mail, chat, messaging, presence, etc.) that leverage the flexibility of SIMPLE. It will provide Java developers with a standard API to SIMPLE protocol stack providers and allow them to use a multitude of SIP and SIMPLE-enabled applications. As for carriers, it will remove their dependence on a specific SIP/SIMPLE vendor and allow them to integrate with other JAINTM solutions. 2.4 Why isn't this need met by existing specifications?There are no existing Java specifications of an API that support presence on top of the SIP protocol. It is well established that SIP offers tremendous advantages with the SIMPLE extensions to support presence: unification of major communication services, sharing of databases, sharing of proxies, sharing of servers, reduction of management costs, enabling of new combined services, etc. Moreover, JAINTM SIMPLE Presence comes as a natural extension to the JAINTM SIP and JAINTM SIP Lite APIs. As JAINTM SIP is a standard API to the SIP protocol, and JAINTM SIP Lite is a lightweight definition of SIP for user agents (including J2ME devices), in a similar vein, the JAINTM SIMPLE Presence API is intended to be a standard API to presence in the SIMPLE protocol (i.e., SIP augmented with presence capabilities). Concomitantly, the PAM Forum has elaborated the PAM (Presence and Availability Management) API. PAM is a high-level, abstract, protocol neutral API for presence. JAINTM SIMPLE Presence will not preclude the use of a Java PAM API. On the contrary, there is an opportunity for synergy between the two APIs since JAINTM PAM can sit on top of the JAINTM SIMPLE Presence API. JAINTM PAM is positioned at the application level while JAINTM SIMPLE Presence provides a standard way to interact with a SIP/SIMPLE stack. 2.5 Please give a short description of the underlying technology or technologies:? SIP is an IETF standard protocol for IP-communication, enabling IP-Telephony gateways, client endpoints, PBXs and other communication systems or devices to communicate with each other. SIP primarily addresses the call setup and tear down mechanisms of sessions and is independent of the transmission of media streams between caller and callee. ? SIMPLE is a set of natural extensions made to the SIP protocol to support presence and instant messaging. ? JAINTM SIP API fully supports the SIP protocol, and is dedicated to Java session control in the telecommunications and Internet industry. ? JAINTM SIP Lite is an abstract JAIN API to the SIP protocol. It is dedicated to user agents running on both the J2SE and J2ME platforms. 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)The package names being considered are: ? javax.jain.ip.simple.security: This package contains security mechanisms that enforce the authorization property. It is primarily to support access control lists. ? javax.jain.ip.simple.presence: This package contains capabilities needed to support presence. This includes support for presence servers (receiving subscription requests, authenticating and authorizing requests, sending notifications, read/write presence information, etc.) and presence user clients (buddy and buddy list manipulations, sending subscriptions, receiving notifications, etc.). 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.8 Are there any security issues that cannot be addressed by the current security model?The proposed API needs to enforce the following security properties: authentication, secrecy and authorization. Authentication and secrecy are fully addressed by the JavaTM security model. However, the API must implement a mechanism to enforce authorization. In particular, an ACL (Access Control Lists) model to manage authorizations for subscription requests at the level of the presence servers is required. 2.9 Are there any internationalization or localization issues?The expert group developing this specification will research the internationalization and localization requirements. 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?No 2.11 Please describe the anticipated schedule for the development of this specification.The anticipated schedule is:
? Requirements: T0 + 4 weeks. where T0 is the time at which the expert group starts working on the elaboration of this proposal. 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The anticipated working model will use:
? A dedicated mailing list. 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.? Panasonic JAINTM-SIMPLE Presence API is being elaborated as a joint research and development initiative between Columbia University (Dr. Henning Schulzrinne) and Panasonic Information and Networking Technologies Laboratory (Dr. Alexander Gelman and Dr. Mourad Debbabi). ? Panasonic JAINTM SIP Lite implementation has been architected, designed and implemented by Panasonic Information and Networking Technologies Laboratory. ? Panasonic Information and Networking Technologies Laboratory and Laval University in Canada are working on a joint research and development initiative that aims to accelerate and secure the J2ME/CLDC platform. ? Rosenberg et al., SIP Extensions for Presence. IETF Draft of the SIMPLE Working Group, September 24, 2001, Expires: March 2002. ? J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, D. Oran, SIP Extensions for Instant Messaging. IETF Draft of the SIMPLE Working Group, July 18, 2001, Expires: January 16, 2002. ? B. Campbell, J. Rosenberg. SIP Instant Message Sessions. IETF Draft of the SIMPLE Working Group, July 13, 2001, Expires: January 11, 2002. ? B. Campbell, J. Rosenberg. SDP Extensions for SIP Instant Message Sessions. IETF Draft of the SIMPLE Working Group, July 13, 2001, Expires: January 11, 2002. ? SIMPLE WG, J. Rosenberg et al. An XML Based Format for Watcher Information. IETF Draft of the SIMPLE Working Group, July 13, 2001, Expires: January 2002. ? SIMPLE WG, J. Rosenberg et al. A SIP Event Sub-Package for Watcher Information. IETF Draft of the SIMPLE Working Group, July 13, 2001, Expires: January 2002.
3.2 Explanation of how these items might be used as a starting point for the work.Our strong starting point in this initiative is twofold:
? A well-defined protocol produced by the IETF SIMPLE working group. This definition comes as a set of extensions to the SIP signaling protocol to support presence and instant messaging. Moreover, we plan to leverage our expertise in SIP, JAINTM SIP, JAINTM SIP Lite and J2ME to elaborate the proposed API. |
