Novell EDIRECTORY 8.8 SP3, Administration Manual, Page: 408 / 634

408 Novell eDirectory 8.8 Administration Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
Š
“Using Scopes to Handle the 64 KB Limitation Issue” on page 408
Š
“Understanding Scope Filtering” on page 409
Š
“Filtering” on page 409
Scopes
In SLP, a scope is simply a list of SLP services that have been registered with a Directory Agent.
Using Scopes in Directory Mode
In Directory mode, when a Directory Agent is created, it registers the SLP Scope Unit container
object, which is the actual storage container for SLP service information. Each Scope Unit container
holds all the SLP Service objects for a specific scope. You can replicate this container into other
partitions within the tree or within federated trees.
As mentioned earlier, the Scope Unit has an attribute called the Scope Name. This Scope Name is
used by the Service Agent and User Agent to define what scopes they are to work with. SLP scopes
allow network administrators to organize SLP services into groups. The Service Agent determines
which groupings the services on that the server will be registered in. By default, all SLP services are
registered in the unscoped scope. When clients send SLP requests to a Directory Agent, they can
specify a scope for the Directory Agent to use in order to find the service they are looking for. If no
scope is specified by the client, the Directory Agent looks in the Unscoped table to find the
requested service.
A Directory Agent can service multiple scopes and a Service Agent can register services in multiple
scopes. The registered services can be replicated between sites by using eDirectory.
Using Scopes in Local Mode
Scopes configured in Local mode operate similarly to scopes configured for Directory mode with
the exception that the scopes are stored locally instead of in eDirectory. By default, all SLP services
are registered in the unscoped scope. We recommend that you configure at least one scope.
Using Scopes to Handle the 64 KB Limitation Issue
A total of 64 KB of data is the most that the Directory Agent can send to the client via a TCP
connection. If there is more than 64KB of a certain service type, the list will be cut short. The reason
for this is that in SLP 1, the length field in the SLP response packet header is only 16 bits, allowing
up to 64 KB of service data.
Table 15-20 lists the common service types that fit into a 64 KB response packet.
Table 15-20
Common Service Types
Service Number per Response Packet
NDAP.Novell About 1,200, depending on the length of the partition names
Bindery.Novell 700 to 1,100, depending on the length of the server names
MGW.Novell About 1,200
SapSrv.Novell No more than 540