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.
IETF · 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.
{
"id": "RFC3082",
"number": 3082,
"title_en": "Notification and Subscription for SLP",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "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.",
"authors": [
"J. Kempf",
"J. Goldschmidt"
],
"organizations": [],
"publication_date": "2001-03-01",
"current_status": "EXPERIMENTAL",
"current_status_ru": "Экспериментальный",
"publication_status": "EXPERIMENTAL",
"publication_status_ru": "Экспериментальный",
"lifecycle": "experimental",
"lifecycle_ru": "Экспериментальный",
"stream": "Legacy",
"stream_ru": "Исторический поток",
"area": "",
"area_ru": "",
"working_group": "",
"source_draft": "draft-kempf-srvloc-notify-05",
"page_count": 14,
"doi": "10.17487/RFC3082",
"keywords": [
"SLP",
"service location protocol"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc3082/",
"html": "https://www.rfc-editor.org/rfc/rfc3082.html",
"txt": "https://www.rfc-editor.org/rfc/rfc3082.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc3082/"
}
}