Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 140: Service Location Protocol (SLP) API for Java

This JSR has been Withdrawn
Reason: The Spec Lead was not doing work on the JSR. While several other organizations have done seemingly promising Java work in the SLP area, none of them was interested in taking over the spec lead position to progress a JSR on it.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Caldera Systems

Name of Contact Person: Darren R. Davis

E-Mail Address:

Telephone Number: +1 801 932 5601

Fax Number: +1 801 765 1313

Specification Lead: Darren R. Davis

E-Mail Address:

Telephone Number: +1 801 932 5601

Fax Number: +1 801 765 1313

Initial Expert Group Membership:

Caldera Systems Sun Microsystems

Section 2: Request

2.1 Please describe the proposed Specification:

This Java specification request will standardize the Java SLP API that was described in RFC 2614.

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

J2SE and J2EE.

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

The Java community will be able to use the standard SLP API for discovery in Java Applications.

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

This API is decribed in RFC 2614, but has not been formally standardized by the JCP.

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

Service Location Protocol is an IETF standards track protocol that provides a framework to allow networking applications to discover the existence, location, and configuration of networked services in enterprise networks.

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

To be defined, but something like javax.slp.

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?

This should replace RFC 2614and should not effect any Java specifications.

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

This process should take approximately 6 month.

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

The working group will start with the existing IETF RFC 2614. We have some proposed changes which will be applied. We will pass this specification via email to the expert group members for review. We will have teleconference discussions monthly to discuss any needed changes.

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.

RFC 2614 - OpenSLP - mSLP - Service Location -

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

The RFC mostly describes the C and Java API for SLP. Some requested updates to the API are available. This JSR will bring the Java API current.

Section 4: Additional Information (Optional)

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