Re: [weirds] FW: I-D Action: draft-kong-dnrd-ap-response-json-00.txt

[Andrew Sullivan <[e-mail]>]

On Tue, Jun 12, 2012 at 10:04:55PM +0800, Ning Kong wrote:

> I think you put forward a general issue. IMO, the HTTP draft
> (draft-designteam-weirds-using-http-00) as the common infrastructure
> document is suitable to cover this point. For example, a new section (e.g.
> 5.5 Unauthorized Answers) may be added to propose the corresponding response
> mechanisms.

This raises an interesting and vexing issue, I think.

As we're working now, we are talking about responses and requests.
But in a REST context, it seems to me, you either get the resource or
you don't.  

One of the goals so far has been to permit differential levels of
service depending on credentials.  (I believe quite strongly that if
we do not provide that functionality, we will have completely botched
this work.)

It seems to me therefore that data we return must be much more linked
and much less cohesive.  For instance, in the present draft, the
response for domains includes contact data, nameserver data, and so
on.  But instead, that all ought to be linked data, so that it is
possible to return the appropriate response (e.g. the data vs. http
401 or 403 errors) depending on who asks for it.  It seems also that
it might be possible to create a roll-up type resource that provides
all the answers in one go, at the cost of authorization being the
denied if any of the underlying resource permissions aren't available.

Thoughts?

Best,

A 

-- 
Andrew Sullivan
[e-mail]