Enabling Proxy Registration

The first step in enabling proxy registration is to create a proxy registration file. You can locate the file anywhere on the host's file system, or anywhere else on the network that is accessible by HTTP. Use the net.slp.serializedRegURL property in the slp.conf file in the /etc/inet directory to locate it (see slp.conf(4)).

When creating proxy registrations, you should check whether a service type template exists for the service. A service type template is a description of the service URL and attributes for a service type. Templates enable UAs and SAs to interoperate, because they define what constitutes a service advertisement for a particular service type. If a service type template exists, you should use the template to construct the proxy registration. See RFC 2609 for more information on service type templates.

If a service type template is not available for the service, then you should select a collection of attributes that precisely describe the service. In addition, you should use a naming authority, other than the default, for the advertisement, because the default naming authority is only allowed for service types that have been standardized. See RFC 2609 for more information on naming authorities.

For example, suppose a company called BizApp has a local software defect database that they would like to advertise. They make a URL with the service type service:bugdb.bizapp and advertise that. In this case, the naming authority is bizapp.

When the proxy registration file is complete, you need to configure slpd to read it. Edit the slp.conf file and add the following line:

net.slp.serializedRegURL=<proxy registration file URL>

You do not add the file name here. Instead, you add a URL giving the location of the file. For example, if the serialized registration file is named slp.reg, and it is in the local /net/inet directory, you configure the following the URL property:

net.slp.serializedRegURL=file:/etc/inet/slp.reg