[CPWG] [registration-issues-wg] Mission creep (was Re: Geographical Names and ISO 4217 alpha3 currency codes [...])

Sun Jun 30 16:54:01 UTC 2019

Dear Friends and Colleagues:

Allow me to add a few comments to this thread, and to note with appreciation that the issue was presented to CPWG in Marrakech with balance and understanding.

1.  It is evident that I have a rather broader view of the interests of Internet users than is the case for some of our colleagues.  In short, the interests of final Internet users include consumer protection and the conditions of fair and transparent competition.  

In this case, the risks of consumer confusion and/or financial and fiscal fraud, fully justify the reservation, or close regulation of the ISO 4217 currency codes, as to which Registries would be eligible to apply for them. 

2.  The current status of this question in the PDP is that the co-leads of WT5 have formally referred the question to the PDP plenary because they doubt that these codes are geographical names within the scope of WT5.

(A curious position in so far as all the currency codes are directly derived from the ISO3166 alpha2 country codes. Whereas the alpha3 country codes, equally so derived,  are fully protected.)

3.  ATLAS III?  I trust that this issue will have been resolved one-way-or-another before the Montreal meeting. However, even should colleagues deem that the currency codes are not geographical names and/or are not of interest to final Internet users, I would still consider that the issue is of major importance for the PDP, GNSO and the ICANN Board.

Best regards to you all

CW

PS:  Pour memoire, I attach my original paper for CPWG on this matter.

> On 24 Jun 2019, at 20:01, Evan Leibovitch <evan at telly.org> wrote:
> 
> On Mon, 24 Jun 2019 at 09:04, <h.raiche at internode.on.net <mailto:h.raiche at internode.on.net>> wrote:
> I also concur
> 
> Thanks to all for the support of this position.
> 
> As I get older, most of my thought processes these days start with "life's too short to dwell over the irrelevant". I didn't intentionally mean to pick on Christopher's issue to make this stand.
> 
> In the past, ALAC has indulged in this kind of mission-creep far too often and I confess to having been a part of that. We got way too deep into issues such as vertical integration, dot-brands and similar battles that have near-zero impact on end-users. In hindsight, I even think that the massive amount of work that ALAC did in promoting (new-gTLD) Applicant support -- an effort that I co-chaired -- was for the benefit of would-be registries and indirectly registrars, with little fallout beyond them.
> 
> It wasn't an Alt-Large issue.
> 
> I can bemoan the execution of the Applicant Support program but must now realize in hindsight that its failure really did not impact end-users one bit. Even had it succeeded, registrants would have benefited but the end-user impact would be negligible. Given the massive amount of person-hours spent on the program by myself, Avri, Tijani, Alice (from the GAC) and many others, this realization is disheartening. Others should learn from our errors and be encouraged to avoid similar paths of futile irrelevance.
> 
> As my penance I will do what I can going forward to repeat the end-user-relevance litmus test applied on currency-code TLDs to other ALAC issues and requests for comments, as they come forward. I invite others to be similarly vigilant.
> 
> At one time I recall that At-Large staff measured the success and effectiveness of ALAC by how many statements and comments it produced. That approach of measuring quantity rather than quality, in retrospect, was an awful mistake, and must be repudiated should it still exist(*). Let's be super selective in the topics of interest -- issues of trust, abuse, IDNs, access and safety, for example -- but do justice to them once identified.
> 
> Cheers,
> Evan
> 
> (*) Yet one more instance of the many ways in which At-Large-related metrics are awful and an impediment to our real effectiveness. The only metric that really matters is "how is ICANN better because we are here?"
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
> 
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on._______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
> 
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20190630/c2143ef8/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ISO 4217.pdf
Type: application/pdf
Size: 78620 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20190630/c2143ef8/ISO4217-0001.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20190630/c2143ef8/attachment-0003.html>