Service Location Protocol
draft-veizades-ipng-svrloc-00

Document Type Expired Internet-Draft (individual)
Authors John Veizades  , Charles Perkins  , Scott Kaplan  , Erik Guttman 
Last updated 1994-11-14
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-veizades-ipng-svrloc-00.txt

Abstract

The service location protocol provides a framework for the discovery and selection of network services. It relies on multicast support at the network layer of the protocol stack it is using. It does not specifically rely upon the TCP/IP protocol stack but makes use of concepts that are found in most TCP/IP protocol implementations. Traditionally, users find services using the name of a network host (a human readable text string) which is an alias for a network address. The service location protocol eliminates the need for a user to know the name of a network host supporting a service. Rather, the user supplies a set of attributes which describe the service. The service location protocol allows the user to bind this description to the network address of the service.

Authors

John Veizades (veizades@home.net)
Charles Perkins (charliep@computer.org)
Scott Kaplan (scott@catch22.com)
Erik Guttman (erik.guttman@sun.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)