[Gnso-igo-ingo-crp] Proposed Implementation of GNSO Consensus Policy Recommendations for the Protection of IGO&INGO Identifiers in All gTLDs

[Phil Corwin]

Thanks Mary

George, the portion of the proposal that relates to our WG is this-

                Specifically, the names that are protected by this policy are:

        ...             2.Full names of specific IGOs in up to two (2) languages: reservation at the top- and second-level.

If implemented, this will somewhat reduce any potential need for recourse to CRP by IGOs by blocking registration of their full names at the second level in two languages. Access to CRP would remain relevant for registration of the full name in a third language, registration of their acronym, and confusingly similar domain registrations.

Hope that helps.

Best, Philip


Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/Cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

From: gnso-igo-ingo-crp-bounces at icann.org [mailto:gnso-igo-ingo-crp-bounces at icann.org] On Behalf Of Mary Wong
Sent: Thursday, May 18, 2017 7:50 AM
To: George Kirikos
Cc: gnso-igo-ingo-crp at icann.org
Subject: Re: [Gnso-igo-ingo-crp] Proposed Implementation of GNSO Consensus Policy Recommendations for the Protection of IGO&INGO Identifiers in All gTLDs

Thanks for this, George. All - this proposed implementation relates only to the GNSO policy recommendations that have been approved to date by the ICANN Board and does not concern the remaining ones that are inconsistent with GAC advice. For IGOs this means the implementation is limited only to the full names on the GAC list that are to be reserved, and not to IGO acronyms.

Petter is a member of the implementation team so he may have more to add.

Cheers
Mary

Sent from a mobile phone, sorry for any errors and brevity.

On May 18, 2017, at 13:44, George Kirikos <icann at leap.com<mailto:icann at leap.com>> wrote:
FYI, ICANN published this last night:

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_igo-2Dingo-2Dprotection-2D2017-2D05-2D17-2Den&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=lF80__SQQ-qOtSw8rdAD4R-khWD3IgGxI3iNzhGDGK0&s=Y0xJkKLXb0tG7t-MBWMr7-WRqlblKZYJs5j-E579c7A&e=

and conceivably it might impact our work to some degree. More comments
later, once I've had time to analyze it fully.

Sincerely,

George Kirikos
416-588-0269
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.leap.com_&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=lF80__SQQ-qOtSw8rdAD4R-khWD3IgGxI3iNzhGDGK0&s=S1m4HhlvHU90HICk3Z70W3bp6Yvf78DT0qkVH_629VY&e=
_______________________________________________
Gnso-igo-ingo-crp mailing list
Gnso-igo-ingo-crp at icann.org<mailto:Gnso-igo-ingo-crp at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com/email-signature>
Version: 2016.0.8012 / Virus Database: 4776/14441 - Release Date: 05/06/17
Internal Virus Database is out of date.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-igo-ingo-crp/attachments/20170518/76f7b19e/attachment.html>