RFC 3832: Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV
In plain English — editorial summary, not part of the RFC
Remote service discovery refers to discovering desired services in given remote (i.e., non-local) DNS domains. This document describes remote service discovery in the Service Location Protocol (SLP) via DNS SRV. It defines the DNS SRV Resource Records for SLP Directory Agent services, discusses various issues in using SLP and DNS SRV together for remote service discovery, and gives the steps for discovering desired services in remote DNS domains. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3832
- Published
- July 2004
- Authors
- W. Zhao; H. Schulzrinne; E. Guttman; C. Bisdikian; W. Jerome
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
- Updated by:
- RFC 8553
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 2782A DNS RR for specifying the location of services (DNS SRV)Updated
February 2000
- RFC 3822Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)Updated
July 2004
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 3404Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)Current
October 2002
- RFC 3403Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) DatabaseCurrent
October 2002
- RFC 3402Dynamic Delegation Discovery System (DDDS) Part Two: The AlgorithmCurrent
October 2002
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
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?