[gtld-tech] RDAP server of the registry

Hollenbeck, Scott shollenbeck at verisign.com
Tue Oct 6 18:53:52 UTC 2015

It’s more than just policy, Kaveh – it’s implementation requirements that I’m suggesting should be developed with community consensus. Internet-Drafts can be (and have been) written to document implementations of IETF standards. Here’s one example that became an Informational RFC:


An Informational-intended document that describes protocol option settings could be developed for RDAP in a very similar way. What’s in the document now is incomplete, but it would be a very good start, and as I said – I’m willing to help write.


From: Kaveh Ranjbar [mailto:kranjbar at ripe.net]
Sent: Tuesday, October 06, 2015 10:05 AM
To: Hollenbeck, Scott
Cc: Gustavo Lozano; gtld-tech at icann.org; eppext at ietf.org
Subject: Re: [gtld-tech] RDAP server of the registry

Hi Scott,

With all due respect I disagree. The intent of the document is to outline ICANN’s “policy” towards it’s Registries and Registrars. It basically points out the RFC’s they have to comply with and outlines a few issues and provisions, mostly ICANN specific requirements (for example details of address information) which IMHO is out of scope of an I-D.

On the other hand, there are few issues pointed out in the document (specially the ones from Appendix A) which are good candidates for IETF discussions and possibly updating (or writing new) RFCs.

All the best,

On 05 Oct 2015, at 13:11, Hollenbeck, Scott <shollenbeck at verisign.com<mailto:shollenbeck at verisign.com>> wrote:

Gustavo, I’d very much prefer to see the profile described in an I-D and developed using the IETF’s consensus process. I’m also willing to back up that preference with writing help as needed. I’ll have specific comments on the profile itself “soon”.


From: EppExt [mailto:eppext-bounces at ietf.org] On Behalf Of Gustavo Lozano
Sent: Monday, October 05, 2015 10:34 AM
To: gtld-tech at icann.org<mailto:gtld-tech at icann.org>
Cc: eppext at ietf.org<mailto:eppext at ietf.org>
Subject: [eppext] RDAP server of the registry


The first version of the ICANN gTLD profile was published days ago, (see:http://mm.icann.org/pipermail/gtld-tech/2015-September/000507.html), this document describes basic parameters and objects to be implemented by ICANN-contracted parties.

The gTLD Whois output contains a field with the Whois server of the Registrar. In the case of thin registries, this allows the end user to get the registration data from the registrar, and in the case of thick registries, this allows the end user to query for extra Whois fields (e.g. registrar expiration date).

The gTLD profile support the same functionality with the following mechanism:

The RDAP domain lookup response MUST contain a links object as defined in RFC7483 section 4.2. The links object MUST contain the elements rel:related and href pointing to the Registrar's RDAP URL for the queried domain object.

Questions for this group:

* What do you think about this proposal? If you have different ideas on how to provide this functionality, please share it with the group.
* What is your opinion about documenting this mechanism in an I-D?

Gustavo Lozano

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20151006/61dfbb80/attachment-0001.html>

More information about the gtld-tech mailing list