Re: [weirds] New Unified DNR/RIR Internet-Drafts

[Byron Ellacott <[e-mail]>]

Hi Murray,

On 05/09/2012, at 5:03 PM, Murray S. Kucherawy wrote:

> A fairly complete set would appear to be something like:
> 
> draft-designteam-weirds-using-http
> draft-hollenbeck-weirds-rdap-sec
> draft-hollenbeck-weirds-unified-rdap-query
> draft-newton-weirds-unified-json-response
> draft-kucherawy-weirds-requirements (but only if we want to keep a
> requirements document going)
> 
> The issues of redirection and service discovery don't appear to be
> covered in this set.  I seem to recall consensus ion Vancouver
> swinging in the direction of deciding that we don't want to tackle
> discovery on a first pass, but I can't recall where we landed on
> redirection.  (I also admit I haven't yet reviewed the JSON response
> document to know if it covers redirection.)  Please correct me if I'm
> wrong there.

Redirects can be found here:

http://tools.ietf.org/html/draft-designteam-weirds-using-http-01#section-5.2

> So far response to the middle three has been entirely positive.  Can I
> get some comments on the first and last, and also on the issue of
> redirection, and a few more comments from people representing the name
> registries?

I think I missed a call or two here, so to be clear, I support WG adoption of all five drafts.

Regarding redirection, the text in using-http suggests 301 for permanent relocations, and 307 for all other situations.  I am in favour of specifying only this much about redirection, leaving matters like authentication to be dealt with by each server-client interaction separately.

  Byron