Re: [weirds] Query Parameters

["Hollenbeck, Scott" <[e-mail]>]

> -----Original Message-----
> From: Andy Newton [mailto:[e-mail]]
> Sent: Friday, May 04, 2012 11:00 AM
> To: Hollenbeck, Scott
> Cc: Francisco Arias; [e-mail]
> Subject: Re: [weirds] Query Parameters
> 
> 
> On May 4, 2012, at 10:23 AM, Hollenbeck, Scott wrote:
> 
> > It would be very helpful to identify the query parameters that
> registries and registrars currently support. As a start, here's what we
> currently support at Verisign for lookups:
> >
> > Domain: by domain name (example.com)
> > Name server: by host name (ns1.example.com) and by IP address (v4 and
> v6 text format)
> > Registrar: by registrar name (text string case insensitive match) and
> by registrar ID
> > Contact: by EPP contact ID and by EPP ROID
> 
> Given Francisco's suggestion, would it be worth teasing each of these
> out into separate drafts? That way ICANN can say that it's regulated
> registries support must support RFC 1, RFC 2, RFC 3, while other
> registries can simply say "we support RFC 1 and RFC 3". Or maybe put
> the domain name lookup in its own draft and the rest in a draft
> intended as a collection of the other things ICANN registries must do.
> Just a thought.

Maybe, I'm not sure. If I'm writing client code I would probably want to support as many query parameters as possible to work with as many servers as possible, and having all client query parameters specified in one document would probably be easier than having to worry about multiple documents. A server operator that doesn't support a particular type of query can just return an appropriate HTTP response.

I guess I'm saying that I don't think we should be writing clients on a per-registry basis.

Scott