Browse Prior Art Database

How to Interact with a Whois++ Mesh (RFC1914)

IP.com Disclosure Number: IPCOM000004232D
Original Publication Date: 1996-Feb-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 10 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Faltstrom: AUTHOR [+2]

Related Documents

10.17487/RFC1914: DOI

Abstract

In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 23% of the total text.

Network Working Group P. Faltstrom Request for Comments: 1914 Bunyip Information Systems, Inc. Category: Standards Track R. Schoultz KTHNOC C. Weider Bunyip Information Systems, Inc. February 1996

How to Interact with a Whois++ Mesh

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.

1. Overview

In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server ’refers’ the client to the next appropriate server(s). The protocol is simple. The client opens a connection to a server, sends a query, receives a reply, closes the connection, and after parsing the response the client decides which server to contact next, if necessary.

So, the client needs to have an algorithm to follow when it interacts with the Whois++ mesh so that referral loops can be detected, cost is minimised, and appropriate servers are rapidly and effectively contacted.

Faltstrom, et al Standards Track [Page 1]

RFC 1914 How to Interact with a Whois++ Mesh February 1996

2. Basic functionality

Each Whois++ client should be configured to automatically send queries to a specific Whois++ server. The deault Whois++ server can vary depending on which template is desired, and the location of the client with respect to the WHOIS++ index mesh, but as a rule the server should be as local as possible.

A / \ B C / \ \ Z -----> D E F / \ G H

Fig 1: The client Z is configured to first query server D

After getting responses from a server, the client can act in several ways. If the number of hits is greater than zero, the response is just presented to the user. If the client gets one or many servers- to-ask answers, the client should be able to automatically resolve these pointers, i.e. query these servers in turn.

A / \ B C / \ \ Z <----- D E F \ / \ --> G H

Fig 2: The client Z gets a "servers-to-ask G" response from D and therefore may automatically queries server G.

3. How to navigate in the mesh

A client can use several different strategies when traversing or navigating around in the mesh. The automatic way of doing this is to just "expand the search" (described in 3.1) and a second method is to use the "Directory of Servers" (described in 3.2).

3.1. Expansion of searches

If the number of hits is zero, or if the user in some way wants to expand the search, it is recommended for the client to issue a ’polled-by’ and ’polled-for’ query to the server. The client can then repeat the original query to the new servers indicated.

Faltstrom, et al Standards Track [Page 2]

RFC 1914 How to Interact with a Whois++ Mesh February 1996

A / \ /-----> B C / / \ \ Z <----- D E F / \ G H

Fig 3: The client Z gets a "polled-by B" response from D and therefore queries s...

Processing...
Loading...