Hello, On 7/14/20 17:21, Patrick Mevzek wrote:
> It is a classical chicken and egg problem based on the fact that registries, > once they got one version working have no or very little incentive to change > (being similar as other registries is not a strong force for them) and for > registrars as long as not all registries do the same thing they have anyway > to code for the extra case and then once they done it for one registry they > could as well use that for others. So for registries they have only one case > to handle, where registrars have many but for registries each registrar is > like any other, besides its market position eventually. > > However, for a non trivial number of players in this game they are bound by > contracts that > can basically force them to implement new standards after some given delay. > But that wouldn't apply for ccTLDs where each registry is king in its kingdom. True, and even for gTLDs, there is no real pressure here since ICANN doesn't seem to be particularly aware of the EPP fee extension (or care about interoperability with regard to domain price tiers for that matter). But that may (and should) change, of course. > Besides market pressure, that has its limits here, I see only contractual > forces able to move things around. It could go a long way if some of the larger registries (Verisign, Afilias, Neustar, CentralNic, Donuts) would care to implement the RFC version *and* start to phase out the older versions with clear deadlines. As long as they keep supporting ancient versions of the extension (or, in the case of Donuts, use their own proprietary one), the larger registrars will see no incentive to implement newer versions, and will in turn pressure smaller registries into adding support for these ancient versions (e.g. by threatening to otherwise not include their premium domains in their portfolios). Best regards, Thomas -- TANGO REGISTRY SERVICES® Knipp Medien und Kommunikation GmbH Thomas Corte Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: thomas.co...@knipp.de Germany _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
