[Ietf-not43] XML-RPC for an information service?

[Stephane Bortzmeyer]

On Fri, Jul 26, 2002 at 01:28:12PM -0400,
 Leslie Daigle <leslie@thinkingcat.com> wrote 
 a message of 75 lines which said:

> What you are proposing seems based on the assumption that you know
> what server you are going to connect to, 

Right. Referrals are another TODO.

> queries you might make against it.  That's the easy part of what
> CRISP is trying to do.  CRISP is tasked with defining a _service_
> that will work across the individual servers managed by 
> registries,

Your explanation is very clear and precise but does not reflect the
work I've seen on this WG. The IRIS draft, for instance, is not very
detailed on this point and, like my proposal, focus on interaction
with a given server.

> such that a client starting with some label (e.g.
> a dns name) can find the authoritative server and make the
> relevant query. 

This could be done on the client-side, too, like many whois clients do
at the present time.

"\.(com|net|org)" -> whois.networksolutions.com
"\.(info)"        -> whois.affilias.info
"\.(.*)           -> whois.nic.$1

> For example, the domain name SERVICE is 
> not just about the packet format for making dns queries; it's
> also about having a well-known, universally-supported mechanism
> for navigating the tree of servers to find authoritative information.

Glad you mention it. I could add just one line saying that the
authoritative server is found with RFC 2782.
  
> But until I'm a little more convinced you understand what problem
> this group is solving, 

I understand much better the issues, thanks to your explanations. But
I agree with the Ted Hardie's point of view: Crisp has several
problems to solve and my proposal more-or-less fits one (querying a
given server). Unlike you, I do not think it is the less important
question.