Re: [apps-discuss] draft-ietf-weirds-bootstrap-00 and our lawn -- feedback?

[Mark Nottingham <[e-mail]>]

On 12 Feb 2014, at 1:09 am, Marc Blanchet <[e-mail]> wrote:

> yes. that is another way. it provides an additional level of indirection to remove the url component out from the spec. but it actually overload the registry with more data than typically necessary, and pretty repetitive. i.e. most likely every registry will have rel: domainlookup  href-template: http://exampleregistry1.com/lookup/{domain}, rel: domainlookup  href-template: http://exampleregistry2.com/lookup/{domain}, rel: domainlookup  href-template: http://exampleregistry3.com/lookup/{domain}.  Given the number of TLDs and that there are about 10 objects, we are multiplying the entries by 10, becomes pretty large registry operationally to parse.

Perhaps, but it may be possible to mitigate that, depending on the particulars of how it's going to be used and deployed.

E.g., have IANA run a lookup service themselves; e.g., http://iana.org/rdap/domain/foo.com

Or, define a document format that IANA points to in the registry, and *it* points to the various endpoints. 

Also, if the data is that voluminous, it suggests that you may have a problem anyway; adding such repetitive information shouldn't affect the size of the response after gzip (which you'd want to use in any case) that much.



>> I'm very curious to hear what other APPS folks think about this -- especially those of a Web bent. We're trying to line up some conversations about this in London, and I'd like to inform them with the WG's perspective, rather than just my own.
> 
> btw, "them/they", "we":  we are the same IETF people. Why are we talking the "them" and "we" perspective?

Strangely, we *do* organise ourselves into groups and areas here. Or are you proposing something more radical?

--
Mark Nottingham   http://www.mnot.net/