RFC 2608: Service Location Protocol, Version 2
In plain English — editorial summary, not part of the RFC
The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet need little or no static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2608
- Published
- June 1999
- Authors
- E. Guttman; C. Perkins; J. Veizades; M. Day
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 54
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2128Dial Control Management Information Base using SMIv2Current
March 1997
- RFC 2127ISDN Management Information Base using SMIv2Current
March 1997
- RFC 2605Directory Server Monitoring MIBCurrent
June 1999
- RFC 2609Service Templates and Service: SchemesCurrent
June 1999
- RFC 2610DHCP Options for Service Location ProtocolCurrent
June 1999
- RFC 2614An API for Service LocationCurrent
June 1999
- RFC 2863The Interfaces Group MIBUpdated
June 2000
- RFC 2878PPP Bridging Control Protocol (BCP)Obsoleted
July 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?