Re: FW: EPP extensions working group

Hi Patrick

You are right, the challenges on the technical side are not to much of a 
problem. The economical side and policies (in some cases the legal / 
regualatory requirements) induce far stronger drag to more harmonization 
in EPP.

Back in 2005 (while still working for the .ch/.li ccTLD / before EPP was 
implemented widely) I took an effort (in CENTR) to standardize one 
consolidated alternative for each of those parts in EPP, that did not fit 
well for most (European) ccTLDs. Those were mainly the Contact object and 
the Transfer Logic (among other smaller issues).

It was rather difficult to convince other Registries to invest time and 
resources into more EPP standardization. The question I got was often: 
"What is our incentive, if we can just make our own extensions and let the 
Registrars deal with it?"


And on the Registrar side I often hear: "We have implemented all the 
extensions by now. Why should we help to make things easier to new 
competitors?"


I don't think things have changed too much in the meantime, however I'd be 
more than happy to learn the opposite, i.e. that things had changed...


cheers,
  Bernie

--

http://ucom.ch/
Tech Consulting for Internet Technology


On Tue, 23 Jul 2013, Patrick Mevzek wrote:

> As stated in my presentation however the crux of the problem is not
> technical but economical : specifically for currently in use
> extensions, registries will have no incentive to switch over new ones
> doing the same thing even if done more "standardized", with registrars
> not wanting to change their existing implementation
> (from my ccTLD technical experience, we still see people struggling
> with DNSSEC in general, and specifically DNSSEC in EPP)
>
> This is my only fear in working on "unified/standardized" versions: at
> the end, what guarantee do we have that we have really replaced the
> old ones, and not just create another iteration?
>
> Obligatory XKCD on that: http://xkcd.com/927/
>
> -- 
> Patrick Mevzek
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg
>
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg