Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt

[Andy Newton <[e-mail]>]

On Jun 23, 2014, at 8:51 PM, Tom Harrison <[e-mail]> wrote:

>> For example, a domain RDAP query for a.b.example.com matches the com
>> entry in one of the arrays of the registry.  Following the example
>> above, the base RDAP URL for this query is
>> "https://registry.example.com/myrdap/".  The {resource} specified in
>> [I-D.ietf-weirds-rdap-query] is then appended to the base URL to
>> complete the query.  The complete query is then
>> "https://registry.example.com/myrdap/domain/a.b.example.com".  This
>> example is not normative.
> 
> This limits implementations to path-based lookup, since the object
> type and the query value don't have separate variables. This isn't in
> keeping with draft-ietf-appsawg-uri-get-off-my-lawn-05 [2.3], since an
> implementation might prefer to use query processing instead. Should
> there be text in the document explaining why this is OK in this case?

Perhaps the draft should say the template is “https://registry.example.com/myrdap/{resource}” and that {resource} is substituted for a.b.example.com.

But I think what is being proposed does allow for query use instead of path use, and the object type is implicit in the bootstrap registry type. For domains, the DNR could submit {proto}://example.com/blahblah?domain={resource} just as easily as {proto}://example.com/blahblah/{resource}.

BTW, if we are to stick with the proto array, we should really rename it. In URI/URL speak, it is “scheme” not protocol.

-andy