paf@nada.kth.se Mon, 25 July 1994 02:24 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09986; 24 Jul 94 22:24 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09978; 24 Jul 94 22:24 EDT
Received: from ucdavis.ucdavis.edu by CNRI.Reston.VA.US id aa14318; 24 Jul 94 22:24 EDT
Received: by ucdavis.ucdavis.edu (8.6.9/UCD2.50) id TAA05300; Sun, 24 Jul 1994 19:18:04 -0700
X-Orig-Sender: ietf-wnils-request@ucdavis.edu
Received: from staff.nada.kth.se by ucdavis.ucdavis.edu (8.6.9/UCD2.50) id TAA05266; Sun, 24 Jul 1994 19:17:59 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: paf@nada.kth.se
Received: by staff.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA15291; Mon, 25 Jul 94 04:17:48 +0200
Date: Mon, 25 Jul 94 04:17:48 +0200
Message-Id: <9407250217.AA15291@staff.nada.kth.se>
To: ietf-wnils@ucdavis.edu
Subject: draft-ietf-wnils-whois-mesh-00.txt

In a separate mail you will recieve the first draft of a document which
describes the client interaction with a whois++ mesh.

What is described is based on the standard centroid mechanism, both
how the normal "servers-to-ask" response is used, but also how
a client can "expand" a search by asking "polled-for" queries.

This document will in a very near future be expanded with a 
description of how the Directory-Of-Servers works and
can be used from a clients perspective.

So, this is the first try to describe how the mesh is working...

		Patrik, Rickard and Chris