"the" plan

Daniel,

>   > Elise Gerich <epg at merit.edu> writes:
>   > Daniel,
>   > Here is what we'd like to do. 
>   > 
>   > 1) Announce our registry on Wednesday (this is using the minimum
>   > set we agreed on and the extensions from our draft document)
>   > 2) we have a translation program which will translate our
>   > data to a syntax compatible with RIPE
>   > 3) we will store your data in our registry with source RIPE
>   > and will give you the compatible file to store in your DB with
>   > source Merit
> 
> Perfect.
> 
> We should find a mechanism for incremental updates too, like just forwarding
> the update messages with a special kludge to prevent multiple 
> diagnostic replies.

Good idea - we have discussed this but have no solution right now.

> 
>   > 4) Laurent is working on a whois daemon that will search both
>   > DBs - thereby negating the need to swap files
> 
> Doing a whois daemon that queries multiple places has some design issues
> associated with it. At least the following will have to be looked at:
> 
> 	- how to deal with replication of data (wanted for redundancy)
> 
> 	- how to combine and use multiple answers
> 
> 	- how to report only partial availability of servers back to the user
> 
> 	- Rwhois work by Kosters and Williamson
> 	
> 	- other distributed whois work
> 
> We have looked into some of this and it is not straightforward. 
> It ain't difficult either but we want to consider waht we are 
> doing carefully.

My statement was not completely accurate. We are interested in exploring
the whois daemon that queries multiple places, but what Laurent is
working on as an intermediary step is a whois daemon that understands
both the original RIPE-81 syntax and the Merit syntax.
This whoisd can look at several DB files on the same host, but
does not support query to multiple places yet. Laurent will send
a more detailed message about the whoisd.

So immediately, we have a translation program which will translate
the Merit syntax to compatible RIPE syntax. We will send you the
ripe-a-like file so that you may store it on your machine and the
whoisd will return the ripe-a-like info for info registered with
Merit and prtraceroute will work.

The whoisd that Laurent is working on would be able to read the
RIPE-81 syntax AND the Merit syntax thereby negating the need for
the translation program.  Files that are exchanged between us
would have the "native" syntax and the whoisd would be able to
respond with information from either and prtraceroute would
work with the new whoisd.

Then down the road we would try to actually have a whoisd that
would obviate the need for exchanging files.

> 
>   > 5) if you are agreeable, we would like to have both of us run the
>   > new whois daemon when it is ready (Laurent says that prtraceroute
>   > will work just fine with the new whoisd).
> 
> see above.
> 
>   > So, does this sound like a go to you all? If so, we will send
>   > a message to regional-techs, bgpd, iepg, and any ripe groups
>   > that you would like.
> 
> Fine. No jont announcement then. I don't mind.
> 

Guess I thought that it would still be a joint announcement since
we'd like the message to go from both of us - RIPE and Merit.

>   > Really looking forward to getting this show on the road.  Thanks.
> 
> Me too.
> 

How come everything seems to happen right before IETF???
        --Elise




-------- Logged at  Tue Mar 22 17:14:48 MET 1994  ---------