2.1 Please describe the proposed Specification:

SIP Servlet 1.1 made significant progress in standardization of SIP
programming based on the Java EE platform. The purpose of the SIP Servlet 2.0
specification is to further evolve the SIP Servlet technology to address the
new requirements pertaining to converged application development.

The specification would align the SIP Servlets with latest Java EE standards .
As part of this effort, the following Java EE 6 enhancements are planned to be
extended to SIP Servlets.

Expert group would look at aligning with Java EE 7 features that are being
standardized now.

This specification also intend to enhance the SIP and communication
functionality in the following areas.

- Interworking of SIP Servlets with other protocols.

A typical SIP Servlet application interact with a number of different
protocols (eg: diameter, MSRP). Many times, application listeners and sessions
of such protocols interwork with SIP servlets and SIP sessions. The
specification would look at standardizing interworking of such protocols with
SIP servlets by defining a generic model wherever possible.

- Simplification of SIP Servlet development.

SIP Servlet 1.1 introduced many new concepts for simplifying the development
of SIP applications. These include new annotations, dependency injection, helper
class for back to back user agent pattern etc. This specification will look at
further simplification of the programming model to enable rapid development of
communication services.

- Incorporate requirements from other standardization efforts.

A number of groups are working on standardizing technologies relevant to SIP
Servlet outside JCP. One example is WebRTC standardization in IETF and W3C.
The SIP Servlet expert group will examine any requirements from such efforts
for potential standardization.

- Other enhancements and bug fixes.

The expert group will also look at enhancing other features of SIP Servlets.
Potential areas for enhancement and bug fixing could include, but not limited
to,

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

This specification has no direct impact on the Java Enterprise Edition or
the Java Standard Edition. An implementation of this specification may run on the
Java Standard Edition or Java Enterprise Edition run-time.

2.4 Should this JSR be voted on by both Executive Committees?

No. It should be voted on by the Java SE / EE Executive Committee only.

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

See 2.1 above.

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

This specification is an update to the existing SIP Servlet specification.

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

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

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

The primary means of communication will be email and conference calls.
Face-to-face meetings will be scheduled if needed.

2.15 Provide detailed answers to the transparency checklist, making sure to
include URLs as appropriate:

- Is the schedule for the JSR publicly available, current,
and updated regularly?

The schedule will be available on the project page for the JSR.

- Can the public read and/or write to a wiki for the JSR?

We'll use a public mailing list for comments.

- Is there a publicly accessible discussion board for the JSR that
you read and respond to regularly?

We'll track such discussions and respond to them on the public
comment mailing list.

- Have you spoken at conferences and events about the JSR recently?

There was a BOF session at JavaOne 2011 covering this JSR.

- Are you using open-source processes for the development of the
RI and/or the TCK?

No.

- What are the Terms of Use required to use the collaboration tools
you have prepared to use with the Expert Group, so that prospective
EG members can judge whether they are compatible with the JSPA?

The terms will be available on the project page for the JSR.

- Does the Community tab for my JSR have links to and information about
all public communication mechanisms and sites for the development of my JSR?

Yes, it will point to the project page for the JSR.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The RI and TCK will be delivered stand-alone, just like SIP Servlet v1.1.
The RI and TCK will be built upon the SIP Servlet v1.1 RI and TCK.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).

N/A

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.