Re: [regext] WGLC: draft-ietf-regext-org-02

[Antoin Verschuren <[e-mail]>]

Op 28 mei 2018, om 22:48 heeft Patrick Mevzek <[e-mail]> 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 can you let me know which protocol limitations currently forbid registry to add formatted content in their whois or, let us say just decide to implement RDAP to start with? Do you really think there are almost none because of protocol limitations, especially in the EPP channel, or maybe for other reasons?

Perhaps it’s not only protocol limitations, or perhaps limitation the wrong word, it’s more the pinpointed ICANN RRR model I think that can only be provisioned for now.
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 be a good idea.
But half the registries concluded that they wanted to stick to their own extensions because they felt local legislation or their local constituencies required them so, and the other half had the standpoint that they would only implement as followers, after extensions would be standardized.

Again Patrick, I share your concern of complexity, and we shouldn’t build something nobody uses.
I also shared your concern for double labeling both at the organization and link level, but James managed to convince me it’s a choice between two bad’s where the responsibility of registrars over records they maintain outscores double entries in the database for organizations that do anything for anybody.

The reseller draft was originally requested and supported by cnnic, sidn and dns belgium who also had the intend to implement. If not this standard then their own extension.
Other registries didn’t immediately acknowledge the need for resellers unless mandated by (ICANN) policy, but there was consensus that if we were to standardize something to accommodate resellers, it should be reusable for other emerging "Internet identifier registration related roles" as well. This was not only TLD registries that had an opinion, and I remember some hesitation especially by ICANN registrars as well because they didn't want extra work, but third party dns-operators, ICANN related policy makers, RIR’s, registrants and plain IETF protocol guardians also have an equal voice in the IETF process, even though they don’t implement.


- --
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: [phone]