[gtld-tech] RDAP referral to registrar ?

Gustavo Lozano gustavo.lozano at icann.org
Thu Sep 1 01:04:20 UTC 2016


A nit in your comment, the requirement applies to ³thin² registrations.

BTW, a Registrar may optionally provide an RDAP service.


On 8/31/16, 04:34, "Michele Neylon - Blacknight" <michele at blacknight.com>

>Sorry if I¹m coming late to the party . Š
>This conversation makes it sound like registrars are expected to run RDAP
>services .. but since they¹d only be used for ³thin² registries they¹d
>only be used for a very limited time ..
>Am I missing something?
>Mr Michele Neylon
>Blacknight Solutions
>Hosting, Colocation & Domains
>http://www.blacknight.press - get our latest news & media coverage
>Intl. +353 (0) 59  9183072
>Direct Dial: +353 (0)59 9183090
>Social: http://mneylon.social
>Random Stuff: http://michele.irish
>Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business
>Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845
>On 31/08/2016, 12:30, "Hollenbeck, Scott" <gtld-tech-bounces at icann.org on
>behalf of shollenbeck at verisign.com> wrote:
>    > -----Original Message-----
>    > From: gtld-tech-bounces at icann.org
>[mailto:gtld-tech-bounces at icann.org]
>    > On Behalf Of Gustavo Lozano
>    > Sent: Tuesday, August 30, 2016 6:34 PM
>    > To: John Levine; gtld-tech at icann.org
>    > Subject: Re: [gtld-tech] RDAP referral to registrar ?
>    > 
>    > Unfortunately, HTTP redirections are not an option in the case of
>    > gTLD
>    > space, because Registries are contractually required to provide an
>    > response.
>    > 
>    > From an operational perspective, I think that HTTP redirections are
>    > also
>    > not an option in the case of the domain industry, because the
>    > business model has two parties (i.e. Registries and Registrars)
>    > certain portions of the data elements. For example, the Registry is
>    > authoritative source of information for the domain statuses.
>    Gustavo, if I'm understanding what you're saying correctly it would
>seem to
>    be a description of a use case in which redirection would actually be
>    *good* operational practice. If a registry has some data elements and
>    registrar has other data elements I believe it's possible to retrieve
>    sets of elements if (for example) a registry receives a query and
>    with an HTTP 300 (Multiple Choices) status code:
>    https://tools.ietf.org/html/rfc7231#section-6.4.1
>    The RDAP response data from the registry can be carried in the body
>of the
>    redirecting response. The client follows the redirect (or URI
>    found in the payload) to the registrar, sends the registrar a query,
>gets a
>    response, and both sets of data elements are retrieved.
>    Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4701 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20160901/3ccb2711/smime.p7s>

More information about the gtld-tech mailing list