RFC 3082: Notification and Subscription for SLP
In plain English — editorial summary, not part of the RFC
The Service Location Protocol (SLP) provides mechanisms whereby service agent clients can advertise and user agent clients can query for services. The design is very much demand-driven, so that user agents only obtain service information when they specifically ask for it. There exists another class of user agent applications, however, that requires notification when a new service appears or disappears. In the RFC 2608 design, these applications are forced to poll the network to catch changes. In this document, we describe a protocol for allowing such clients to be notified when a change occurs, removing the need for polling. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3082
- Published
- March 2001
- Authors
- J. Kempf; J. Goldschmidt
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3224Vendor Extensions for Service Location Protocol, Version 2Current
January 2002
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
- RFC 3049TN3270E Service Location and Session BalancingCurrent
January 2001
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 2610DHCP Options for Service Location ProtocolCurrent
June 1999
- RFC 2609Service Templates and Service: SchemesCurrent
June 1999
- RFC 3822Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)Updated
July 2004
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?