Service Location Protocol (svrloc)

Last Modified: 17-May-01

Chair(s):

Erik Guttman <erik.guttman@sun.com>

Internet Area Director(s):

Thomas Narten <narten@raleigh.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>

Internet Area Advisor:

Thomas Narten <narten@raleigh.ibm.com>

Mailing Lists:

General Discussion:srvloc@srvloc.org
To Subscribe: srvloc-request@srvloc.org
Archive: http://www.srvloc.org/hypermail/index.htm

Description of Working Group:

The Service Location Protocol is a decentralized, lightweight, scalable and extensible protocol for service discovery within a site. It allows but does not require centralized administration. Even when security, administrative policies or convenience require centralization (say in large enterprise deployments) the protocol requires very little administration. The protocol limits its use of multicast and broadcast as much as possible to conserve network bandwidth. Moreover, the protocol is extensible to arbitrary service advertisement and discovery and supports multiple languages and character set encodings.

The working group will document procedures for discovering services, and standardize "service:" schemes, which are definitions for resource and service URLs.

The focus of the working group will be on completing various documents which describe how to do service discovery and how to standardize service definitions which will be advertised and discovered.

- Interactions between Service Location Protocol and other enterprise naming and directory service protocols will be explored, defined, and standardized.

- Schemes for popular services will be discussed, and standardization efforts with other working groups explored as needed.

- Operational experiences and security procedures will be discussed and documented as best current practice.

- Service Type attribute definitions will be standardized by registering a 'Service Template' with IANA. This document will also describe how Service Types and Directory Schemas can be made interoperable. The Service Location Protocol can then be used to populate a directory service dynamically.

- An Application Programmers Interface has been developed to allow a uniform mechanism for applications to make use of Service Location Protocol functions, which will be supplied as an informational document.

- The Service Location Protocol itself will be revised and improved on, continuing it along the standards track.

Goals and Milestones:

Done &nbsp&nbsp Open discussion and determine if a working group should be formed.
Done &nbsp&nbsp Continue discussion trying to refine the problem statement and possible resolutions.
Done &nbsp&nbsp Issue a standards track protocol specification for the Service Location Protocol
Done &nbsp&nbsp Define an authentication mechanism for Service Location.
Nov 97 &nbsp&nbsp Submit an API for the Service Location Protocol to IESG for consideration as an Informational RFC.
Nov 97 &nbsp&nbsp Define a Service Discovery procedure for use in site as well as internet applications. Also define a mechanism for advertising services using DNS TXT records.
Nov 97 &nbsp&nbsp Submit the modifications to SLP for implementing it on IPv6 to IESG for consideration as a Proposed Standard.
Nov 97 &nbsp&nbsp Submit a service: URL and service template definition as an Internet-Draft.
Dec 97 &nbsp&nbsp Submit a revised I-D of the Service Location Protocol reflecting implementation experience and working group consensus on open issues.
Jan 98 &nbsp&nbsp Review the status of the SVRLOC WG. Revise the charter or shut down.

No Current Internet-Drafts

Request For Comments:

Service Location Protocol (RFC 2165) (169889 bytes)
Service Location Protocol, Version 2 (RFC 2608) (129475 bytes)
Service Templates and service: Schemes (RFC 2609) (72842 bytes)
An API for Service Location (RFC 2614) (164002 bytes)
Conversion of LDAP Schemas to and from SLP Templates (RFC 2926) (55365 bytes)
Service Location Protocol Modifications for IPv6 (RFC 3111) (25543 bytes)