idnits 2.17.1 draft-kempf-srvloc-notify-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3082 5 Title: Notification and Subscription for SLP 6 Author(s): J. Kempf, J. Goldschmidt 7 Status: Experimental 8 Date: March 2001 9 Mailbox: james.kempf@sun.com, jason.goldschmidt@sun.com 10 Pages: 14 11 Characters: 33410 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-kempf-srvloc-notify-05.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3082.txt 18 The Service Location Protocol (SLP) provides mechanisms whereby 19 service agent clients can advertise and user agent clients can query 20 for services. The design is very much demand-driven, so that user 21 agents only obtain service information when they specifically ask for 22 it. There exists another class of user agent applications, however, 23 that requires notification when a new service appears or 24 disappears. In the RFC 2608 design, these applications are forced to 25 poll the network to catch changes. In this document, we describe a 26 protocol for allowing such clients to be notified when a change 27 occurs, removing the need for polling. 29 This memo defines an Experimental Protocol for the Internet community. 30 It does not specify an Internet standard of any kind. Discussion and 31 suggestions for improvement are requested. Distribution of this memo 32 is unlimited. 34 This announcement is sent to the IETF list and the RFC-DIST list. 35 Requests to be added to or deleted from the IETF distribution list 36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 37 added to or deleted from the RFC-DIST distribution list should 38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 42 help: ways_to_get_rfcs. For example: 44 To: rfc-info@RFC-EDITOR.ORG 45 Subject: getting rfcs 47 help: ways_to_get_rfcs 49 Requests for special distribution should be addressed to either the 50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 51 specifically noted otherwise on the RFC itself, all RFCs are for 52 unlimited distribution.echo 53 Submissions for Requests for Comments should be sent to 54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 55 Authors, for further information.