Browse Prior Art Database

An API for Service Location (RFC2614)

IP.com Disclosure Number: IPCOM000003201D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Kempf: AUTHOR [+2]

Abstract

The Service Location Protocol (SLP) provides a new way for clients to dynamically discovery network services. With SLP, it is simple to offer highly available services that require no user configuration or assistance from network administrators prior to use. This document describes standardized APIs for SLP in C and Java. The APIs are modular and are designed to allow implementations to offer just the feature set needed. In addition, standardized file formats for configuration and serialized registrations are defined, allowing SLP agents to set network and other parameters in a portable way. The serialized file format allows legacy services to be registered with SLP directory agents in cases where modifying the legacy service program code is difficult or impossible, and to portably exchange a registration database.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group J. Kempf

Request for Comments: 2614 E. Guttman

Category: Informational Sun Microsystems

June 1999

An API for Service Location

Status of This Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Abstract

The Service Location Protocol (SLP) provides a new way for clients to

dynamically discovery network services. With SLP, it is simple to

offer highly available services that require no user configuration or

assistance from network administrators prior to use. This document

describes standardized APIs for SLP in C and Java. The APIs are

modular and are designed to allow implementations to offer just the

feature set needed. In addition, standardized file formats for

configuration and serialized registrations are defined, allowing SLP

agents to set network and other parameters in a portable way. The

serialized file format allows legacy services to be registered with

SLP directory agents in cases where modifying the legacy service

program code is difficult or impossible, and to portably exchange a

registration database.

Table of Contents

1. Introduction 4

1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2. Terminology . . . . . . . . . . . . . . . . . . . . . 4

2. File Formats 7

2.1. Configuration File Format . . . . . . . . . . . . . . 8

2.1.1. DA configuration . . . . . . . . . . . . . . 9

2.1.2. Static Scope Configuration . . . . . . . . . . 9

2.1.3. Tracing and Logging . . . . . . . . . . . . . 11

2.1.4. Serialized Proxy Registrations . . . . . . . . 11

2.1.5. Network Configuration Properties . . . . . . . 12

2.1.6. SA Configuration . . . . . . . . . . . . . . . 14

2.1.7. UA Configuration . . . . . . . . . . . . . . . 14

2.1.8. Security . . . . . . . . . . . . . . . . . . 15

2.2. Multihomed Machines. . . . . . . . . . . . . . . . . . 16

2.3. Serialized Registration File . . . . . . . . . . . . . 16

2.4. Processing Serialized Registration and Configuration

Files . . . . . . . . . . . . . . . . . . . . . . . . 18

3. Binding Independent Implementation Considerations ...