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

[Andrew Newton <[e-mail]>]

On Sat, Feb 15, 2014 at 5:44 PM, Darrel Miller <[e-mail]> wrote:
> As an example, this URL,
> http://example.com/.well-known/rdap/ip/192.0.2.0/24 would be pain for
> a few of the frameworks that I am familiar with as it is not possible
> to have a slash as part of a parameter value.  Creating a routing that
> would handle both the IP and CIDR parameters would be tricky.

And yet there are some methods/frameworks that would have a problem
doing as you suggest as well, so it's a tradeoff. As it stands, all
RDAP lookups can be laid down on a file system. Your suggestion would
remove that.

> Now all you need is a single .well-known name, such as,
> http://example.com/.well-known/rdap/home that could return something
> like this application/home+json document,

[..snip..]

I believe this is where Mark was going with the bootstrapping. It's
worth exploring at that layer as it is more useful there than with
.well-known.

Thanks.

-andy