[gtld-tech] RDAP referral to registrar ?

Gustavo Lozano gustavo.lozano at icann.org
Tue Aug 30 22:33:33 UTC 2016

Unfortunately, HTTP redirections are not an option in the case of the gTLD
space, because Registries are contractually required to provide an RDDS

>From an operational perspective, I think that HTTP redirections are also
not an option in the case of the domain industry, because the prevalent
business model has two parties (i.e. Registries and Registrars) keeping
certain portions of the data elements. For example, the Registry is the
authoritative source of information for the domain statuses.

The mechanism defined in section 2.3 of the gTLD RDAP profile allows the
Registry to provide an RDAP response, and say something like "btw, this
other party may have more information".



On 8/29/16, 19:17, "gtld-tech-bounces at icann.org on behalf of John Levine"
<gtld-tech-bounces at icann.org on behalf of johnl at taugh.com> wrote:

>>From an automation and information publishing perspective, we think
>>always having a link to registrar from the registries might be very
>>convenient. Is there a way to publish this whenever it's available ?
>If the registrar has the information, the registry can return an http
>redirect to the registrar and it'll all look automatic to the client.
>In much the same way, if you do an RDAP query to one of the RIRs, and
>the address has been reassigned to another RIR, they do the redirect
>and for the client it just works.
-------------- 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/20160830/c1ae9ad7/smime.p7s>

More information about the gtld-tech mailing list