Browse Prior Art Database

Architecture of the Whois++ Index Service (RFC1913) Disclosure Number: IPCOM000004231D
Original Publication Date: 1996-Feb-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 13 page(s) / 31K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Weider: AUTHOR [+1]


The authors describe an architecture for indexing in distributed databases, and apply this to the WHOIS++ protocol.

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

Network Working Group C. Weider

Request for Comments: 1913 Bunyip

Category: Standards Track J. Fullton


S. Spero


February 1996

Architecture of the Whois++ Index Service

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.


The authors describe an architecture for indexing in distributed

databases, and apply this to the WHOIS++ protocol.

1. Purpose:

The WHOIS++ directory service [Deutsch, et al, 1995] is intended to

provide a simple, extensible directory service predicated on a

template-based information model and a flexible query language. This

document describes a general architecture designed for indexing

distributed databases, and then applys that architecture to link

together many of these WHOIS++ servers into a distributed, searchable

wide area directory service.

2. Scope:

This document details a distributed, easily maintained architecture

for providing a unified index to a large number of distributed

WHOIS++ servers. This architecture can be used with systems other

than WHOIS++ to provide a distributed directory service which is also


3. Motivation and Introduction:

It seems clear that with the vast amount of directory information

potentially available on the Internet, it is simply not feasible to

build a centralized directory to serve all this information. If we

are to distribute the directory service, the easiest (although not

necessarily the best) way of building the directory service is to

build a hierarchy of directory information collection agents. In this

architecture, a directory query is delivered to a certain agent in

the tree, and then handed up or down, as appropriate, so that the

query is delivered to the agent which holds the information which

fills the query. This approach has been tried before, most notably

in some implementations of the X.500 standard. However, there are

number of major flaws with the approach as it has been taken...