It is interesting to see the discussion about EPP over HTTP. Right now I am
working on a greenfield development project where we will need to connect to
the majority of Registries. Being that this is a greenfield project we have
been keen to architect the system that will interact between
On Wed, May 30, 2018, at 22:24, Antoin Verschuren wrote:
> I remember a CENTR meeting where ccTLD’s tried to get consensus over if
> we could harmonize EPP extensions so registrars would not have to code
> differently for every TLD.
> This was before EPPEXT existed.
> We all thought this would
Op 28 mei 2018, om 22:48 heeft Patrick Mevzek het volgende
geschreven:
> In your quote you missed the other part which is basically: all domain names
> are not under ICANN policies.
I didn’t want to go in that discussion, but I’m on your side on that one.
> So for all other TLDs currently
Folks, one of the questions that came up during a presentation at the recent
Registration Operations Workshop was focused on RDAP's search capabilities and
if they were sufficient for use in the gTLD community. Francisco Arias has some
thoughts on functional requirements, so I thought it might
Besides DNSSEC, I'm thinking of NS data and reseller data
kind regards
Pieter
> On 30 May 2018, at 11:10, Kal Feher wrote:
>
> Hi Pieter,
>
> could you elaborate on what objects you think might be modified? Are you
> thinking of anything other than DNSSEC material?
>
> delegation of epp
Hi Pieter,
could you elaborate on what objects you think might be modified? Are you
thinking of anything other than DNSSEC material?
delegation of epp to 3rd parties that are unknown to the registry does
have some operational implications that need to be thought through.
Although I suppose
