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". Scott From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Gustavo Lozano Sent: Monday, October 05, 2015 10:34 AM To: gtld-tech@icann.org Cc: eppext@ietf.org Subject: [eppext] RDAP server of the registry Hello, 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? Regards, Gustavo Lozano ICANN