RFC 2610 (rfc2610) - Page 1 of 6
DHCP Options for Service Location Protocol
Alternative Format: Original Text Document
Network Working Group C. Perkins
Request for Comments: 2610 E. Guttman
Category: Standards Track Sun Microsystems
June 1999
DHCP Options for Service Location Protocol
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract
The Dynamic Host Configuration Protocol provides a framework for
passing configuration information to hosts on a TCP/IP network.
Entities using the Service Location Protocol need to find out the
address of Directory Agents in order to transact messages. Another
option provides an assignment of scope for configuration of SLP User
and Service Agents.
1. Introduction
The Dynamic Host Configuration Protocol [2] provides a framework for
passing configuration information to hosts on a TCP/IP network.
Entities using the Service Location Protocol, Version 2 [3] and
Service Location Protocol, Version 1 [4] need to obtain the address
of Directory Agents and Scope configuration. The Service Location
Protocol (SLP) provides a default configuration for Scopes and
Directory Agents may be discovered using multicast or broadcast. It
is useful in a larger deployment to be able to configure SLP Agents
using DHCP, so as to centralize the administration and to deploy SLP
in networks where multicast routing is not available.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [1].
Perkins & Guttman Standards Track