Slp Service Scope Option (Option 79) - Extreme Networks Summit WM Technical Reference Manual

Service Agent so configured must not employ either active or passive multicast discovery of Directory
Agents.
The Directory Agents listed in Option 78 must be configured with the a non-empty subset of the scope
list that the Agent receiving the Directory Agent Option 78 is configured with.

SLP Service Scope Option (Option 79)

Services are grouped together using scopes. Scopes are strings that identify a set of services that form an
administrative grouping. Service Agents (SAs) and Directory Agents (DAs) are always assigned a scope
string.
A User Agent (UA) is normally assigned a scope string (in which case the User Agent can only discover
that particular grouping of services). This allows a network administrator to provision services to users.
The use of scopes also allows the administrator to scale SLP deployments to larger networks.
The Scope-List String is a comma-delimited list of the scopes that a SLP Agent is configured to use. The
Length value must include one for the Mandatory byte. The Mandatory byte determines whether SLP
Agents override their static configuration for scopes with the <Scope List> string provided by the
option. This allows DHCP administrators to implement a policy of assigning a set of scopes to Agents
for service provision.
If the Mandatory byte is 0, static configuration takes precedence over the DHCP provided scope list. If
the Mandatory byte is 1, the <Scope List> provided in this option must be used by the SLP Agent. The
Scope List String usage is defined in the SLPv2 specification (RFC2608).
19
Summit WM Technical Reference Guide, Software Version 5.1