[gtld-tech] [eppext] RDAP server of the registry

Hollenbeck, Scott shollenbeck at verisign.com
Wed Oct 7 14:41:26 UTC 2015

> -----Original Message-----
> From: Gustavo Lozano [mailto:gustavo.lozano at icann.org]
> Sent: Wednesday, October 07, 2015 10:00 AM
> To: Patrik Wallström; Hollenbeck, Scott
> Cc: Kaveh Ranjbar; gtld-tech at icann.org; eppext at ietf.org
> Subject: Re: [eppext] [gtld-tech] RDAP server of the registry


> gTLD Registries want to have full requirements and an implementation
> plan
> for all RDSS (i.e. whois, rdap) related activities, therefore the
> schedule
> to have the gTLD profile ready looks tight.

Gustavo, what's driving that schedule? How does it fit with the RDDS policy
development processes that are either under way or being considered? The EWG
I was part of made a number of recommendations that depend on RDAP. Where do
those recommendations come into play?

This gTLD registry operator wants to be sure that we do this once, we do it
so that we don't have to undo things in the future, and we make
implementation decisions based on consensus policies. If that takes time, so
be it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5924 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20151007/2ea3ff24/smime-0001.p7s>

More information about the gtld-tech mailing list