The serviceid: URI Scheme for Service Location
draft-guttman-svrloc-serviceid-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Erik Guttman | ||
Last updated | 2002-08-13 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Service Location Protocol (SLP) allows clients to discover services with little or no prior configuration. SLP can be used to advertise services of any kind through the use of URLs. However, SLP uses URLs for two purposes: as a LOCATOR (indicating the location of the service) and as an IDENTIFIER (used for subsequent operations on a service, such as registration, deregistration and looking up attributes.) Confounding these two functions in one object leads to certain problems. The serviceid: scheme separates identification from location, eliminating these problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)