Week 1 Status Report

> "Dale S. Johnson" <dsj at merit.edu> writes:
> > We need to make the tools just a little more configurable in the sense
> > of how they use different whois servers on "source:"s.
Multiple design issues here:
1) Which source:s comprise the routing registry?
2) In which precedence if multiple source:s have the same info?
This is really a RR consistency problem. But it exists and
even if we do consistency checking will continue to exist.
2a) is it OK to combine info from different sources?
3) Which servers to use?
4) In which order?
Current answers:
1) all
2) the server lookup precedence
2a) yes
3) only one selected by -h option, environment, configured
4) not applicable
My future answers:
1) should be limited (preferably in server)
2) server lookup precedence seems ok, but see 4)
2a) I don't really know. Until we see it break badly we can combine.
3) Everything should allow for an ordered list of servers.
If TCP connecting to the first one times out, use the next one. ...
We should look at automagic heuristics to choose a good one ... later.
4) see above, but then we might have to warn the user that a secondary
is being used because of possible different precedences for information.
> Ok; should this be on your queue, or should we help?
Think about those.
Daniel
-------- Logged at Wed Feb 23 12:12:40 MET 1994 ---------